Fear, loathing, and excitement as Threads adopts open standard used by Mastodon

Ansgar@lemmy.world to Technology@lemmy.world – 143 points –
Fear, loathing, and excitement as Threads adopts open standard used by Mastodon
arstechnica.com
23

You are viewing a single comment

Yeah, Threads can do all it wants. I've set a preemptive block. I want nothing to do with Threads. Of course, I cannot control what other instances decide to federate and get my content that way. But I won't make it easy for them.

What steps did you take to preemptively block it? I want nothing to do with Threads either but am a bit confused on what I should be doing. Is there a list of instances who defederated from threads or something?

I run my own instance so I simply added a block in the instance configuration. If I had to hazard a guess, I would say the folks at lemmy.world have most likely done the same.

No need to guess, just look at https://lemmy.world/instances

If anything was being blocked you would see it there. AFAIK lemmy.world does not normally block/defederate anyone as a standard policy (including threads.net).

If you want an example on the other end of the spectrum go see https://beehaw.org/instances they are currently at 405 instances being blocked including threads.net.

I don't think any Lemmy instance is going to have to block Threads.

Mostly because Lemmy doesn't support microblogging. Kbin does. And the big one is Mastodon.

All because ActivityPub is not a monolith, different services use different parts of the standard.