Threads' New Terms & Conditions Affects the Fediverse
wedistribute.org
Threads is moving forward with their Fediverse plans, and updated their Terms of Service to focus on "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.

    • moitoi@feddit.de
      0·
      1 year ago

      With the last court rule in Norway, Meta must ask your consent otherwise they can’t do anything. This is a huge issue for them on the fediverse. They must ask the consent of each European user what is nearly impossible. One solution is to filter were the instances are hosted. They don’t interact with the instance hosted in Europe. But, it doesn’t resolve the issue looking how the fediverse work. This is why Europe won’t see Thread.

      To prevent, instances should migrate to be hosted in Europe. The second is to change how fediverse works. It’s fondamental to add options to ban some instances not just defederate. It’s the tactic of putting meta and instance that federate with them on the side.

      This reminds me of the issue with some image content we spoke at the beginning of the week. I saw it like astroturfing. I would be surprised if this federation of Thread has a similar end.

  • moreeni@lemm.ee
    0·
    1 year ago

    If someone had any doubts about federation with Threads, they shouldn’t by now. Facebook is trying to turn Fediverse into Shittyverse and Fedizens should resist that

    • Krapulaolut@sopuli.xyz
      0·
      1 year ago

      Lemmy needs an option for a user to block an instance.

      If your local instance is not going to defederate with meta then an average user can’t do anything about it.

      Yeah sure you can create a new user in other instance or selfhost an instance, but who would actually go through that?

      • Rikudou_Sage@lemmings.world
        0·
        1 year ago

        Everyone should change their instance to one they agree with. If you don’t want to be federated to Meta, go to an instance that’s not federated.

        User blocks are pretty much a simple filter, Meta will still have your data if you block them individually instead of defederating.

        • zaphod@feddit.de
          0·
          1 year ago

          Sounds great, but in the end it just means everyone has to host their own instance. That could be interesting, but I doubt everyone would want to do that.

  • maynarkh@feddit.nl
    0·
    1 year ago

    Stupid question, couldn’t instances just say they don’t allow scraping specifically from Facebook in their ToS and then report them for GDPR violations if they do?

    As in say that have the ToS says that “we’ll give your data to other instances because that’s how the Fediverse works, we won’t give your data to Facebook” and also “Facebook is not allowed to federate, and is not allowed to pull data”.

    Then just say that your data subjects don’t consent to any data pulling by Facebook, and Facebook scraping your system even through ActivityPub is a violation of GDPR.

    • Razp@lemm.ee
      0·
      1 year ago

      But GDPR is the European thing, and Threads isn’t even available in Europe.

      • Ctri@beehaw.orgEnglish
        1·
        1 year ago

        GDPR is a protection that applies to European citizens, regardless of where they’re situated. companies don’t get a pass because they blocked IP addresses coming from Europe.

        now, enforcement outside the EU is a challenge, but the law is written in such a way that it covers the personal info of every EU citizen regardless of location.

      • Squizzy@lemmy.world
        1·
        1 year ago

        If there service is affecting a service in the EU then they will have to abide by Gdpr. Fact is if your server is in the EU and they scrape it they are active in the EU.