Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.

If you’re a server admin, please defederate Meta’s domain “threads.net

If you don’t run your own server, please ask your server admin to defederate “threads.net”.

  • Chozo@kbin.social
    link
    fedilink
    arrow-up
    5
    arrow-down
    7
    ·
    edit-2
    1 year ago

    what happens to existing culture on fediverse

    Likely nothing. If Threads users are problematic and Meta refuses to moderate them appropriately, then instances can defederate later.

    Doing it preemptively or forming a pact is just absurd, though. It’s treating the users of Threads as a threat, instead of Meta (who can and will still be able to harvest anything they want from the Fediverse, because that’s how ActivityPub works), and that’s not fair to them who didn’t ask to be thrown into our community in the first place.

    • sour@kbin.social
      link
      fedilink
      arrow-up
      13
      arrow-down
      2
      ·
      edit-2
      1 year ago

      defederate later

      problem often causes damage before is addressed

      pre block be safer

      threads users signed up for threads

      • Chozo@kbin.social
        link
        fedilink
        arrow-up
        4
        arrow-down
        4
        ·
        1 year ago

        If that’s how you want to run your instance, that’s your right to do. But for community-based instances, the users should have some say in the matter.

        Yes, I can move to another instance if mine decides to defederate, but that’s a lot of hassle that I’d have to go through because of a decision somebody else made for me, all because they can’t or won’t moderate themselves.

        • squiblet@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          If you don’t like decisions somebody else makes for you, then run your own instance.

          This isn’t meant to be snarky, btw, it’s a valid solution and one of the freedoms of the fediverse system.

      • yOya@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        3
        ·
        1 year ago

        problem often causes damage before is addressed

        pre block be safer

        You build a bridge. After awhile it might start to decay and without proper upkeep it might even collapse! Better to never build a bridge in the first place.

    • liquidparasyte@pawb.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Clearly you haven’t dealt with a Mastodon instance having a major defederation event.

      For most users, regardless of the validity of the defed, the user experience is terrible. Their social graph just suddenly, stops working, the people they follow can no longer see their posts, all because of the actions of a few bad actors or administration failures.

      This paired with the fact that maybe only Firefish or Misskey lets you (mostly) seamlessly migrate to a new instance with your data intact, and the lack of a standard way to see what followers you will actually keep when you migrate, means that the defederation experience is sucks, and migrating to a different instance to escape that is a pain in the ass.

      Meta has already shown it has piss poor moderation in the best of times, and actively boosts incendiary content in the worst of times, all while collecting, profiling, and exploiting your data. It’s literally inevitable that they’re going to break the rules of all but the free-est of free speech Instances, so for the privacy, safety, and headaches of everyone in the fediverse, we might as well save ourselves the trouble.**