• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • Ethan@lemmy.worldtoFediverse@lemmy.worldLemmy.world Should Defederate with Threads
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    11 months ago

    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.






  • Ethan@lemmy.worldtoFediverse@lemmy.worldLemmy.world Should Defederate with Threads
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    11 months ago

    They could already get all of your profile and post info… I could get that right now through the free api for every account on this and every other thread with a couple dozen lines of code.

    Edit: I’m also unclear on how they would ever get your IP- if you never use their frontends the only IP they’d have access to is that of the server your account is hosted on… Which would only be your own IP for the extreme minority who host their own instance from their personal internet connection, and Meta wouldn’t be able to tell that that’s the case anyway.