So, Chrome's "web standard" Prompt API:

[yoasif@mastodon.social]

@jaffathecake Sounds kind of like how #Mozilla pushed ahead with #AI even after your lying polls about the provenance of training data in translations and the multitude of negative comments here and on Mozilla Connect.

Pretty good blind spot for Mozilla - you can only tell when things are bad when your competitors do it.

Firefox’s AI Kill Switch is a Trap: How Mozilla Made AI Your Problem

TL;DR: Mozilla recently released AI controls for Firefox: a singlecontrol panel that lets people disable AI features in the browser or pick andchoose which t...

Youssuff Quips (www.quippd.com)

[maikel@vmst.io]

@jaffathecake internet explorer from its grave.

[oblomov@sociale.network]

@jaffathecake @joshhunt it's like the XSLT situation in reverse

Google: we want to drop XSLT support

web developers: we really want you to keep XSLT and possibly upgrade support for v3 of the standard so we can use it with JSON too

Google: OK, we've listened to everybody's opinion and nobody wants XSLT so we're dropping it.

[oblomov@sociale.network]

@jaffathecake @joshhunt

(and obviously Mozilla follows suit, because why are they there if not to suck up to the bully)

[platymew@layer8.space]

@yoasif @jaffathecake If the word ends in an s-like phoneme, you're supposed to eschew the s after the apostrophe.

E.g. For Fox' sake!

[yoasif@mastodon.social]

@platymew @jaffathecake MLA and Chicago Manual of Style agree with what I did, at least: https://grammarist.com/punctuation/apostrophe-after-s-rules-and-examples/

[schouten_b@mastodon.social]

@jaffathecake There's a serious question to be asked about whether an engine shipping things which the broader standards community is opposed to can still be considered a standards compliant browser.

[platymew@layer8.space]

@yoasif @jaffathecake Ah, yes, the Bri'ish vs. 'murrican vs. Internet rules of englishing.

[yoasif@mastodon.social]

@Schouten_B @jaffathecake Hasn't that happened before? Who else supported PNaCl?

I think that is kind of an academic question too, unfortunately - most developers seem to care less about whether something is a standard, and more about whether their userbase can access the feature.

[schouten_b@mastodon.social]

@yoasif @jaffathecake Sure, I think the PNaCl objections were of a different, less fundamental nature, but yeah, this is a question I've asked myself more often.

And sure, humans fundamentally look out for number 1 first. You're not wrong, but some do care about standards, I've been considering blocking Chrome on my own sites. Since they aren't commercial anyway and I don't care if people won't switch browsers in order to access them .