No Mark. Let's not. #fediblock
You know, it is a good thing, that Meta is creating an ActivityPub/Fediverse compatible social media system with Threads because it instantly legitimizes the protocol. That said, it could be argued Microsoft did the same for HTML/HTTP when it built a web browser in the 1990s, but I still managed to avoid using Internet Explorer except when absolutely necessary over most of the past 30 years. The important thing is the underlying open system and freedom to choose.

@chris
#AltTxt4You
Screenshot from some app somewhere with a round profile pic of a pasty android-looking techbro with the handle "zuck", which coincidentally rhymes with the first word that pops into my head whenever I see that vile git's face. Anyway... I digress...
"zuck" apparently said the following:
Let's do this. Welcome to Threads. (fire emoji)

To that pandering drivel, apparently there were (at the time the screenshot was taken) 373 replies, and 1.1k likes.

@chris
This is an excellent point.

Yes - good - legitimize the protocol. Excellent.

And - fortunately - the rest of the ActivityPub ecosystem is pretty mature by this point, and those of us who are on instances that want to have nothing to do with Fark Muckerberg already have the tools to stem the tide of sewage which inevitably cometh whence.

@kelvin0mql exactly. And in this nascent moment when the Fediverse is so small having Threads around will feel like there is a bull in our china shop. Other servers and services big and small will come and go but as long as the protocol survives and is improved then we will have gotten to a new, better, place.
@chris Embrace, Extend, Extinguish is so ingrained in the history of silicon valley that I'm surprised anyone sees that as anything but an opening attack move. Google did it with XMPP too.
@ve3mal That is a risk for sure, but not one we can actively stop. At some point it is all up to how internet users and service providers react. I see there being enough momentum already behind the protocol itself that it is more like HTML than XMPP.
@chris Federation is the lever they use. HTML isn't federated, so the "fediverse" is more like XMPP. When one large company has enough control, and they build-in enough incompatibility that it drives users to their particular instance to avoid UX frustrations, they eventually just de-federate and rely on the network effect to kill off everything else.
@chris
Yeah. Is this going to be Google and XMPP or AOL and HTTP? Or somewhere in between? I wish I knew. They have a lot of distrust to overcome, but our trust may not even be relevant to them.
@ve3mal