cross-posted from: https://discuss.online/post/5768097

Greetings c/lemmy_support community,

I wanted to express my frustration with the Lemmy developers for consistently closing my reported issues as “not planned” without involving the community in the decision-making process. It appears that the devs prioritize their own interests, such as developing Android thumb keyboard apps, over listening to user feedback and addressing community priorities.

Given this approach, I have decided that I will not be contributing to this project in any capacity. It is disheartening to see a lack of consideration for user input and a focus on personal projects rather than community needs.

For reference, you can view the list of my reported issues on GitHub for Lemmy here:

  • Lemmy Backend Issues: Link
  • Lemmy UI Issues: Link

Thank you for your attention, but I regret to say that I will not be engaging further with this project due to the lack of user-centric development practices.

  • wiki_me@lemmy.mlEnglish
    0·
    7 months ago

    The project is missing developers, if you want to then implement them yourself , or fund raise the money using a bounty platform like polar, some of the ideas are fairly controversial and linus law of trail and error apply here, with that said i think lemmy could benefit from a add on system like those wordpress and discourse have and those ideas can be checked out.

    Personally i had them accept some of my feedback before (e.g. i am the one who requested the ability to block an instance which got implemented despite one of the developers were against it and the other suggested i should switch instances).

    Just try to be prudent and persuasive .

    • The_Lemmington_Post@discuss.onlineOPEnglish
      0·
      7 months ago

      I don’t really mind whether or not the issues I suggested are implemented, but it frustrates me when they close the issues without listening to the input from the community.

      • 420stalin69 [he/him]@hexbear.netEnglish
        0·
        7 months ago

        Isn’t assessing the issue on the issue tracker “listening to input” though?

        Your options are

        • do it yourself and create a pull request
        • make a suggestion to the devs on the issue tracker, who have every right to reject it
        • start a discussion here if you believe a feature is important enough to have public debate

        That seems like a lot of options for listening to input to me.

        What exactly is missing that you want to see? How could you add what you see is missing?