So, Chrome's "web standard" Prompt API:
-
@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 I think the big power developers do still hold is to just not use this API. The web isn't cast in stone (as much as people may think it is), if the usage stays low enough there's a chance it might unship in years to come, or at least go through changes to make others more onboard (idk if that's feasible here though).
-
@jaffathecake Honestly, maybe the reality is just that we developers nowadays are positioned too much by business practices that the majority is indeed strongly supportive. I don’t know anymore.
I am tired of this all. When you’re sounding the alarm early you’re being negative and when you criticize it when it’s a manifest problem then you’re being called complicit.
I don’t know anymore. Im a modern Luddite at this point
@nachtfunke @jaffathecake
My conclusion from the earlier browser wars: history unfortunately repeats itself, and too much market dominance is harmful to platform-independent web standards. -
@nachtfunke @jaffathecake
My conclusion from the earlier browser wars: history unfortunately repeats itself, and too much market dominance is harmful to platform-independent web standards.@af yes indeed. I would argue that market dynamics shouldn't have any influence on the infrastructure of modern human connection.
-
@nachtfunke oh, Google had you all down as "strongly supportive" https://groups.google.com/a/chromium.org/g/blink-dev/c/iR6R7-nQeHI/m/gN4iEGEdAQAJ
@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! 
-
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
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. -
@nachtfunke oh, Google had you all down as "strongly supportive" https://groups.google.com/a/chromium.org/g/blink-dev/c/iR6R7-nQeHI/m/gN4iEGEdAQAJ
@jaffathecake Maybe there's some definition of "developers" in the spec process, but I think it is problematic to consider "developers" to be one giant mass.
I agree with you - this is a bad API. But especially given the topic, I think this process self-selects for the most vocal, and I can imagine there are loads of developers out there that are genuinely supportive of an API like this.
-
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 agents in your very browsers
-
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 I've been saying chrome is the new ie for years...
-
@jaffathecake Maybe there's some definition of "developers" in the spec process, but I think it is problematic to consider "developers" to be one giant mass.
I agree with you - this is a bad API. But especially given the topic, I think this process self-selects for the most vocal, and I can imagine there are loads of developers out there that are genuinely supportive of an API like this.
@joshhunt if there is then they failed to show it. They posted a couple of links, including a survey about something else.
-
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…'
Alternatives are available.
https://www.firefox.com -
Alternatives are available.
https://www.firefox.com@bit I switched to it last year and not had any issues. It's a great alternative if your tired of all the nonsense Chrome keeps rolling out.
-
@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.