Threads' New Terms & Conditions Affects the Fediverse
wedistribute.org
Threads, Meta's new microblogging platform, is updating its terms to focus on data collection from "Third Party Users".

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.

    • Hazelnoot [she/her]@beehaw.orgEnglish
      24·
      1 year ago

      I agree that this is nothing to panic over, but I want to clarify that Lemmy is not safe from this. Lemmy and Mastodon both use the same protocol (ActivityPub) and that’s also the protocol that Threads will use to federate. Just as Mastodon users can like, boost, and reply to Lemmy threads / comments, Threads users will be able to do the same. That’s why it’s important to defederate Threads on all ActivityPub-enabled instances.

        • Hazelnoot [she/her]@beehaw.orgEnglish
          2·
          1 year ago

          Defederating actually does stop Meta from accessing data (at least through ActivityPub) if you enable AUTHORIZED_FETCH / similar. That setting requires remote instances to authenticate themselves, which prevents blocked instances from querying anything. IIRC, Lemmy either already supports or plans to support that same feature.

          Meta could, of course, just use web scraping, but that can be prevented with DISALLOW_UNAUTHENTICATED_API_ACCESS. Although admittedly, I don’t think Lemmy has this feature yet.

      • Nougat@kbin.social
        5·
        1 year ago

        kbin includes a “microblog” feature which is a mastodon-like implementation of ActivityPub.

          • Nougat@kbin.social
            2·
            1 year ago

            I don’t use it, so I’m not super clear on it. It does feel like a bit of an afterthought.

            I do know that I’ve interacted with Mastodon users in fediverse comment threads via kbin in the “regular, reddit-like” interface. My understanding is that APub is APub is APub, and the client implementations define the format you see content in, and implement or do not implement different APub features based on how the developer(s) want to shape their client.

    • Zak@lemmy.world
      15·
      1 year ago

      Threads is not Mastodon. Both are microblogging, while Lemmy is better described as a forum or link aggregator.

      It’s possible to interact with Lemmy from Mastodon. I do so regularly by tagging a community in myastodon post. Following a community from Mastodon is also possible, but the UX is rough.

    • Ottomateeverything@lemmy.world
      63·
      1 year ago

      Meta says, for Threads to federate, they access the same data any instance does when it federates.

      Okay, but like, I don’t want Meta consuming that data? At least if they wanted to scrape through reddit to put that together, they’d be going out of their way. This data is now just coming through the same API “for free”.

      If I didn’t mind Meta scraping through all this, why wouldn’t I just use Threads?

      This is exactly the kind of shit that pushed me here - I don’t want Meta sifting through all my shit. Its unlikely that some other instance host is going to start building psychological advertising profiles on me and sell it to the highest bidder. But you bet your ass Meta will try.

      • JoYo@lemmy.mlEnglish
        82·
        1 year ago

        If I didn’t mind Meta scraping through all this, why wouldn’t I just use Threads?

        I’m curious what precautions you have taken to prevent web scraping of your posts.

          • JoYo@lemmy.mlEnglish
            31·
            1 year ago

            They admitted to federating for research back around bluesky’s announcement.

            If you don’t want your data scraped you’ll need to use e2ee.

    • paraphrand@lemmy.worldEnglish
      31·
      1 year ago

      You can follow lemmy stuff via Mastodon accounts. 🤔 No? Do I not quite understand how and why that works?

      Your point about slowing the fuck down still stands though.

        • paraphrand@lemmy.worldEnglish
          2·
          1 year ago

          Ok, that was my experience. I haven’t found a great context/use case for it yet.

          It does seem a client could be made that uses the functionality. Or a purpose deployed instance or community could make use of it too.

          But I agree, it’s hard to imagine a good use. And your point still stands about how panicking is unhelpful.