Threads new ‘Supplemental Privacy Policy’ (Instagram link) says they’ll collect (from fediverse users interacting with Threads users):

  • Username
  • Profile Picture
  • IP Address
  • Name of Third Party Service
  • Posts from profile
  • Post interactions (Follow, Like, Reshare, Mentions)

From the linked article:

“Granted, these sound like basic table stakes for federation to work well within the Fediverse. Most Mastodon servers collect roughly about the same amount of data for basic features to work correctly. But again, Meta is first and foremost an advertising and data harvesting company…”

  • ryan@the.coolest.zone
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    1 year ago

    I realize we’re all on the “fuck Meta” train (and yes, fuck 'em), but I will note that my kbin instance is also collecting all of that from y’all just due to how federation works (except for IP address I believe).

  • nebula42@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    1 year ago

    And this is exactly why I swapped instances, because

    1. I don’t want my family seeing my masto account, it’s a safe space online for me and
    2. I don’t wanna support threads being apart of the fediverse.
      • nebula42@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        I personally migrated to toot.site, but any of the instances listed on fedipact.online aren’t federating with threads if you don’t wanna go on toot.site for whatever reason.

    • Otter@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I don’t want my family seeing my masto account, it’s a safe space online for me and

      Wouldn’t it be better to open one without your name in that case?

  • Makr Alland@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Regarding the IP address, how are they going to get it? I assumed that servers wouldn’t pass them along to other nodes, isn’t that the case?

    • Otter@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I thought IP addresses are accessible to all 3 instances (where the account is, where the post is made, and where the post is viewed)

      Otherwise it would be hard to deal with spam bots from an instance, and the only avenue would be to defederate.

      The issue here is that other instances use the IP address to prevent spam and they don’t track it unless they need to

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        No, IP addresses of the users are only known to the instance you connect to directly / have an account on.

        Spam is managed on a user account level, not user IP level.

  • wutBEE@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Honestly, Meta federating is probably the best chance of Mastodon becoming accessible to the larger public, and I’m all for anything that brings us closer to a world where Twitter isn’t top dog.

    And I say this as someone who’s rooting for BlueSky/ATProto, not Mastodon.

    • nilloc@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      Meta isn’t connecting to Mastodon to make Mastodon better, it’s doing it to get free users for Threads. As soon as it has enough Treads-first users, it will break or stop supporting Mastodon and most users of Mastodon will wonder where all the content went.

      This is behind lots of tech companies’ support for open standards. The adopt, modify, dominate, and then drop the open standards and move on.