Please post one top-level comment per complaint. Then others can reply with ideas or existing GitHub issues that could address that complaint. This helps identify both common complaints and potential solutions.
You can also reply on !polls@reddthat.com to better organize the discussion:
https://reddthat.com/post/5049064
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. I propose creating a quarterly pinned post on Lemmy asking users for complaints and suggestions. This way, developers can better understand the community’s biggest pain points and what to focus on. The goal is to provide constructive feedback so developers can prioritize the most pressing issues.
Please keep discussion productive and focused on specific problems. Avoid vague complaints or feature wishes without justification. Our aim is to give developers clear insights into issues impacting users most.
Sure, and that’s great to know and remind people. You and I know how to workaround the issue, but the experience is broken for people who don’t. People who are new to lemmy don’t know that they need to install a browser extension. And that’s why this isn’t an acceptable solution. This needs to be a very high priority, and should be the next thing they work on after 0.19 release.
If there is an extension for it, it means that it can be implemented fully client-side.
If it can be implemented client-side, it shouldn’t be implemented server side. It just makes things harder to scale and more expensive to run.
Maybe this could be a feature request on lemmy-ui, but not for lemmy itself.