cross-posted from: https://lemmy.world/post/3191819
cross-posted from: https://lemmy.ca/post/3305498
After a thread was made in [email protected] asking to defederate from lemmy.dbzer0.com for “the facilitation of piracy, and copyright infringement in general which is illegal”, the admins of lemmy.world deleted it prompting discussions on !asklemmy[@]lemmy.ml and !piracy[@]lemmy.dbzer0.com.
Did they not know that piracy was a community before this post? It often hits front page, and is one of the very active communities. Even Reddit still has a piracy community ffs. At least take some time and/or get some feedback from the users before you take some off the cuff rash decisions.
Maybe they decided that they couldn’t maintain deniable plausibility of not knowing it existed with it being directly brought up in their support community
These are individuals volunteering their time to host a community and they don’t have deep pockets so they have to shield themselves from liability. I don’t blame them from deleting content from piracy, drug use, or porn communities because they could be held liable for the content. Even if it’s within their rights and they are not technically liable, any lawsuit will bring these small Lemmy communities down immediately
LW admins proving as incompetent as Reddit admins. Let’s not forget they can barely keep the site up.
I get that you’re upset about the piracy community being blocked, but calling the lemmy.world admins incompetent is completely uncalled for. The site’s been hit with intermittent DDOS attacks, and since Lemmy is a fairly new platform there aren’t a lot of tools to mitigate these attacks. Hence the need for cloudflare.
Being the biggest instance, lemmy.world gets to experience all the growing pains of scaling up Lemmy first. The lemmy.world admins have been on top of things and open about status updates throughout all this. They’ve even found solutions to issues in the Lemmy code and issued pull requests to implement them.. And they’re doing this as unpaid volunteers.
Cool!
How have you managed these issues on your instance?