265
petition: Defederate any instances that federates with threads proactivly , add threads.net on blocklists everywhere. (lemmy.ml)
submitted 2 years ago* (last edited 2 years ago) by ModdedPhones@lemmy.ml to c/fediverse@lemmy.ml
110 comments fedilink hide all child comments

I really want to nip threads in the bud. Besides blocking threads.net itself, defederate from any instances that do not. This is blatantly an EEE strategy and a united front is the only way to save what have been accomplished. Here is how Indivudals can do it on mastodont as an example to follow. https://hachyderm.io/@crowgirl/110663465238573628 Edit found this , https://fedipact.online/ please sign.

you are viewing a single comment's thread
view the rest of the comments
[-] animist@lemmy.one 7 points 2 years ago

Why shouldn't the instance owner make that choice? It's their hardware, time, money, and desire that made that instance. As soon as I start one, first thing I'm doing is making sure it never gets federated with fashy instances or meta.

[-] bluejay@partizle.com 5 points 2 years ago

Yeah this is a weird spot with who really wants to control things. I would argue anyone with a strong opinion one way or the other should probably self host. Those that can't will need to find an instance where their views line up with the instance admin.

Ultimately I think you're right though, instance admin has final say since uh, they're the admin. Anyone who wants to admin a huge instance probably would leave it open for users to decide though.

this post was submitted on 06 Jul 2023
265 points (100.0% liked)

Fediverse

17857 readers
1 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml