@brynet personally, I think #WMI is #Microsoft's #EmbraceExtendExtinguish strategy to #proprietary-ize functions that should belong into open ABIs like #ACPI!
#embraceExtendExtinguish
@theverge @tech-news-theverge yeah...
Meanwhile I recommend migrating to #WebRTC like #JitsiMeet, #WebCall and espechally classic #SIP / #VoIP like #Linphone!
- #Skype fucked up big time, but TBH it was #Microsoft doing #EmbraceExtendExtinguish instead that killed it!
Until they finally said the quiet part out loud.
#Mastodon #Decentralized #FuckBluesky #EmbraceExtendExtinguish
Microsoft To Shut Down Skype in May
#EmbraceExtendExtinguish - Microsofts de facto corporate motto.
Another good occasion to switch to #FreeAsInFreedom software
https://slashdot.org/story/25/02/28/1426223/microsoft-to-shut-down-skype-in-may-shift-users-to-teams
😊👉 Scheduled posts
😔🫸 More Bullshitsky #EmbraceExtendExtinguish
RE: https://shonk.social/notes/a2fg9w09qjq5000e
#googleSucks #google #embraceExtendExtinguish
Google continues to break things they buy and don't want, things they build and no longer want, things they just can't monetize (with cash or data) enough.
I hates them, dirty, mean, googles.
#spam I don't care about a bluesky enabling app. Why is my feed suddenly blowing up over "SwILL"? (added a w just because)
Looks to me the the money at bluesky has taken official am at mastodon.
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish
@winterschon @mms @stefano can the #AfferoGPL be a safeguard against #EmbraceExtendExtinguish?
@Deborah Hartmann Preuss, pcc 🇨🇦 Embrace-Extend-Extinguish.
Embrace = they join the Fediverse.
Extend = they introduce stuff that's non-standard and not really compatible with what already exists. Everything else has to adopt that non-standard stuff or risk becoming incompatible. Since they're one of the biggest players or the biggest player, they can get away with it.
Threads has yet to do this. Mastodon has been doing it all the time.
Extinguish = They decide they don't care for interoperability anymore. They become incompatible with everything else. As big as they are, they get away with it. But they basically kill everything else off because all that "everything else" can hardly survive without being connected to that one big player.
Mastodon has more power to do this than Threads because Threads is a late addition to the Fediverse, Threads isn't even really welcome in the Fediverse, only a tiny fraction of Threads even federates, and I guess that to more people than not, Mastodon is the Fediverse.
(Public reply because the original post is public. I'm on Hubzilla and not on Mastodon, and on Hubzilla, all replies always have the exact same permissions as the original post. Permission changes within a thread are not supported.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EEE #EmbraceExtendExtinguish
Embrace = they join the Fediverse.
Extend = they introduce stuff that's non-standard and not really compatible with what already exists. Everything else has to adopt that non-standard stuff or risk becoming incompatible. Since they're one of the biggest players or the biggest player, they can get away with it.
Threads has yet to do this. Mastodon has been doing it all the time.
Extinguish = They decide they don't care for interoperability anymore. They become incompatible with everything else. As big as they are, they get away with it. But they basically kill everything else off because all that "everything else" can hardly survive without being connected to that one big player.
Mastodon has more power to do this than Threads because Threads is a late addition to the Fediverse, Threads isn't even really welcome in the Fediverse, only a tiny fraction of Threads even federates, and I guess that to more people than not, Mastodon is the Fediverse.
(Public reply because the original post is public. I'm on Hubzilla and not on Mastodon, and on Hubzilla, all replies always have the exact same permissions as the original post. Permission changes within a thread are not supported.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #EEE #EmbraceExtendExtinguish
@Johannes Hentschel
They won't be able to achieve that. For that, they'd all have to join forces. Instead, the big players would rather bash each other's heads in.
If Zuckerberg wanted to buy out the Fediverse through the SWF and assume full control over it, that'd go hard against what Flipboard wants, what Ghost wants, what Mastodon wants etc.
If you think Zuck and Gargron will join forces in EEE'ing the Fediverse, I have a bridge to sell you. If Zuck wants to EEE the Fediverse, this includes Mastodon which is why everyone panics. But Gargron himself wants to EEE the Fediverse, too. Mastodon users don't notice it, but everyone else does, from Misskey to (streams). And if he could, that'd include assuming indirect control over Threads by forcing Mastodon's proprietary, non-standard solutions upon it.
Write.as, maintainer of WriteFreely, is a supporter of the SWF, too. WriteFreely is basically one of the Fediverse's alternatives to Medium. Notice how Medium itself is a supporter. Medium won't try to build a monopoly and get rid of WriteFreely through the SWF if WriteFreely itself has a saying in this. And so does Automattic because Medium competes against WordPress.
Mastodon vs Write.as + Medium + Automattic = "The Fediverse is for microblogging, we won't support more than a tiny subset of HTML, and the rest of the Fediverse has to adjust" vs "Everything in the Fediverse must support full HTML rendering for Article-type objects."
And the SWF won't grant voting power according to how much money someone invests into it. Meta won't be able to out-vote everyone else by pumping a billion into the SWF. If that was possible, @Evan Prodromou, as the very founder of the SWF, would have no voting power at all.
Lastly, these are the supporters. The financial backers. Not the only members and even less the only members the SWF will ever have. It's just kind of difficult for a Fediverse project with nothing but one or two spare-time devs behind it to join the SWF.
CC: @Mike McCue
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MetaPlatforms #Threads #Automattic #WordPress #Medium #Write.as #WriteFreely #SWF #SocialWebFoundation #EEE #EmbraceExtendExtinguish
Their interest is hegemony.
They won't be able to achieve that. For that, they'd all have to join forces. Instead, the big players would rather bash each other's heads in.
If Zuckerberg wanted to buy out the Fediverse through the SWF and assume full control over it, that'd go hard against what Flipboard wants, what Ghost wants, what Mastodon wants etc.
If you think Zuck and Gargron will join forces in EEE'ing the Fediverse, I have a bridge to sell you. If Zuck wants to EEE the Fediverse, this includes Mastodon which is why everyone panics. But Gargron himself wants to EEE the Fediverse, too. Mastodon users don't notice it, but everyone else does, from Misskey to (streams). And if he could, that'd include assuming indirect control over Threads by forcing Mastodon's proprietary, non-standard solutions upon it.
Write.as, maintainer of WriteFreely, is a supporter of the SWF, too. WriteFreely is basically one of the Fediverse's alternatives to Medium. Notice how Medium itself is a supporter. Medium won't try to build a monopoly and get rid of WriteFreely through the SWF if WriteFreely itself has a saying in this. And so does Automattic because Medium competes against WordPress.
Mastodon vs Write.as + Medium + Automattic = "The Fediverse is for microblogging, we won't support more than a tiny subset of HTML, and the rest of the Fediverse has to adjust" vs "Everything in the Fediverse must support full HTML rendering for Article-type objects."
And the SWF won't grant voting power according to how much money someone invests into it. Meta won't be able to out-vote everyone else by pumping a billion into the SWF. If that was possible, @Evan Prodromou, as the very founder of the SWF, would have no voting power at all.
Lastly, these are the supporters. The financial backers. Not the only members and even less the only members the SWF will ever have. It's just kind of difficult for a Fediverse project with nothing but one or two spare-time devs behind it to join the SWF.
CC: @Mike McCue
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MetaPlatforms #Threads #Automattic #WordPress #Medium #Write.as #WriteFreely #SWF #SocialWebFoundation #EEE #EmbraceExtendExtinguish
#Microsoft embracing, extending and extinguishing as always
@Mike McCue A new proposal for a Fediverse logo is a Unicode character: ⁂ (U+2042).
This would not only allow, but actively help Meta assume control over the Fediverse.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Asterism #FediverseSymbol #FediverseLogo #Meta #EmbraceExtendExtinguish
Most of all, whether we like it or not, millions of people are being exposed to this icon everyday on Threads as a symbol of the fediverse so I think it’s a pragmatic choice.
This would not only allow, but actively help Meta assume control over the Fediverse.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Asterism #FediverseSymbol #FediverseLogo #Meta #EmbraceExtendExtinguish
#EmbraceExtendExtinguish aplicado a las causas justas y los movimientos sociales:
Primero se infiltran en las mismas.
Después toman el control de las mismas y las moldean a su gusto y placer.
Por último deciden quienes merecen formar parte y quienes no, reemplazando su status de popular por el de uno sectario.
Así se desacreditan las causas justas y los movimientos sociales por dentro.
Ooh, can’t wait to read the gushing praise from Mastodon GmbH for this on the Mastodon blog.
(Mastodon gGmbH and Meta are besties, you see. https://www.platformer.news/mastodon-interview-eugen-rochko-meta-bluesky-threads-federation/)
Is it up yet?
#mastodon #meta #besties #allTheBetterToSeeYouWith #EmbraceExtendExtinguish https://social.wildeboer.net/@jwildeboer/112391192672337102
Ah but if #Mastodon implements controls in replies and #quoteposts it's suddenly not #EmbraceExtendExtinguish or #EEE and it's actually good because safety yadda yadda. :seija_coffee:
These #fedipact people literally think that EEE in the #fediverse is when Mastodon isn't doing it lmao :reimu_sigh:
#fediversemeta
RE: https://mas.to/users/tokyo_0/statuses/112382573964635856
Tbh I'm not enthusiastic about a #Mastodon #hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
#fediversemeta
RE: https://hachyderm.io/users/jenniferplusplus/statuses/112355187216928083
@BeAware@social.beaware.live Uhh I think you've gotten it fundamentally wrong here :thinking_cirno:
Whether your instance's posts appear on the blocked instance or not doesn't depend on the blocked having #AuthorizedFetch, but rather your instance having AF. That instance can still fetch your posts because your instance doesn't check if the request is signed (so an instance can sign all their fetching but still not enable AF, which is what vanilla #Misskey currently does) and from which instance the fetch request is coming from (hence the "authorized").
Threads already defederates from instances that don't sign their fetching (by design because they've enabled AF), but they don't care if an instance has enabled AF (it's that instance's problem to deal with posts still appearing in Threads).
The problem (I have) with AF is that it's pretty much just #securitytheater. The documentation doesn't seem to account for this possibility, but if your adversary has enough money for some cheap domains and is well-versed in how #ActivityPub works nowadays, then it's trivial for them to forge signatures to look like their fetches come from an innocent server, therefore effectively bypassing the check and allowing the blocked to get your posts into their instance. This is already being done in the wild (with the #Soapbox developer doing this to bypass Threads' fediblock being the most infamous recently).
It also complicates AP implementations because now you have to deal with more cryptography with all that signing and verifying of requests. And signing alone does have a significant impact on performance. It's impossible to create a 100% compatible AP implementation from the spec alone without looking at Mastodon's implementation. That's where the #EmbraceExtendExtinguish or #EEE comes to play.
So overall it's the overeagerness of #MastoAdmins in adopting AF or #SecureMode without understanding the compatibility and performance implications that brought us to this mess today.
@:mima_rule: Mima-sama
Threads overrunning the Fediverse, pushing its culture and its limitations upon the rest of the Fediverse, forcing the rest of the Fediverse to adopt its own proprietary and non-standard stuff to stay compatible and trying to "be the Fediverse": 😠😖🤬🤮👎🖕💢🐖💩💀
Mastodon overrunning the Fediverse, pushing its culture and its limitations upon the rest of the Fediverse and forcing the rest of the Fediverse to adopt its own proprietary and non-standard stuff to stay compatible and trying to "be the Fediverse": 😍😁🤗🥰👍👌👏🫶💙💯
Of course, none of those who recognise this hypocrisy as such are on Mastodon themselves and not on Threads either.
Oh, and by the way: No, Mastodon wasn't here first. It wasn't even the first project to support ActivityPub.
CC: @BeAware :veriweed: @Kitty Wife Milkshake
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Threads #Mastodon #EEE #EmbraceExtendExtinguish #Hypocrisy
Threads overrunning the Fediverse, pushing its culture and its limitations upon the rest of the Fediverse, forcing the rest of the Fediverse to adopt its own proprietary and non-standard stuff to stay compatible and trying to "be the Fediverse": 😠😖🤬🤮👎🖕💢🐖💩💀
Mastodon overrunning the Fediverse, pushing its culture and its limitations upon the rest of the Fediverse and forcing the rest of the Fediverse to adopt its own proprietary and non-standard stuff to stay compatible and trying to "be the Fediverse": 😍😁🤗🥰👍👌👏🫶💙💯
Of course, none of those who recognise this hypocrisy as such are on Mastodon themselves and not on Threads either.
Oh, and by the way: No, Mastodon wasn't here first. It wasn't even the first project to support ActivityPub.
CC: @BeAware :veriweed: @Kitty Wife Milkshake
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Threads #Mastodon #EEE #EmbraceExtendExtinguish #Hypocrisy
Defederating #Threads will, however, stop Threads from drowning out the entire rest of the Fediverse.
The result of federating is that Threads *is* the Fediverse now, and the rest of us are just the silent periphery that no one cares about and aren't even allowed to speak to Threads users (the federation is one-way). This kills the Fediverse. Easiest #EmbraceExtendExtinguish ever.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst