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

  • @ByteMeEnglish
    23•1 month ago

    I think it would be nice if same communities from different instances could be merged in same way. Like there are 2 android communities.

    • @DendrologistEnglish
      1•1 month ago

      Join both?

      I like alcohol. That doesn’t mean every bar should merge into one big bar. Sometimes, despite two identical themed bars serving the same drinks and having similar clientele, you can have a cracking time in one and a shit time in the other.

      Sometimes, that’s due to the staff (or mods in terms of Lemmy), sometimes, that’s due to particularly fun customers being in that day, and sometimes it’s just your mood on the day.

      Having multiple communities for the same topic is a feature, not a bug. It also prevents a community from being strangled by 1 or 2 bad mods as another community can be made in response. Unlike the Reddit model, where there is 1 community for 1 topic, and if it has bad mods, well, you’re shit out of luck.

      • @ByteMeEnglish
        8•1 month ago

        Yeah okay, I meant if all communities want it of course. Just sometimes it leads to smaller communities that’s all