I'd like to invite you all to share your thoughts and ideas about Lemmy. This feedback thread is a great place to do that, as it allows for easier discussions than Github thanks to the tree-like comment structure. This is also where the community is at.

Here's how you can participate:

Post one top-level comment per complaint or suggestion about Lemmy.
Reply to comments with your own ideas or links to Github issues related to the complaints.
Be specific and constructive. Avoid vague wishes and focus on specific issues that can be fixed.
This thread is a chance for us to not only identify the biggest pain points but also work together to find the best solutions.

By creating this periodic post, we can:

Track progress on issues raised in previous threads.
See how many issues have been resolved over time.
Gauge whether the developers are responsive to user feedback.

Your input may be valuable in helping prioritize development efforts and ensuring that Lemmy continues to meet the needs of its community. Let's work together to make Lemmy even better!

(page 2) 50 comments

sorted by: hot top controversial new old

[–] PumpkinDrama@reddthat.com 4 points 1 month ago* (last edited 1 month ago) (3 children)

The decentralized nature of Lemmy, while appealing in theory, creates significant frustration in practice due to widespread instance blocking. Finding an ideal instance becomes a daunting task, as users must navigate a complex web of inter-instance politics and restrictions. This challenge is further compounded for those who prioritize factors like low latency or specific content policies. Lemmy's architecture heavily favors instance-level configurations, leaving individual users with limited control over their experience. The only reliable solutions seem to be either hosting a personal instance—a technical hurdle for many—or simply hoping that your chosen instance's admins align with your preferences and don't block communities you enjoy. This politicking ultimately undermines the platform's potential.

[–] Cataphract@lemmy.ml 2 points 1 month ago (1 children)

I'm not sure on the technical aspect but I think "instance blocking" should be an OPT-IN message sent to users of the instance. For example, say lemmy.world wanted to block lemmy.ml, hexbear, and reddthat. Each instance is added to a "Suggested blocked instance" setting in your profile and a message is sent to the user notifying them the opt-in option is available. Could have a whole list with descriptions besides the instances for why the suggested block option is there. Users would be informed with an actionable option and not automatically opted in. Could just be a toggle-able switch list in user settings.

load more comments (1 replies)

load more comments (2 replies)

[–] surewhynotlem@lemmy.world 4 points 1 month ago

Automatic OCR and filtering based on content in an image.

[–] homesweethomeMrL@lemmy.world 3 points 1 month ago (1 children)

It seems when a user is blocked and comments on a thread, any comments under that are also blocked. It should only be blocking that user, not the thread?

[–] infeeeee@lemm.ee 4 points 1 month ago (1 children)

It would be hard to get the context, and you could totally misunderstood the thread, e.g. from your hidden comment everyone get that replies are sarcastic, but you don't.

Maybe an "temporarily unhide blocked user's comment and replies" button to show the whole thread.

load more comments (1 replies)

[–] JTskulk@lemmy.world 2 points 1 month ago (1 children)

When I go to Lemmy, I'm not logged in until I click on a post to read, what's up with that? I used to stay logged in.

[–] FundMECFSResearch@lemmy.blahaj.zone 3 points 1 month ago (1 children)

sounds more like a potential browser/cache/extsnion thing than lemmy itself but what do i know

load more comments (1 replies)

load more comments