Earlier quoted context omitted.
Exactly. Also, if some anecdata can help change a mind: Firefox is a really good browser these days. I use it quite heavily, and it hasn’t disappointed in the last three or so years since I switched from Chrome. About the only use case I still need Chrome for is for sites requiring experimental web APIs not supported by Firefox, such as Web USB or Web Bluetooth. Site compatibility for everything else, including very…
I switched to Firefox for the idealogical reasons above and was pleasantly surprised to find that it was a net improvement. The only site I have compatibility issues with on desktop is MS Teams and even then it's only for voice/video calls, everything else works fine. Firefox Android is a slightly less happy place. The password manager doesn't work very well (am moving away from the built-in one) and I can't log in o…
Google is already pushing WEI into Chromium
541–550 of 876 posts
Re: Google is already pushing WEI into Chromium
#542Apple would be in the position to fight this.
"Apple already shipped attestation on the web, and we barely noticed" https://news.ycombinator.com/item?id=36862494
Attestation bad. Chrome is just catching up to what Safari is already doing, with in fairness more open standard.
We need to kill both.
Re: Google is already pushing WEI into Chromium
#543Will OS check if such python lib is installed or script running in the background? Then those that doing ad fraud will move to programmable board as BLE keyboard/mouse/hid. Even microbit can can be programmed as BLE HID device [1]. Add external camera on unattested device that will stare at attested device screen and you can automate lots of thing. Sure this is more complicated to pull off but will probably eventually happen anyway if this is a lucrative business.
In the end WEI wouldn't prevent ad fraud / fakes but would end up used for restricting other things.
Re: Google is already pushing WEI into Chromium
#544Earlier quoted context omitted.
That sounds entirely unhelpful. They can just close the issue tracker + people will obviously just move on. This sounds like the Reddit 'blackout' that did nothing and is already forgotten. What we really need is for the collective browser vendors to refuse to implement this and, if Chrome pushes forward, to bring Google to court over it. Nothing short of legal intervention is going to help here.
What sort of regulation do we imagine a government putting into place to stop this? If anything, governments tend to lean in favor of identification and verification systems because they make corporate commerce run more smoothly.
Legislation around device ownership rights are already present, especially in the EU.
Re: Google is already pushing WEI into Chromium
#545This is a crisis of our own making. You don't want Google taking decisions for the web at large? Then don't let them own 85% of the browser market share. When that's the case they don't need W3C or anything to implement whatever they want, they effectively control the client-side internet.
I hope, pragmatically, something similar might happen with this: say that Brave (my daily driver) disables WEI in their Chromium build, and a new Chromium-derived browser surges in popularity... like judo, using their own power against them.
Re: Google is already pushing WEI into Chromium
#546Earlier quoted context omitted.
Which executive orders, federal appointments, and other executive branch actions, would you attribute to Eric Schmidt?
From this article: "At the same time, Schmidt has been appointed to numerous White House advisory positions, giving him privileged insight into the administration’s policies in technology, science and military defense, as well as unusual access to top policymakers." https://www.techtransparencyproject.org/articles/eric-schmid... A quick Google of "eric schmidt obama" brings up a lot of articles discussing their close…
Re: Google is already pushing WEI into Chromium
#547Earlier quoted context omitted.
I switched to Firefox for the idealogical reasons above and was pleasantly surprised to find that it was a net improvement. The only site I have compatibility issues with on desktop is MS Teams and even then it's only for voice/video calls, everything else works fine. Firefox Android is a slightly less happy place. The password manager doesn't work very well (am moving away from the built-in one) and I can't log in o…
Interesting. Firefox android works great for me, but Firefox windows gets very slow on my machine. I don't use their password manager on either, though, so I can't attest to that.
https://news.ycombinator.com/item?id=35458746>
Re: Google is already pushing WEI into Chromium
#548Earlier quoted context omitted.
That sounds entirely unhelpful. They can just close the issue tracker + people will obviously just move on. This sounds like the Reddit 'blackout' that did nothing and is already forgotten. What we really need is for the collective browser vendors to refuse to implement this and, if Chrome pushes forward, to bring Google to court over it. Nothing short of legal intervention is going to help here.
Or we could show Chrome users what the future will look like for alternative browsers - by blocking Chrome now.
Re: Google is already pushing WEI into Chromium
#549Earlier quoted context omitted.
Tech-literate folks really should make a concerted effort to move to our own darknet, something like freenet or I2P, to recreate the internet before the advent of mass adoption of smartphones by the public. Forums, IRC, vent/TS, webrings, XHTML 1.0. No WebGL. No Canvas. No WebAssembly. No damn WEI. Normies can f&$% off and enjoy the data-mined, DRM'd, ad-infested, CCP-propagandized, upload-your-photo-ID-to-post-here,…
While I like this idea, starting from the foot of "CCP-propagandized" based on the tiktok service hosted by Oracle in the US is an amazing way to start off on a Nazi infested foot. Anti-communism and fascism are historically in lock-step. No one is going to use the services if you basically create web4 stormfront.
Re: Google is already pushing WEI into Chromium
#550Earlier quoted context omitted.
That sounds entirely unhelpful. They can just close the issue tracker + people will obviously just move on. This sounds like the Reddit 'blackout' that did nothing and is already forgotten. What we really need is for the collective browser vendors to refuse to implement this and, if Chrome pushes forward, to bring Google to court over it. Nothing short of legal intervention is going to help here.
Similar feature is already in production Safari, alas: https://httptoolkit.com/blog/apple-private-access-tokens-att...