In quali modi il Fediverso può reagire all'irruzione di Threads?
Lo scossone per il #Fediverso sarà enorme: guardando alla sproporzione di risorse tra #Meta e l’universo federato, sembra chiaro che tutto ciò porterà a una distruzione del Fediverso per come lo conoscevamo.
Facebook/Meta starts talking about the "Extend" phase of Embrace, Extend, Extinguish as predicted:
"“You could imagine an extension to the protocol eventually — of saying like, ‘I want to support micropayments,’ or … like, ‘hey, feel free to show me ads, if that supports you.’ Kind of like a way for you to self-label or self-opt-in. That would be great,”
Yes, as co-facilitator of #FEP, that is the point. Highly in favor of a bottom-up 3-phase standards process designed to guarantee an open ecosystem and tech landscape. Wrote a bunch about that on #SocialHub:
Actually, Internet Explorer 6 was once 97% of the browser market. That’s right, 97%—they had the browser market locked down!
If ever there was a situation where “embrace, extend, extinguish” (EEE) should have worked, it was with the open web.
Yet Microsoft failed. Why is that?
First, while Microsoft initially was installed by default on every Mac, they had neglected the Mac version of Internet Explorer. So Apple took action and made their own browser—Safari. They shipped this in 2003.
But also, Microsoft refused to build a version of Internet Explorer for Linux. This forced Linux advocates to build their own web browser engines, most prominently KHTML. Apple forked KHTML into WebKit, which was then used as Safari’s browser engine.
Thereafter Netscape rose from the ashes as Mozilla, released Firefox. And Firefox not only caused tabs to go mainstream, but also extensions too.
And where was Microsoft while all this was happening? Resting on their laurels, content with the belief that EEE would work. They never improved IE6. As all the other browsers came out, IE6 looked more and more worse.
But still, they had the corporations using it, so there was no fire in Microsoft to improve IE6.
The final nail in the coffin was Chrome. Corporations were willing to make the leap to Chrome because Google built backwards compatibility for IE6 with Chrome.
Microsoft tried to recover with subsequent versions of Internet Explorer. But they eventually discontinued it and released a new browser called Edge.
Nevertheless, Microsoft never achieved browser dominance again even with installing edge as the default browser on Windows.
Microsoft failed to #EEE the open web. It wasn’t the open web that was extinguished. It was Internet Explorer.
Some people accuse me of putting "embrace, extend, and extinguish" (#EEE) to a standard that is unfalsifiable.
First off, it doesn't matter whether or not EEE is unfalsifiable -- this was still a monopolistic strategy that Microsoft tried to employ to kill competition.
But as it happens, EEE actually did work on a few occasions. Most prominently with OS/2 Warp.
What many people don't realize is that IBM didn't merely make OS/2. It was a collaboration with Microsoft.
But Microsoft stabbed IBM in the back and made a competitive product called Windows. Perhaps you might have heard of it.
Much of Windows was based off OS/2. Windows even had a similar UI to OS/2.
Every part of EEE happened to OS/2. Microsoft embraced it. They extended it. And OS/2 was extinguished in 2001.
Why was this possible? I suspect a big reason is that OS/2 was proprietary, not open source.
#Threads user with dotted username (an impossibility in vanilla #Mastodon) spotted in the wild federating with a #Misskey instance (namely, Voskey)! So, does this mean Misskey can handle dotted usernames & thus can further do what #Mastodont?
So, this (the dotted usernames that can federate with other #ActivityPub instances but can't yet be @ pinged from such instances) is a clear example of #EEE being exercised by #Threads upon the #Fediverse. @youronlyone Your thoughts on this again, as we previously discussed it on #Bluesky?
but can't yet be @ pinged from such instances) is a clear example of #EEE being exercised by #Threads upon the #Fediverse
Is, well, not a fair example because dotted usernames have been in used years before Threads and the Twitter Migration. As I mentioned, site plugins have been using @-domain.tld@domain.tld format.
If dotted usernames are going to be used to build a case of EEE by Meta, then the same argument can be used to accuse all other “plugins” using the same format, like Automattic's AP plugin and Brid.gy fed. ^_~
To clarify, I'm not defending Threads. I just find the issue of dotted usernames being linked to EEE, to build a case against Threads, as inaccurate. ^_^
There is no such thing as "#lawful#access". Encryption is #math. There is no math that the "good guys" can do but which cannot be done by the "bad guys".
Anyone who suggests different is #lying, to #spy on you.
L’urlo di Threads fa cagare addosso il Fediverso? EEE… basta
«Noi siamo #Threads, l'esistenza come voi la conoscete è terminata, assimileremo le vostre peculiarità biologiche e tecnologiche alle nostre. La resistenza è inutile.»
I feel like I’ve thoroughly debunked the “Google killed Usenet” narrative.
The problem with these “embrace, extend, extinguish” (EEE) narratives is that, facts be damned, the myth is too compelling.
Never mind that #EEE has never worked against open source. Never mind that open source projects like Linux, Git, and the Web itself continue to thrive. Never mind that the entire world is populated by open projects that killed their proprietary equivalents—rather than vice versa.
If a story sounds good, people won’t just believe it, they’ll double down even when you show them facts.
The problem is that it’s the supposed “fans” of open source—in this case, the #Fediverse—that believe in the EEE narrative the most. They’re the architects of their own fear, uncertainty, and doubt. They’re the ones trumpeting doom and gloom, telling all newcomers that they should cower in fear. Again, facts be damned, the narrative of EEE is too compelling for them.
Microsoft, Google, and Meta don’t have to say anything to make people scared for the future of the Fediverse. Fans of the Fediverse do that for them.
It's funny, whenever spreaders of "embrace extend extinguish" (#EEE) FUD come into my inbox, I tell them that the "extinguish" part of EEE has never worked against open source.
And they almost always reply, "Oh, we don't actually mean 'extinguish'. We mean something else."
Then don't use the word "extinguish" -- because extinguish means extinguish.
If you don't mean "extinguish", then you're clearly moving goal posts. Or worse, you're re-defining a word ("I don't really mean extinguish") to imply something happened when it actually didn't. Don't use the word "extinguish" if that's not what you actually mean.
You're not helping open source by spreading false EEE narratives. You're hurting it.
So according to Eugen, he's been using XMPP during a time when people let their desktop PCs run all the time, which is ideal for XMPP's requirement to maintain an active connection from sender to recipient in order to actually deliver messages.
But when the world transitioned from desktop PCs to mobile phones, XMPP's requirement to stay always on was just not practical, and the world moved on from XMPP and onto other platforms.
The only way people used XMPP was through Facebook and Google Talk, but the mainstream really didn't have a strong appreciation for XMPP.
According to Eugen, Email is still going strong because everyone knows how to work with it
Effectively, embracing, extending, extinguishing is just not a thing for email yet.
People actually think “embrace, extend, and extinguish” (#EEE) was a fun slogan created by open source advocates, and was never meant to be taken literally.
That’s not the case.
Microsoft made that phrase up, not open source advocates. And they meant it literally, not figuratively. When they said “extinguish”, this wasn’t an exaggeration. They really did mean it.
Some people say that Meta makes Threads federate with Mastodon so it would eventually siphon its users (see #EEE).
That's one of the reasons several Mastodon instance admins decided to preventively block Threads (see #Fedipact).
I think that keeping some Mastodon users from interacting with Threads might on the contrary push them away from their instance and maybe go to Threads instead, what we want to avoid in the first place.
Can those of you that are tenured here in the #Fediverse tell me where this alarmist #EEE views have come from? Either this people are grossly misinformed/uninformed or they are disingenuous and that would bother me more. Like how if you believe in the #fediverse do you believe some corp can come and take it all over?
With a corporate takeover and corporate "values" they shed like fleas, the #EEE will come in form of #Fediverse losing original intent and meaning.
No longer a place of refuge where people build things to the delight of others and in natural interaction foster cultures where humanity can be freely expressed.
Fediverse will be a category name, just like Web and Internet. A place of marketeers and commerce.
And yes, somewhere there.. #fedi still around. That neat hidden place, only to be found!
Welcome!
Welcome to the my little pony magazine!...