This Threads thing really does just highlight why "block instance" needs to actually do something it doesn't do. Muting a whole instance, while viscerally satisfying on some level I'm sure, doesn't really solve the "I'd rather not interact with places that are going to ship my posts on to Meta, at all." So now I'm in an awkward position of having to ask them to server block MY account on their federated with Meta instance. Inefficient, overtly-dramatic, super annoying.
Conversation
Notices
-
Embed this notice
AnarchoNinaWrites (anarchoninawrites@jorts.horse)'s status on Wednesday, 27-Mar-2024 06:22:57 JST AnarchoNinaWrites - AnthonyJK-Admin repeated this.
-
Embed this notice
AnarchoNinaWrites (anarchoninawrites@jorts.horse)'s status on Wednesday, 27-Mar-2024 06:23:47 JST AnarchoNinaWrites Like, I get it, this is a wet dream for a bunch of weird techbros; your place at the table. I'd just rather not be dragged to that table with you and the nature of federation makes that pretty much impossible. I'm not in a position to ask MY admin to do anything about it since that would sever so many connections for other people, who may not care.
But *I* very much care. I abandoned my zombie facebook and instagram accounts for a reason.
AnthonyJK-Admin repeated this. -
Embed this notice
AnarchoNinaWrites (anarchoninawrites@jorts.horse)'s status on Wednesday, 27-Mar-2024 06:23:53 JST AnarchoNinaWrites I would of course miss many of you who remain on instances that federate with threads, but not as much as I'm GOING to miss *not* feeding Zuck's dragon.
-
Embed this notice
for a day, while . . . (cgsines@mastodon.world)'s status on Wednesday, 27-Mar-2024 06:23:59 JST for a day, while . . . if you go, please let us know where you're going