This shouldn’t come as a huge surprise. Meta is moving forward with their plans for Theads and the Fediverse, and their adjusted terms reflect a new impending reality for Fediverse users.
I don’t know what you’re getting excited about here; this is all publicly available information which Facebook could scrape at any time they wanted (federated or not), even right this very second.
Shhh, I train my AI here.
deleted by creator
With the last court rule in Norway, Meta must ask your consent otherwise they can’t do anything. This is a huge issue for them on the fediverse. They must ask the consent of each European user what is nearly impossible. One solution is to filter were the instances are hosted. They don’t interact with the instance hosted in Europe. But, it doesn’t resolve the issue looking how the fediverse work. This is why Europe won’t see Thread.
To prevent, instances should migrate to be hosted in Europe. The second is to change how fediverse works. It’s fondamental to add options to ban some instances not just defederate. It’s the tactic of putting meta and instance that federate with them on the side.
This reminds me of the issue with some image content we spoke at the beginning of the week. I saw it like astroturfing. I would be surprised if this federation of Thread has a similar end.
Can someone please explain why this matters. Almost all madtadon instances are public and can be data mined by any company. Why is it such a large concern if threads is able to see a portion of the posts on the fediverse like any other mastadon instance. To me the only thing threads federation changes is allowing me to view posts on threads without the amount of MS my cursor is over the podt being data mined to know what food Ill be craving in a week.
