Live data from Hacker News

Google is already pushing WEI into Chromium

github.com

511–520 of 876 posts

Re: Google is already pushing WEI into Chromium

#511
post #397

There are many arguments against this but not many brought the implications for search engines. If websites implement this, it will effectively make building a web search engine impossible for new entrants. The current players can whitelist/attest their own clients while categorizing every other scraping clients as bots. If not for other reasons, I can't see how Google a search company can be allowed to push somethin…

Is it possible for them to implement this API in such a way that it will fail 5% of the time or so, making it impossible for websites to deny individuals based on failing attestation? https://github.com/RupertBenWiser/Web-Environment-Integrity/...

Why would they?

Re: Google is already pushing WEI into Chromium

#514
post #212

Earlier quoted context omitted.

I use Firefox as a daily driver. And I never encounter these sites. Perhaps we are not surfin on the same pages? Do you have a list of these pages?

Is your firefox rendering google maps the same sharp (vectorized) as in chromium? In my firefox it seems not so sharp and rasterized (tiles?), but might be related to some privacy plugins/settings I'm using.

I didn't compare or realize that. So if you are right and most probably you are, I suppose I am not that interested in that sharpness.

Re: Google is already pushing WEI into Chromium

#515
post #4

Can somebody explain what are the practical implications of this?

Unblockable ads, sites can serve you data that you can’t manipulate or copy, micropayments can exist, invasive surveillance. Surveillance is possibly the worst of the bunch. They say it’s just to do a better job of serving ads, but that’s only the tip of the iceberg. Governments could easily use it to know and track everything you do online. Just wait till the next elected nut job wants a list of everybody that has e…

Getting some "PLEASE DRINK VERIFICATION CAN" vibes...

https://imgur.com/dgGvgKF

Re: Google is already pushing WEI into Chromium

#516
post #34

And also, to switch back to Firefox

Firefox' killer feature on mobile is that it supports uBlock Origin, while Chrome doesn't. Browsing the web without it is horrible -- the screen covered in popups with tiny Xes. There's a decent fraction of the time that you can't even read the content underneath. Firefox solves all that. However. Try opening any article from The Guardian on Firefox mobile. Even a good phone will start feeling sluggish and laggy and…

Firefox mobile on Android, ublock origin and darkreader installed. No lag on guardian articles on a pixel 6a.

Re: Google is already pushing WEI into Chromium

#517
post #186

It's small, but here's a real actionable item that you can do to help: Put a gentle "Use Firefox" (or any other non-Chromium-based browser) message on your website. It doesn't have to be in-your-face, just something small. I've taken my own advice and added it to my own website: https://geeklaunch.io/ (It only appears on Chromium-based browsers.) We can slowly turn the tide, little by little.

i find this comment a bit funny given that you use googletagmanager on your website :)

Re: Google is already pushing WEI into Chromium

#518
post #342
post #50

Earlier quoted context omitted.

Limiting posting and asking for civility is the only way for individuals to meaningfully engage with even a mere thousand others. Nothing about the human mind was meant for social internet at the scale of the internet, where there are more distinct voices than you have heartbeats in a lifetime.

Yes, and the response should be to make the repo private. Only allowing interactions from previous contributors to a public repo is disingenuous.

My expectation is that private is worse for any public involvement in any discussion because nobody else can see it, and also likely to get them yelled at more via other channels, and also lead to the assumption that they "have something to hide".

Re: Google is already pushing WEI into Chromium

#519
post #397

There are many arguments against this but not many brought the implications for search engines. If websites implement this, it will effectively make building a web search engine impossible for new entrants. The current players can whitelist/attest their own clients while categorizing every other scraping clients as bots. If not for other reasons, I can't see how Google a search company can be allowed to push somethin…

Is it possible for them to implement this API in such a way that it will fail 5% of the time or so, making it impossible for websites to deny individuals based on failing attestation? https://github.com/RupertBenWiser/Web-Environment-Integrity/...

Have you seen bank "login redirects" when the system redirects you for ca. 5-10 times before actually letting you in? This proposal could be defeated in the same way: after successful authn, the user is redirected to the page '/wei_chk_1', then '/wei_chk_2' and so on until '/wei_chk_$n', e.g. 10 or WEI check success. If the WEI Javascript check succeeded on at least one page, you are logged in. Otherwise, get lost.

Re: Google is already pushing WEI into Chromium

#520
post #332

Earlier 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…

And that makes him “shadow president” how? Was he the one with the most access as opposed to, says, David Axelrod?
Post reply on HN