Have you ever wished for a social media platform that combines the best features of Lemmy and image boards with customizable feed algorithms? I know I have. Here's what my perfect social media platform would look like:

1. A mix of Lemmy and image board: My ideal platform would allow users to post both text-based content and images, using tags instead of communities. With a view like Lemmy^1, and another grid-view like an image board^2.

2. User curation: Unlike Lemmy, where images are difficult to find again due to the lack of tags , my ideal platform would have well-curated images with tags for easy searching^2.

3. Advanced search could also be implemented, as suggested in the Lemmy issue #3788.

4. User trust levels and community moderation: A hierarchical trust level system, similar to Discourse’s trust levels[^3], could distribute the responsibility among users and reduce the burden on admins. Trust levels would be assigned for each community based on user activity and voting affinity with the admin, allowing admins to shape their instance according to their preferences without micromanaging every aspect of the community. This idea is also discussed in the Lemmy issue #3548.

5. Customizable feed algorithms: One of the best things about Lemmy is that users can choose their own algorithm for their home feed^1. My ideal platform would take this a step further by allowing users to customize their feed algorithms like in Bluesky[^4].

6. Machine learning algorithms: To make the feed even more personalized, my ideal platform would use machine learning algorithms to suggest posts to users based on their activity on the platform[^5]. For example, if a user frequently upvotes posts about cats, the platform would suggest more cat-related posts to that user.

7. One-size-fits-all image format: Image boards are known for their simple, one-size-fits-all image format^2. My ideal platform would adopt this format to make it easy for users to share images without worrying about formatting issues.

[^3]: Understanding Discourse Trust Levels [^4]: Bluesky custom feeds and algorithms [^5]: How to implement personalized feed ranking

cross-posted from: https://lemmy.world/post/1723295

I've noticed that there are a few communities that tend to dominate when viewing all. Some days it gets to where looking at all isn't very different than just looking at Memes@lemmy.ml or 196@lemmy.blahaj.zone.

Before someone says "you can just block communities you don't want to see," it's not that I never want to see them, it's that I want to be able to have a view that shows me what is new and popular in a wide variety of communities. I appreciate seeing a few good memes in my feed. The problem is when that's all I see. Changing the sort from active to hot or top x days doesn't have much effect on which communities dominate, so that isn't the solution either.

"You can just subscribe to communities you like". True, but that has the effect of narrowing what I see. I'd like a view that showed me new things I never thought to subscribe to.

Lemmy devs - if you are reading this - it would be nice to have a feed that limited the number of posts showing up from any particular community. It could be a simple cutoff of 2 or 3 posts, or maybe some sort of weighting function to cause additional posts from the same community to appear lower in the sort order for that feed.

I'd love to hear what devs and other users think about this.

Edit: To everyone saying "just sort be new" - yes, that has its uses, but it only solves part of the problem. I'd like a feed that shows me what is new and popular, but from more than just one or two communities.

cross-posted from: https://merv.news/post/26663

most people i know use google by searching whatever question they have and including the word “reddit” at the end to find reddit threads since it currently has the most useful information.

As Lemmy gets more and more filled with useful threads and reviews it would be great if we can collectively improve Lemmy’s SEO so just including the word lemmy in a search will show lemmy threads related to the search.

The obscure tlds used in lemmy servers don’t help and lemmy.com currently redirects to lemm.ee. Is there a way we can improve the SEO of all instances or have lemmy.com be a aggregator of threads from many Lemmy servers?

I miss this function from reddit. I used it often to find if a post has already been submitted. Also, it was useful to see what else was posted from this domain. I hope some day this will come to Lemmy.

Examples:

1. https://www.reddit.com/domain/hillelwayne.com/
2. https://www.reddit.com/domain/hillelwayne.com/top/?sort=top&t=all

I propose relocating most issue discussions from GitHub to !issue_tracker@lemm.ee to optimize developer time and foster increased user engagement and collaboration. This transition would allow developers to focus on critical tasks while leveraging the voting system on Lemmy to sort comments and identify the most valuable ideas. Moreover, Lemmy's nested comments feature would enable a more organized discussion than on GitHub, where comments can become difficult to follow. By reserving the GitHub issue tracker for concise summaries and effective problem-solving, we can enhance the development process and improve the overall user experience. This approach aligns with the preference expressed by developers to minimize interactions on issue trackers [^1]. Additionally, by reducing the flood of comments on GitHub, we can ensure that developers' time is not wasted and that they can efficiently address important issues.

[^1]: Update from Lemmy after the Reddit blackout

• issue_tracking_bot
• The issues of deleted 'ghost' accounts haven't been posted. Need to figure out why.
• Should edit posts and comments if the corresponding issue content changes.

Many of the currently open pull requests are for adding new lemmy-ui user settings, for example keyboard navigation or infinite scroll. These settings are surely useful, but the process for adding them is unnecessarily complicated. Not only does a new setting have to be implemented in lemmy-ui, it also requires changes to this repo for adding a database migration, as well as adding the setting to various database and api structs.

This results in very repetetive work to implement and review such changes. It would be good if the process could be simplified in one way or another. A related problem is that we only store settings for lemmy-ui, but it would also be useful to store settings for alternative frontends and client apps.

One possible solution would be not to store individual settings, but an arbitrary json blob where Lemmy doesnt need to care about the content at all. This would also allow a user to store multiple settings blobs for different frontends/clients. Lemmy would have to do nothing more than provide endpoints for writing/reading the settings, and enforce a size limit.

Are there other solutions worth considering?

Originally posted by Nutomic in #3584

Describe the feature you'd like

Please add a button and/or keyboard shortcut that is the equivalent of clicking on an image thumbnail in a single post from the community view but applied to all image posts displayed on a page. This would be equivalent to Shift+X in Reddit Enhancement Suite.

Originally posted by archer007 in #1930