- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
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.
Yes, but do you analyse this information to sell it to advertisers? Will you start posting sponsored content based on this information? And will the money you collect benefit the community you live in, or will it buy you another politician?
But it’s still no news in any way. This article is simply saying “Threads still plans to federate, eventually”, nothing else changed.
Altering the language of a service policy (or, writing a new one) is usually a good indication that something is indeed about to change at a larger level.
It’s also an indication they’re following US law. They can’t collect data without stating it.
I’m gonna play Devil’s Advocate here…
What’s to stop them from scraping the Fediverse without federating? If they really want the data, they could very well find a way. At least they’re spelling it out here and announced an attempt at proper federation.
The article discusses this, a bit. One of the other platforms is considering an enhancement to require request signatures on non-ActivityPub APIs, I.E. Meta can make unsigned requests, where the server doesn’t know who they’re from, but only get minimal (or no) data back, or Meta can make signed requests, and instance owners get to decide what data (if any) they’re okay with sharing to Meta, based on Meta’s privacy policies. Beyond API’s, you’re talking about web scraping, which is something the industry has been handling for decades.
It also says exactly what they’re planning to collect for starters. That was news to me.
Again, that’s just what federates and automatically gets saved. You could have gotten that information by checking any proper Mastodon instance privacy policy or reading about the Fediverse on a more technical level.
It still news to me.