Live data from Hacker News

Google is already pushing WEI into Chromium

github.com

251–260 of 876 posts

Re: Google is already pushing WEI into Chromium

#251

Earlier quoted context omitted.

Some Google services I regularly depend on (like YouTube and Google Meet) don't work as well on Firefox as they do on Chrome, in ways that actually matter. Besides that I think most websites work fine.

What's wrong with Youtube? I haven't noticed anything.

TBF YouTube has gotten better (see sibling comment), but Google Meet is really what matters here for me. There's also offline mode in Google Docs, which I use regularly because I'm not guaranteed a good-enough connection wherever I go.

Firefox does some things better (like PiP video playback on most websites, like YouTube!) but others are so poorly done (like Profiles) compared to Chrome that it overall makes Chrome my first choice browser.

Re: Google is already pushing WEI into Chromium

#252
I'm surprised to see so many people in this thread saying "write a strongly worded letter!" (or something along those lines), and so few saying we need to build a better browser without this crap in it, which has been the traditionally successful answer to attempts to privatize the Web.

Re: Google is already pushing WEI into Chromium

#253
post #5

I feel like I have to repeat this, since so much is at stake here, where it is about the preservation of the web as we know it today, at the peril of having it turned into yet another walled garden: The only way around the dystopia this will lead to is to constantly and relentlessly shame and even harass all those involved in helping create it. The scolding in the issue tracker of that wretched "project" shall flow l…

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.

Re: Google is already pushing WEI into Chromium

#254
post #222

Earlier quoted context omitted.

>The FTC has been more active on anti-trust issues in the past two years than at any time in the past 30.... That's a direct result of the 2020 election. Active against Google though? Remember, Google can help a certain political party in tough times (e.g. rollout of healthcare.gov).

So can Microsoft and Amazon, surely? Yet they're getting a lot of scrutiny from the FTC right now.

Wake me up with they actually do something instead of making announcements of looking into the possibility of perhaps one day sending a strongly worded letter asking their tech buddies to calm down a little bit, if they're so inclined. Until then, this is campaign fodder and nothing else.

Re: Google is already pushing WEI into Chromium

#256

Earlier quoted context omitted.

So many sites don't work correctly in Firefox. Chrome is the new IE6.

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?

I very occasionally run into these, and keep Chrome as a backup browser. I suspect it's as often to do with adblocking though - I have no content blockers on Chrome.

Firefox performs way better and is a more pleasant experience. (This is a fair comparison because my ad-laden Chrome experience is internet as Google intends!)

Re: Google is already pushing WEI into Chromium

#257

Earlier quoted context omitted.

iOS already implemented this stuff

Not only did iOS implement this, but everyone either sleep-walked on it, or worse, praised it , because Apple sold it as a CAPTCHA bypass instead of a DRM scheme: https://mastodon.delroth.net/@delroth/110775677023220850

How is PrivacyPass related to iOS?

Re: Google is already pushing WEI into Chromium

#258
post #162

From the spec author, in 2022 [0]: > I decided to make this an app in the end. This is where my costs started wracking up. I had to pay for a second hand macbook pro to build an iOS app. Apple’s strategy with this is obvious, and it clearly works, but it still greatly upsets me that I couldn’t just build an app with my linux laptop. If I want the app to persist for longer than a month, and to make it easy for friends…

My understanding is that Ben gets his paycheque from Google.

Re: Google is already pushing WEI into Chromium

#259
post #5

I feel like I have to repeat this, since so much is at stake here, where it is about the preservation of the web as we know it today, at the peril of having it turned into yet another walled garden: The only way around the dystopia this will lead to is to constantly and relentlessly shame and even harass all those involved in helping create it. The scolding in the issue tracker of that wretched "project" shall flow l…

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...

Re: Google is already pushing WEI into Chromium

#260

Earlier quoted context omitted.

All of the major tech companies are in on this. Google and Apple already deployed it for their phone and desktop platforms (iOS, Android, macOS, ChromeOS, all support attestation already). Microsoft is getting there with Windows 11, and all new devices shipping since ~2015 have the hardware support. Google is now closing the gap on desktop browsers. Soon the percentage of people supporting it will be high enough to m…

Thanks for the info, i wasn't aware of that at all. > They'll do it when their bank website tells them so. Right. > The day Cloudflare flips the switch to require it for all connections is the day the open web dies. Makes sense and unfortunately seems realistic.

Here's an example how far along we already are. You can imagine the next steps, right? https://blog.cloudflare.com/eliminating-captchas-on-iphones-...
Post reply on HN