So, Chrome's "web standard" Prompt API:
-
@jaffathecake
Google / Alphabet needs to have Android & Chrome divested from them and them kicked out of everything.They are an Advertising agency that cares nothing about local laws or people.
Somel finance from Eric Schmidt, who was CEO for a while. Hides from public eye and hardly mentioned in history of Google. He turned it into an advertising agency fuelled by surveillance.
Google Analytics and Recaptcha are evil tools they use that no-one should deploy, or any other Google service.@jaffathecake
Amazon, Google, Apple, Musk etc show the huge flaw in allowing shares as collateral for loans as "payment" for a takeover, often described as a merger.Obscene Capitalism.
Musk is rich by background, luck & stupidity of other people, partly Peter Thiel.
Paid Tesla to claim he was a founder.
-
So, Chrome's "web standard" Prompt API:
Mozilla: Opposed
WebKit: Opposed
Microsoft: Several concerns
W3C TAG: Several concerns
Developers: Mostly negativeChrome: Ships anyway.
A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'
@jaffathecake Internal politics trumps external reactions every time.
I am currently using waterfox, a Clean fork of Firefox ( no AI features, kill switch or no )
-
@jaffathecake @nachtfunke I loved that one when I read it the other day
The strongly supportive was one comment in a github issue, a blog that doesn't exist anymore, and another blog post. Overwhelming interest, overwhelming support! @phl @jaffathecake @nachtfunke
Ya know they say threes a crowd
-
So, Chrome's "web standard" Prompt API:
Mozilla: Opposed
WebKit: Opposed
Microsoft: Several concerns
W3C TAG: Several concerns
Developers: Mostly negativeChrome: Ships anyway.
A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'
Given the other shit that Google is shipping the moment, their browser won't be going onto any system that doesn't absolutely need it.
-
So, Chrome's "web standard" Prompt API:
Mozilla: Opposed
WebKit: Opposed
Microsoft: Several concerns
W3C TAG: Several concerns
Developers: Mostly negativeChrome: Ships anyway.
A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'
Google is on the boycott list.
They’re too big for anyone’s good & are tied in with the two governments that care more about big brother surveillance and holy wars than their people.I like ecosia (they plant trees for each search)
Brave and Firefox are cool too -
@jaffathecake what are we as developers supposed to do here? We have literally no say in this whatsoever.
It’s a genuine question, what are we supposed to? Because I subjectively feel like we could have done something maybe 10 years ago, but now…?
@nachtfunke @jaffathecake oh that's easy developers needed to keep using and supporting Firefox because open internet matters more than anything else.
Sadly, majority of developers failed at that, just like they did with Internet Exploder.
-
So, Chrome's "web standard" Prompt API:
Mozilla: Opposed
WebKit: Opposed
Microsoft: Several concerns
W3C TAG: Several concerns
Developers: Mostly negativeChrome: Ships anyway.
A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'
@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)
-
So, Chrome's "web standard" Prompt API:
Mozilla: Opposed
WebKit: Opposed
Microsoft: Several concerns
W3C TAG: Several concerns
Developers: Mostly negativeChrome: Ships anyway.
A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'
@jaffathecake internet explorer from its grave.
-
@joshhunt if there is then they failed to show it. They posted a couple of links, including a survey about something else.
@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.
-
@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.
(and obviously Mozilla follows suit, because why are they there if not to suck up to the bully)
-
@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)
@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 @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!
@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/
-
So, Chrome's "web standard" Prompt API:
Mozilla: Opposed
WebKit: Opposed
Microsoft: Several concerns
W3C TAG: Several concerns
Developers: Mostly negativeChrome: Ships anyway.
A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'
@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 @jaffathecake MLA and Chicago Manual of Style agree with what I did, at least: https://grammarist.com/punctuation/apostrophe-after-s-rules-and-examples/
@yoasif @jaffathecake Ah, yes, the Bri'ish vs. 'murrican vs. Internet rules of englishing.
-
@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.
@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 @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.
@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
.
