Someone has initiated a social.coop vote about defederating from #Threads. I’m voting not to.
I considered making my vote a blocking vote since there’s a good chance I will leave social.coop if it passes, but I’m not sure I can make a compelling case it’s against our core principles, per se. Just not what I want from my server. I will be pretty bummed if it comes to that.
https://www.loomio.com/p/Kwl1mPCi/shall-we-defederate-from-meta-s-threads-net-
Here’s what I wrote:
If threads.net becomes a way that my friends use the Fediverse, which I think is likely, I would probably leave social.coop if I couldn’t interact with them. I would be pretty sad about that—I’ve been here since 2017!
Separately, while I share the skepticism of Meta, I find something distasteful about excluding Meta’s users, who are numerous and imo more diverse than the Fediverse currently.
I am less afraid of EEE than others. I think we’re quite resilient against it.
@harris The problem is that Threads is likely to be very large - perhaps larger than the rest of the Fediverse combined. With such a large userbase, and likely with contributions to the ActivityPub protocol, Meta will have a large amount of sway over the platform(s) as a whole.
If instances were more united and coordinated, I would agree that we are resistance to E³. However, we aren't, and because of that we do not have a large say in how things progress.
@harris It's never really a direct line. It would be more like a "death by a thousand cuts" as Meta influences and changes the Fediverse.
I don't personally think blocking is the answer, mind you. I think banding together and collectively coordinating responses is.
Harris Lapiroff
Fenn Martyn