429 Too Many Requests
wedistribute.org

This shouldn’t come as a huge surprise. Meta is moving forward with their plans for Theads and the Fediverse, and their adjusted terms reflect a new impending reality for Fediverse users.

  • @Ottomateeverything@lemmy.world
    13•1 year ago

    Public? Idk, maybe. I wouldn’t generally consider my IP to username to be public. Comment and post stuff, sort of. But even if it’s public, I still wouldn’t want Meta consuming it.

    • @Durotar@lemmy.ml
      16•1 year ago

      I wouldn’t generally consider my IP to username to be public.

      Are they talking about your IP address or the service’s? Does ActivityPub even share the user’s IP address with other nodes in the network? That’d be crazy, so I assume that it doesn’t. Then Meta can’t find out your IP address.

      • Oliver Lowe
        18•1 year ago

        Does ActivityPub even share the user’s IP address with other nodes in the network?

        No this is not in the specification.

        A malicious instance could in theory distribute this information but it would be non-standard. Of the 2 systems I’ve studied - Mastodon and Lemmy - neither do this.

        Are they talking about your IP address or the service’s?

        In this scenario they would be talking about the IP address(es) of the services.

        • @lolgcat@lemmy.ml
          4•1 year ago

          Thanks for the clarification. That claim seemed really off.

          I’ve assumed that what you see publicly is basically what’s synced. Obv. your instance can have a few more meta details on you, like IP, device info, possibly all the exif they’ve stripped from uploaded photos, but these things aren’t in the ActivityPub outbox

      • @Ottomateeverything@lemmy.world
        1•1 year ago

        If a Threads user posts an image, and Meta hosts it, and I scroll through my feed and see it, my client will hit their server for said image. And Meta can collect my IP.

        Meta basically invented this shit.