this post was submitted on 06 Jul 2023
128 points (69.4% liked)

Fediverse

17849 readers
2 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
128
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
107 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
[–] SlippiHUD@lemmy.world 9 points 1 year ago

I'm all for blocking Threads as an instance or user, but blocking instances that choose to federate with threads is going to leave a lot users who when Threads breaks its compatibility with Activity Pub with no social graph to keep them tethered to ActivityPub.

Threads can't get the data we're worried about it collecting from federation, they can only get it from you installing/using their site or their app. So don't do that.

I think the difference between this EEE and say XMPPs EEE is Meta/facebook is widely seen as a cancerous entity that people who are already here aren't going to want to use, and when they break compatibility few people are going to want to switch to their service as long as there's still enough people here to talk to.

Not to downplay the threat of EEE, we need to remain vigilant. Our best defenses are preemptive defederation or shitposting how we never see ads.