this post was submitted on 06 Jul 2023
132 points (67.6% liked)

Fediverse

17788 readers
16 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
[email protected]
[email protected]
132
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 [email protected] to c/[email protected]
108 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
[–] QuaternionsRock 5 points 1 year ago (2 children)

Won’t they have to comply with at least some EU laws in order to become federated? If EU residents can interact with Threads via another instance, they’ll still be on the hook for all of that mirrored data.

[–] [email protected] 1 points 1 year ago

@QuaternionsRock
AFAIK Yes, federated servers have to comply with local laws, including the EU's data protection regulations. Federated instances are responsible for any mirrored data they handle, even from EU residents. But they’d see the public data only since it’s cashed in the instance server. I think. See: https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/

[–] [email protected] 1 points 1 year ago

It could also be that the instances federating with Threads are on the hook, because they're giving data on EU residents to a third party