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

    • Jake [he/him]@lemmy.mlEnglish
      0·
      8 months ago

      It was things said in the comments of that post and reading between the lines. I think the change is inevitable and already decided. The main active admin of .world is working on sublinks. That is enough for me to view time spent on building community on .world as a waste. If it was the other way around and they were coding in Rust and the Lemmy base was in js or whatever, maybe I’d think differently, but everything I’ve seen is a massive red flag saying sinking ship, or at least I’m on the wrong ship and regret the time spent there now. A lot of people left already. I have my other accounts, but had never made a .ml until recently in an attempt to start making sure communities were shared across larger instances, but I guess it was well timed to make the shift.

      • Die4Ever@programming.devEnglish
        0·
        8 months ago

        I don’t think the chosen language should matter that much, I’m just worried about the fragmentation of the contributors

        duplicated work that could’ve just been done together, or as 3rd party tools that link to the base Lemmy database/API, or plugins/extensions eventually