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.

  • RxBrad@lemmings.worldEnglish
    11617·
    1 year ago

    For all the fucks’ sakes, people.

    Yes, Meta sucks. But at least get your shit together before you all start falling over each other to say how these ToS changes mean that Zuck has now given birth to Time Travelling Baby Hitler or some shit.

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

    And as far as LEMMY.world defederating from Threads… LEMMY. That’s like saying Twitter (or W, or whatever the hell it is now), shouldn’t put Facebook posts in its timeline. Threads is a Mastodon concern. Not Lemmy.

    🤦‍♂️ Ya fuckin’ tinfoil hat nerds. I love you all. But God damn.

    • 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.

    • paraphrand@lemmy.worldEnglish
      4·
      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.

      • RxBrad@lemmings.worldEnglish
        81·
        1 year ago

        You can follow @user@instance or @community@instance on Mastodon. But you just get blasted by every post and comment, one by one, in unthreaded CHRONOLOGICAL order.

        So while you can do it, the question is… should you?

        • 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.

    • 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.