@brynet personally, I think #WMI is #Microsoft's #EmbraceExtendExtinguish strategy to #proprietary-ize functions that should belong into open ABIs like #ACPI!
@brynet personally, I think #WMI is #Microsoft's #EmbraceExtendExtinguish strategy to #proprietary-ize functions that should belong into open ABIs like #ACPI!
@theverge @tech-news-theverge yeah...
Meanwhile I recommend migrating to #WebRTC like #JitsiMeet, #WebCall and espechally classic #SIP / #VoIP like #Linphone!
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?
Their interest is hegemony.
#Microsoft embracing, extending and extinguishing as always
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.
#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.
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.