#embraceextendextinguish — Public Fediverse posts

#Bluesky is a (pathetic) attempt at #EmbraceExtendExtinguish for the #Fediverse .

#censorship #CentralizedControl

So MS are the lower-friction option for getting students doing stuff on the cloud (they offer free credits with no credit card needed, unlike Goog, AWS). I was looking to get into the GitLab for Education scheme. You must be a degree-issuing institution to get on that program. Guess which other distributed version control SaaS provider offers their service to *any* education establishment (schools included)? #BaitAndSwitch #HeartsAndMinds #EmbraceExtendExtinguish #NeverForgetNeverForgive

@winterschon @mms @stefano can the #AfferoGPL be a safeguard against #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.

#Reflexión #MovimientosSociales #Sociedad #Protesta #Causa

@[email protected] 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.

Definitely not hypocritical. #meme #Mastodon #Poast #Pixelfed #Meta #threads #EugenRochko #EmbraceExtendExtinguish

He’s making a list,
He’s checking it twice,
He’s going to decide,
Who’s naughty or nice…
Zuckerberg is coming to town.

#fediverse #threads #moderation #embraceExtendExtinguish #dumbFucks

I know vscode is very easy to use, but this is definitely worth reading:

https://ghuntley.com/fracture/

It's the old "embrace, extend, extinguish". Try open-source alternatives like my emacs-groundup, or vim or what have you.

Programming is not meant to be a 'frictionless' experience. Nothing is. Stop buying into this consumer-centric bullshit.

#vscode #emacs #vim #friction #frictionless #coding #EmbraceExtendExtinguish #opensource

@kasra_mp It's not a question of how long it took (though that's a strong indicator of Google's dedication to the task), but of what the result is:

The total word count of the W3C specification catalogue is 114 million words at the time of writing. If you added the combined word counts of the C11, C++17, UEFI, USB 3.2, and POSIX specifications, all 8,754 published RFCs, and the combined word counts of everything on Wikipedia’s list of longest novels, you would be 12 million words short of the W3C specifications.2

I conclude that it is impossible to build a new web browser. The complexity of the web is obscene. The creation of a new web browser would be comparable in effort to the Apollo program or the Manhattan project.

It is impossible to:

• Implement the web correctly
• Implement the web securely
• Implement the web at all

-- Drew DeVault

https://drewdevault.com/2020/03/18/Reckless-limitless-scope.html

Complexity is a principle tool of monopolisation.

@stux

#DrewDevault #EmbraceExtendExtinguish #W3CSpecification #Complexity #Google #GoogleChrome

It's also worth reflecting on why Facebook pays its employees so highly. There are two principle reasons:

1. It can. The company is an absolute cash machine.

2. It has to. For both selling their morality, and mental health due to the stress.

Which is what cooperating with FB in any way, shape, or form would also entail.

#Facebook #Meta #MetaBlock #KaraSwisher #LinaKhan #USFTC #Antitrust #Monopoly #EmbraceExtendExtinguish #EternalSeptember #MarkZuckerberg #FuckZuck #FuckFacebook

It is very satisfying to finally push the commit titled "Remove Microsoft Internet Explorer workarounds" to production.

#Microsoft #MSIE #EmbraceExtendExtinguish

Folks in Silicon Valley: We’re so glad some poor schmuck created Mastodon on his own dime and time while we were busy making mint festering the Twitters of the world. Isn’t it great? We’re really enjoying it… Now, how do we enclose, exploit, and monetise the shit out of this thing?

#SiliconValley #BigTech #peopleFarmers #fediverse #mastodon #enclosure #embraceExtendExtinguish #ventureCapital #vc #billionaire #douchebags