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

  • @PumpkinDrama@reddthat.comOPEnglish
    22•3 months ago
    • Moving user profile to a new instance #1985: Provide the ability for users to migrate their account and all associated data (posts, comments, moderation actions, saved posts, etc.) from one Lemmy instance to another. This would allow users to move freely between instances without losing their online identity, history, and credibility built up over time on a previous instance.

    It’s crazy when I see this super popular issues closed without completion by the main devs. It makes me feel like they don’t care at all about user feedback.

    • @lemmyingly@lemm.eeEnglish
      11•3 months ago

      There was a submission made about how few people donate to the Devs. I asked about transparency and some links were given that show some things. I commented that it’s not as transparent as it seems at first glance and they responded that it’s fully transparent. I asked them to clarify but they decided to ignore me. I see why the Devs get criticism.

    • flamingos-cantEnglish
      6•3 months ago

      Provide the ability for users to migrate their account and all associated data (posts, comments, moderation actions, saved posts, etc.) from one Lemmy instance to another.

      To implement this feature you’d either have to:

      • Edit the DB entries of every instance to match the new profile;
      • Create copies of the old content on the new instance and federate that out, thus duplicating all the data. You could have it delete the old content, but you’d still need to recreate all the posts and comments.

      Either of these would be very susceptible to abuse. Giving bad actors a button to force instances to run hundreds, potentially thousands, of operations probably isn’t the best of ideas.