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

you are viewing a single comment's thread
view the rest of the comments

[–] 1chemistdown@kbin.social 2 points 1 year ago (2 children)

Threads still hasn't implemented ActivityPub

I’m on kbin.social and when I go to /d/threads.net it is very active. I would not be able to go there if they haven’t implemented activitypub and federated.

[–] static@kbin.social 2 points 1 year ago

/d/ is a domain, not an instance

If you look at the activity of https://kbin.social/d/threads.net those are hyperlinks to threads.net

[–] FaceDeer@kbin.social 1 points 1 year ago

Neat, this is news to me. Last I heard they hadn't pulled the trigger on that. The sky doesn't seem to have fallen as a result, yet.