this post was submitted on 06 Jul 2023
130 points (70.4% liked)

Fediverse

17729 readers
124 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
130
petition: Defederate any instances that federates with threads proactivly , add threads.net on blocklists everywhere. (lemmy.ml)
submitted 1 year ago* (last edited 1 year ago) by ModdedPhones@lemmy.ml to c/fediverse@lemmy.ml
95 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
[–] CheeseQueen@lemmy.blahaj.zone 19 points 1 year ago (2 children)

I must genuinely ask? What does this accomplish, a lot of instances being split apart because one federates with meta and the other doesnt, its not like the meta posts are gonna make it to your instance if you defederate meta, so you are really just splitting the community over nothing. Privacy wise, activity pub is public, by design, so they can just already pull all the information it exposes, and likely do. And finally? How does this stop EEE?

[–] BreakDecks@lemmy.ml 6 points 1 year ago

How does this stop EEE?

I suppose if we burn our own community to the ground the moment we're Embraced, there won't be anything left for Meta to Extend or Extinguish.

[–] mvirts@lemmy.world 1 points 1 year ago

I agree that defederation doesn't solve the problem, the nice thing about federation is everything has an instance associated with it so as a user it is easy to know the source, and although we may not have easy solutions now, the data to provide instance blacklisting to clients is there. Personally I think the better way to neutralize threads would be a strict non-commercial license on all content served from an instance.