Fedigrow

655 readers

2 users here now

To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks

founded 7 months ago

MODERATORS

[email protected]

Is Lemmy.world centralization worth fighting against? (lemmy.blahaj.zone)

submitted 7 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

76 comments fedilink hide all child comments

Probably a very polarizing question.

On the one hand, having most of the users and communities on LW causes technical issues (see this post), and also gives the LW staff too much power over Lemmy as a whole.

On the other hand, with 18k MAU on LW out of 47k (https://fedidb.org/software/lemmy/), every community listed there has a much higher chance of visibility compared to an alternative hosted on another instance

History of LW controversial decisions

when they promoted Discord as an official communication channel (https://lemmy.world/post/3478399 - since then they created a Matrix chat)
when they blocked the piracy communities (https://lemmy.world/post/13320356 )
when they announced they might move from Lemmy to Sublinks (some comments from LW admins were quite controversial: https://lemmy.world/post/13899357 )
when they forced the media bias fact checker bot and discarded user feedback (https://lemmy.world/post/18775630 - to be fair, they since then removed it from [email protected] , it's still in [email protected] )
when they realized centralization of communities on LW was impacting the ability of other instances to stay up to date (https://lemmy.world/post/13967373 )
when they updated their rules following a power trip overtake of a community (https://feddit.org/post/2308651 )

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

[–] [email protected] 3 points 7 months ago

I mean, there's only so much you can do when your upstream is developed exclusively in Japanese (to the point the code comments are also in Japanese) with a focus on adding Reversi and a Suika Game clone into the software instead of refactoring so the same piece of code isn't duplicated in 10 different files split across the frontend and the backend and refuses to implement editing because they find it too hard when both major fork families (Firefish/Iceshrimp and Sharkey) have it and it works fine enough (alt text edits don't federate, but that's comparatively rare)