Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.
If you’re a server admin, please defederate Meta’s domain “threads.net”
If you don’t run your own server, please ask your server admin to defederate “threads.net”.
Comment stolen from user “copygirl” from blahaj.zone:
It’s not as if something was preventing them from
and
here anyway.
So that part about being followed by a Threads user is just a bit stupid.
The danger is in them becoming an integral part of the network where people don’t bother to register at a normal instance, and then Meta pulling out and the network remaining half-dead.
Anyone can collect the data anyway, and I’m sure at least one person out there is already harvesting our Fediverse data.
Is there any sort of legal precedent that covers a situation where:
When I joint my instance, am I implicitly agreeing to any terms of service that exist on any instance that my instance decides to federate with?#
Someone actually asked an almost identical question on StackEx a while ago. (things may have changed since) From what I got from skimming the answer, is there is precedence, and it should be covered within the TOS of the hosting website/network (i.e. lemmy.world)
https://law.stackexchange.com/questions/7773/does-a-tos-also-apply-for-third-party-resources-on-a-website
Lemmy and mastodon profiles are public so I don’t know if privacy concerns are a problem unique to federation with meta considering they could just scrape your profile if they wanted the data that bad. I’d be much more concerned about small instance admins losing funding as users migrate to instances that federate with meta until threads and the big instances are the only ones left on the fediverse