bark.lgbt, meow.social, tech.lgbt, yiff.life, queer.party, todon.eu...
Oh, me? I'm just writing down instances that got banned on Threads for "Violating community guidelines" while all they did was be too queer-friendly or too leftist for Facebook techbros
@fbievan@social.fbievan.live https://www.threads.net/moderated_servers has a full list that got defederated from Zucc's newest social media "invention", Threads
While a lot of instances there are actually worth defederating (mostly nsfw and sometimes even the illegal kind), reading the full list carefully does make a person crack a laughter or two
@witix wait, what? What specifically did they do that got them banned?
@sillyinternetcreatur the fun part is: we don't know
(the full list is at https://www.threads.net/moderated_servers, and while most of these are actually just nsfw, the reason why instances like the ones above are put in the same basket is knowledge Zucc will probably take to his grave)
@getimiskon@fedi.getimiskon.xyz to the instance admins it's probably a relief anyway since being federated with Threads would most likely mean a lot more CPU strain
@getimiskon checks username
checks instance name
OOOOOOOOOOOOOOOOOOOOOOH
@witix ah, yeah it's probably for nsfw reasons then. That would be my bet. Allowing nsfw content, even if it's behind a content warning.
@sillyinternetcreatur That honestly sounds like a very poor excuse because there'll definitely be more nsfw content on Threads itself, given it's moderation (probably ghost of an ancap philosopher)
Also as far as my knowledge goes, every instance allows nsfw content if it's behind a CW unless they can't do that for hosting provider reasons, correct me if I'm wrong though
@Haijo7@snac.haijo.eu tbh most of the instances "banned" by Threads already fediblock it anyway
@witix there is also social.tchncs.de, void.rehab, worm.pink, raru.re, blob.cat, bungle.online, kolektiva.social, todon.nl, shark.community…