So - counter-example. I’m working with a UK organisation that currently still uses Twitter. I’m trying to persuade them to start their own Mastodon instance instead. Being able to reach Threads users, in addition to Masto uses would clearly be substantial selling point of setting up a Mastodon server - given the size of the Threads userbase - and much preferable to them starting a Threads account.
It would be right now, but the first step of Embrace Extend Extinguish is that: Embrace. Opening up to threads now might be extremely detrimental to the fediverse in the future, in the same way as happened with XMPP.
By this argument nothing should ever interoperate with anything else because clearly that’s the first step toward destruction.
I’m writing this on Firefox, which interoperates with Chrome and Edge. Oh no! We need to get these browsers operating on incompatible protocols stat, before they all extend and extinguish each other.
In reality, “embrace extend extinguish” is not a law of nature. XMPP is not ActivityPub. They are separate things with separate circumstances. Did you know that XMPP is actually still functional and open and you can download clients and servers that use it to this day? The stories about how Google “destroyed” it have become wildly distorted folklore at this point.
I think one of the points - and strengths - of the Fediverse is that a single person or instance can’t make that choice for others.
Most lemmy instances defederated that Facebook BS factory right after it was announced.
True, a single person cant, but everyone agrees that Facebook can go fuck itself and that it ain’t getting the stuff from us.
So - counter-example. I’m working with a UK organisation that currently still uses Twitter. I’m trying to persuade them to start their own Mastodon instance instead. Being able to reach Threads users, in addition to Masto uses would clearly be substantial selling point of setting up a Mastodon server - given the size of the Threads userbase - and much preferable to them starting a Threads account.
Thats a different story.
How so? It’s a direct benefit of federation
It would be right now, but the first step of Embrace Extend Extinguish is that: Embrace. Opening up to threads now might be extremely detrimental to the fediverse in the future, in the same way as happened with XMPP.
By this argument nothing should ever interoperate with anything else because clearly that’s the first step toward destruction.
I’m writing this on Firefox, which interoperates with Chrome and Edge. Oh no! We need to get these browsers operating on incompatible protocols stat, before they all extend and extinguish each other.
In reality, “embrace extend extinguish” is not a law of nature. XMPP is not ActivityPub. They are separate things with separate circumstances. Did you know that XMPP is actually still functional and open and you can download clients and servers that use it to this day? The stories about how Google “destroyed” it have become wildly distorted folklore at this point.
God forbid if Microsoft decided to use open document formats by default and to phase out docx - it would clearly be the first step of EEE!
God forbid companies use the world wide web - they’ll run it down the gutter!
The standards must be protected at all costs - may they never see mass adoption.
It might, yes. But I think the risk can be managed, with defederation if need be. I don’t think existing Fediverse users are suddenly going to defect.