this post was submitted on 19 Dec 2023
849 points (82.9% liked)
Fediverse
28465 readers
455 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think you’re fundamentally misunderstanding how data is handled in federated systems. When an account from Threads interacts with your post or you interact with a Threads post, information is exchanged exclusively through Actions sent between the servers- never to or from your or their client and another server. It looks like this:
Client <=API=> Instance <=Action=> Instance <=API=> Client
They don’t get any information that isn’t already available publicly to any random user on your instance- no IP address or anything otherwise. Threads’ mobile app data collection has no bearing on their ability to collect information on you.
Edit: To be clear- there is theoretically a set of protocols in the ActivityPub spec that allows for direct client to server communication (unimaginatively called ActivityPub Client-to-Server), but it hasn’t been adopted by any current Fediverse software implementation that I’m aware of.