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.

The goal is to provide constructive feedback so developers get clear insights into the issues impacting users the most. 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 last post. 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

  • maegul (he/they)@lemmy.mlEnglish
    0·
    7 months ago

    Yea I think some more straight forward mechanisms could help there. Federating the alliance at a deep level is probably tricky. Some thoughts:

    • Being able to view all the comments from the different cross posts or duplicate-link posts (which lemmy can automatically register). This has come up before, even in this comments section.
    • Easily manageable multi-communities. Basically my idea, but making sure that they are easy to share, load, manipulate and view. For instance, your idea of “Allied communities” could be achieved to some extent by having these communities list in their side bar (or maybe some other convenient spot for this specific purpose) a suggested multi-community that contains the other allied communities. But, instead of just being a list, it’s some sort of link that takes you to a view of that multi-community, like any other feed, which you can then easily save to your list of multi-communities.
      • If done along with cross-post comment merging, I’d say you pretty much get to your allied communities idea.
      • Maybe there’d some way to combine the two where the “cross-post-comment-merging” mechanism is aware if you’re viewing through a multi-community and so automatically (depending on a setting probably) merges across communities in your multi-community, or at least presents a button for easily doing that.

    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.