Live data from Hacker News

Google is already pushing WEI into Chromium

github.com

331–340 of 876 posts

Re: Google is already pushing WEI into Chromium

#331

Earlier quoted context omitted.

And if they are broken up, now you’re in 5 companies’ databases, win? And then they are all probably going to implement “sign in with Google”.

>And if they are broken up, now you’re in 5 companies’ databases, win? Yes, win. I'd rather be in a number of smaller businesses database than in the one last company's.

Isn’t that the opposite of privacy?

Re: Google is already pushing WEI into Chromium

#332
post #182

Earlier quoted context omitted.

> when regulations don't exist It’s very likely governments will make this mandatory if they have the chance to regulate over this.

[flagged]

Which executive orders, federal appointments, and other executive branch actions, would you attribute to Eric Schmidt?

Re: Google is already pushing WEI into Chromium

#335

As someone who is a somewhat new to web technologies, can someone really explain why this is bad? I saw the techical discussions in the PRs made to the WEI repo but it was all super technical that I was not able to understand the arguments made for and against it.

Like any technology, there are both positive and negative aspects of it. The positive take would probably be that this technology is already widely used by iOS and Android apps. People use Apple's AppAttest to e.g. ensure that high scores submitted for a game are from a legitimate copy of the game and not just someone calling the SubmitHighScore API.

But it's absolutely fair to argue that the web operates on a different set of expectations than the Play Store/App Store, and I think the concerns that this will create a second-class citizen status for browsers are totally valid. There's a huge difference in character between "in order to prevent piracy and ensure ad revenue we are only releasing our app on the Play Store" and "we are only releasing our web app for Chrome".

Re: Google is already pushing WEI into Chromium

#336

Earlier quoted context omitted.

[flagged]

I don't have a Google account and don't use any Google service, still think that this libertarian message is bullshit, how do you do the free will if the web starts deciding which OS/Browser are authorised to do something? I am not sure we are talking about free will or useful idiots

And how will “breaking up Google” help if the “Chrome company” is still implementing DRM?

Re: Google is already pushing WEI into Chromium

#337
post #267
post #241

Earlier quoted context omitted.

isn't this good? banks can raise security while we can still use any browser to check hackers news! or this 3 cows story?

Not great if your bank arbitrarily decides Linux isn't a supported operating system, for example.

Wouldn’t this just mean I should change my bank?

Re: Google is already pushing WEI into Chromium

#338
post #205
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…

Tiktok is literally controlled by the CCP. If consumers don't care about that, they aren't going to care about DRM.

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, privacy-free dump their illiteracy, careless disregard for harm, and data exhibitionism fetish has allowed the clearnet to turn into.

Re: Google is already pushing WEI into Chromium

#339

Earlier quoted context omitted.

But why do they care so much about this? Is it only for DRM on media playback?

I think there are a lot of parallels with what Reddit did. Reddit wanted to control how users consumed content on their site. To control the experience (i.e. monetize with ads), they had to shut down third-party clients, since those could remove ads. Google appears to be doing the same thing, but for the entire web. WEI is a way for sites that want to monetize with Google ads to prevent folks from accessing their sit…

Third-party clients could have been made to display ads, or they could have gated third-party client access behind Reddit Gold. That wasn't the problem.

The problem was that if you used a third-party client, Reddit would have to coordinate with them to launch whatever new stupid cryptocurrency scam they wanted to push that week. On a web browser they can just push new code into it[0], and their first-party mobile clients can be updated ahead-of-time with support for the feature. But third-party clients would have to spend their own development time adding stupid "click here to get your Snoovatar[1]" links. They could slow-walk that, or just not implement that, and Reddit would have to spend time and money kicking users off that third-party app.

This, incidentally, is why every other major social media platform bans third-party clients. Third-party clients are user agents, not platform agents.

[0] Which, incidentally, makes web browsers not user agents

[1] An NFT scam Reddit tried to pull

Re: Google is already pushing WEI into Chromium

#340

Is adding a feature-flag really the same as pushing the feature into the browser immediately? It can easily just be part of a SWE needing the flag in place in order to continue work without impacting anything else, even if that thing never ever launches. In general Google engineers don't tend to work on branches, especially long-running ones. Incremental small code reviews are the expectation. The general process wou…

When was the last time you heard Google or anything Google-related backing down from getting their paws in deeper? It's no longer a fallacy when there's a sign next to the slippery slope.

I worked in that code base. Things were feature flagged then murdered all the time.
Post reply on HN