Please post one top-level comment per complaint about Lemmy. You can reply with ideas or links to existing GitHub issues that could address the complaints. This will help identify both common complaints and potential solutions.
I believe there are a large number of feature requests on Lemmy's GitHub page, making it difficult for developers to prioritize what's truly important to users. I propose creating a periodic post on Lemmy asking users to list their complaints and suggestions. This way, developers can better understand the community's biggest pain points and focus their efforts accordingly. The goal is to provide constructive feedback so developers can prioritize the most pressing issues.
Please keep discussion productive and focused on specific problems you've encountered. Avoid vague complaints or feature wishes without justification for why they are important.
Here is a summary of all the complaints from the previous post from six months ago. It's interesting to see how many issues have been solved and whether or not developers value user feedback.
spoiler
• Instance-agnostic links (links that don't pull you into a different instance when clicked)
• Ability to group communities into a combined feed, similar to multireddits
• Front page algorithm shows too many posts from the same community in a row, including reposts
• Need to separate NSFW and NSFL posts
• Basic mod tools
• Proper cross-posting support
• Ability to view upvoted posts
• Post tagging/flairs and search by flair
• Better permalink handling for long comment chains
• Combine duplicate posts from different instances into one
• Allow filtering/blocking by regex patterns
• Avatar deletions not federating across instances
• Option to default to "Top" comment sort in settings
• Migration of profile (posts, comments, upvotes, favs, etc.) between instances
• Mixed feed combining subscribed/local/all based on custom ratios
• Categories of blocklists (language, NSFW, etc)
• Group crossposts to same post as one item
• Feedback for users waiting for admin approval
• Propose mixed feed merging subscribed/local/all feeds
• Ability to subscribe to small/niche communities easier
• Reduce duplicate crossposts showing up
• Scroll to top when clicking "Next" page
• User flair support
• Better language detection/defaults for communities
• Ability to subscribe to category "bundles" of similar meta-communities
• RSS feed support
• Option to turn off reply notifications
• Easier way to subscribe across instances
• Default to "Subscribed" view in community list
• Fix inbox permalinks not navigating properly
• API documentation in OpenAPI format
• Notification badges should update without refresh
• Single community mode for instances
• Reduce drive-by downvoting in small communities
• More powerful front page sorting algorithm
Multi communities. They would be a big deal IMO. If you could have multiple saved into a list so that you could check different feeds depending on what you’re interested in, it would be much better. Combine that with the scaled sort (as well as the others), and you’re managing your feed very well IMO.
kbin currently has a "collections" feature which does this.
AFAICT, it's been something on lemmy's radar for a long while too. I get the sense the devs never worked out how they wanted to do it or maybe were a bit too ambitious in what they wanted from the feature and so it was kinda left by the way side, unfortunately. If I were to ever start contributing to lemmy it'd probably be the first thing I try to pick up.
Alternatively community federation, such that a community can be spread over multiple servers.
I'm not sure I understand what that would look like or why you'd want that ... ??
Like ... sort of an alliance of communities on different instances that are discrete but, because they've chosen to "ally" with each other, can be interacted with in some unified way??
Yes something like that, it makes sense because Lemmy is distributed and there are several channels that cross post the same articles, I have no idea if it's feasible.
Yea I think some more straight forward mechanisms could help there. Federating the alliance at a deep level is probably tricky. Some thoughts:
All of that would be, I think, easier than some deeper addition to federation.
More generally, I think a lot of fediverse stuff comes down to just getting smarter with our clients where some helpful endpoints on the server can help but aren't nearly as complex and don't need to increase the complexity on the federation side of things.
Does ActivityPub even support this?
Probably not, and I have no idea how hard it would be to implement.
Allowing communities that are the same name across servers to “interfederate” would be interesting too, I’d like some way cut down in repeat posts in same community feeds from different servers.
Piefed has this, and it's great!
They have multi communities!? Didn’t know!
Just had a brief look ... they seem to be created by the admin and not user defined?