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

  • loki@lemmy.mlEnglish
    20·
    8 months ago

    Hiding read posts means they’re now lost (when you’re logged in) if you didn’t save the link somewhere. Can’t find it after a day and now you have to check it on incognito.

    But if you don’t hide posts you’ve already read, you end up with the same posts on your feed.

    it’s a very small nitpick though. having new posts load every time I visit lets me see a lot of new content, I wouldn’t have seen otherwise.

    I hope some app devs can put up a section for “read posts” locally so instances aren’t overwhelmed.

    • PumpkinDrama@reddthat.comOPEnglish
      1·
      8 months ago

      I had to toggle between show and hide read posts all the time for the same reason but I don’t think having a read posts section would be any simpler than toggling the setting.

    • ripcord@lemmy.worldEnglish
      25·
      8 months ago

      I browse by top 12 hours and I don’t find a lot of repeats, without hiding. Although I don’t check constantly so 6 hours or less might be better for someone who does

      Edit: lol@the downvotes without replying; what’s wrong with the comment