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!

you are viewing a single comment's thread
view the rest of the comments

[–] PumpkinDrama@reddthat.com 4 points 1 month ago* (last edited 1 month ago) (4 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.

[–] OpenStars@discuss.online 1 points 1 month ago

Example 1: when one side wants to bully the other, but the latter does not wish this, how do you solve this problem? Defederation it is then.

Example 2: when someone claims that the Tiananmen Square massacre did actually happen, that user gets blocked from all communities, including those they have never heard of, on lemmy.ml. This is not so rare - and this is straight from the Lemmy developers themselves, i.e. a feature not a bug. It does no good to pretend otherwise.

Example 3: when people refuse to label their kiddie porn properly, others must label it for them, or risk getting into trouble themselves, bc regardless of what some other website chooses to host, the federation model says that if your instance federates with it, then it is content that you are sharing as well. Though actually, I find the Fediverse mostly friendly in how it labels NSFW content, yet it refuses to label toxicity in a like manner - e.g. the brigading attempts organized on hexbear against other communities on different instances. If only a label could be affixed to Chapotraphouse, like "beware ye who choose to enter here...":-).

I find your comment extremely biased towards your own POV and desires, but overall there is much more subtlety and nuance in interpersonal connections, e.g. sometimes women choose the bear, and rather than say that it is "silly", it might behoove people to listen to why that choice may have been made?

load more comments (3 replies)