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.

    • Sean Tilley@lemmy.mlOPM
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      Altering the language of a service policy (or, writing a new one) is usually a good indication that something is indeed about to change at a larger level.

      • danielton@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        1 year ago

        I’m gonna play Devil’s Advocate here…

        What’s to stop them from scraping the Fediverse without federating? If they really want the data, they could very well find a way. At least they’re spelling it out here and announced an attempt at proper federation.

        • JakenVeina@lemm.ee
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          The article discusses this, a bit. One of the other platforms is considering an enhancement to require request signatures on non-ActivityPub APIs, I.E. Meta can make unsigned requests, where the server doesn’t know who they’re from, but only get minimal (or no) data back, or Meta can make signed requests, and instance owners get to decide what data (if any) they’re okay with sharing to Meta, based on Meta’s privacy policies. Beyond API’s, you’re talking about web scraping, which is something the industry has been handling for decades.

    • El Barto@lemmy.world
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      It also says exactly what they’re planning to collect for starters. That was news to me.