Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:UsernameProfile PictureIP AddressName of Third Party ServicePosts from profilePost interactions (Follow, Like, Reshare, Mentions)
Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:
!fediverse@lemmy.ml
Isn’t this just public information anyway, what’s the problem with them taking it?
if you post somewhere on the Fediverse, and some Threads user bumps into it, they can follow you, and that will send all that data to Meta. And it looks to include data well beyond the post the Threads user saw.
I wouldn’t generally consider my IP to username to be public.
Does ActivityPub even share the user’s IP address with other nodes in the network?
Are they talking about your IP address or the service’s?
In addition to [ActivityStreams] collections and objects, Activities may additionally be addressed to the special "public" collection, with the identifier https://www.w3.org/ns/activitystreams#Public.Activities addressed to this special URI shall be accessible to all users, without authentication.
if there will be some exceptions.
Everybody, please understand what defederating means. It will not stop the defederated instance from getting the data. It just means you don't pull theirs.
Yeah sure you can create a new user in other instance or selfhost an instance, but who would actually go through that?
not because of any existing tangible evidence in this circumstance
And if you’re here and pretending to care about data privacy at least try to do the bare minimum in understanding how the Fediverse works.
Oh, I do. I’m my own instance admin, I work as a senior architect and grasped the concept of Fediverse quite fast.
If you’re going to quote me I’d appreciate if you didn’t cut out relevant parts of it to fit your argument.
The “you” in my comment was a generalized “you”, not you specifically.
AUTHORIZED_FETCH
However: you are not a company that profits from vast amounts of data ingestion.
I don’t imagine Meta is bothering to scrape Lemmy
Meta says, for Threads to federate, they access the same data any instance does when it federates.
If I didn’t mind Meta scraping through all this, why wouldn’t I just use Threads?
Lemmy needs an option for a user to block an instance.