Afaik, whenever an Activitypub instance has defederated from another it has always had to do with some combination of bad user behavior, poor moderation, and/or spam. Are the various instance admins who have decided to preemptively block threads.net simply convinced that these traits will be inevitable with it? Is it more of a symbolic move, because we all hate Meta? Or is the idea to just maintain a barrier (albeit a porous one) between us and the part of the Internet inhabited by our chuddy relatives?

(For my part, I’m working on setting up my own Lemmy and/or Pixelfed instance(s) and I do not currently intend to defederate.)

  • valaramech@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Honestly, I feel like the bigger issue is the immense flood of content that’s going to pour out of Threads. I’m not sure if many of the self-hosted instances will be able to federate with it and continue to function.

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

      This seems like a more viable argument than much of the EEE stuff, in regards to Threads v Mastodon.

      But I simply don’t understand the ins-and-outs of how Threads stuff gets federated, and how much toll it would actually put on other servers.