Comment on Fear, loathing, and excitement as Threads adopts open standard used by Mastodon
housepanther@lemmy.goblackcat.com 1 year ago
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.
Moogosa@lemmy.world 1 year ago
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.
housepanther@lemmy.goblackcat.com 1 year ago
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.
brickfrog@lemmy.dbzer0.com 1 year ago
No need to guess, just look at 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 beehaw.org/instances they are currently at 405 instances being blocked including threads.net.
housepanther@lemmy.goblackcat.com 1 year ago
Ah thanks for letting me know about that. I thought the instances view was only for admins.
chaogomu@kbin.social 1 year ago
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.
housepanther@lemmy.goblackcat.com 1 year ago
I’ve preemptively blocked threads on my Mastodon instance as well.