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.
I would agree with you if threads didn’t choose to avoid market with decent consumer protection laws, EU.
They aren’t launching at EU for a reason, and that’s good enough for me to take a stance against them.
Just because they haven’t launched in the EU yet doesn’t mean they won’t. They were clearly rushing to get this out the door. I’d be absolutely shocked if they don’t go to the EU since Facebook and Instagram are there already.
Facebook is in a lot of shit with EU right now because of GDPR non compliance. They are at a risk of just getting flat out booted from here if they don’t fix their shit.
That combined with the upcoming Digital Markets Act means they might not get a chance to launch here at all
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.
@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/
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