zlacker

Google is already pushing WEI into Chromium

submitted by topshe+(OP) on 2023-07-26 12:05:43 | 1376 points 786 comments
[view article] [source] [go to bottom]

NOTE: showing posts with links only show all posts
12. wasmy+l4[view] [source] 2023-07-26 12:33:32
>>topshe+(OP)
Another tame article in The Register:

https://www.theregister.com/2023/07/25/google_web_environmen...

Despite the spec's half-baked state, the blowback last week was swift – in the form of a flood of largely critical comments posted to the WEI GitHub repository, and abuse directed at the authors of the proposal. The Google devs' response was to limit comment posting to those who had previously contributed to the repo and to post a Code of Conduct document as a reminder to be civil.

The usual way to deal with opposition these days.

◧◩
21. foobar+M4[view] [source] [discussion] 2023-07-26 12:35:16
>>c0l0+h3
Is https://github.com/RupertBenWiser/Web-Environment-Integrity/... the best place to shame?
◧◩◪
28. thejos+j5[view] [source] [discussion] 2023-07-26 12:37:13
>>csomar+44
Cloudflare want to be the internets backbone. And they've honestly succeeded.

Now it's almost impossible to access websites in an automated way -- the CTO posted you can just email him (>>34639212 ) and he'll sort it. Because that scales.

edit: Mispoke about the CTO, said he would approve you, I was wrong. Apologies.

Their DNS is "privacy focused", but they provide "aggregated results" of domains. How is that privacy focused?

Cloudflare came from the approach of being a developers friend ("Look! SSL is now free!") but was given the internet on a silver platter.

◧◩◪
32. jvolkm+F5[view] [source] [discussion] 2023-07-26 12:38:57
>>BlargM+A4
https://killedbygoogle.com/
◧◩◪
43. jjoona+v6[view] [source] [discussion] 2023-07-26 12:43:21
>>foobar+M4
Yoav Weiss is closing concern threads, calling them "spam."

Ben Wiser ( https://benwiser.com ) turned off comments altogether.

58. andy99+p7[view] [source] 2023-07-26 12:47:30
>>topshe+(OP)
Has anyone come across a good nontechnical summary that could be shared more broadly?

Edit: the Register article linked elsewhere looks as good as it gets for now https://www.theregister.com/2023/07/25/google_web_environmen...

◧◩◪
69. shmde+n8[view] [source] [discussion] 2023-07-26 12:51:26
>>foobar+M4
https://github.com/chromium/chromium/commit/6f47a22906b28994...

Here.

◧◩
71. luuurk+p8[view] [source] [discussion] 2023-07-26 12:51:42
>>lagran+G7
"Apple already shipped attestation on the web, and we barely noticed"

>>36862494

76. itissi+C8[view] [source] 2023-07-26 12:53:41
>>topshe+(OP)
I am a bit confused. This sounds a bit stupid. If this is DRM for web content, then what would non chrome browsers like FF for web pages that ask for such authentication? Refusing to work with other browsers than chrome seems like a lawsuit waiting to happen.

[1]https://arstechnica.com/gadgets/2023/07/googles-web-integrit...

◧◩
77. JimDab+I8[view] [source] [discussion] 2023-07-26 12:54:01
>>dolive+O6
> I was watching a video about nesting in CSS and how it's just in Chrome

Nested CSS is supported in the latest version of all major browsers.

https://caniuse.com/css-nesting

◧◩◪◨
78. px43+N8[view] [source] [discussion] 2023-07-26 12:54:31
>>troupo+V6
> Google's open source projects are open in name only.

The link at the top of the page is pointing to the GitHub repo, where you can see literally over a million contributions from thousands of people working at hundreds of companies: https://github.com/chromium/chromium/commits/main

I've worked on both Chrome and Android (Chromium and AOSP) professionally, and never worked at Google.

◧◩
109. btown+5b[view] [source] [discussion] 2023-07-26 13:05:03
>>wasmy+l4
Also worth noting that this locks reactions (thumbs up, hearts, etc.) - providing plausible deniability that "only a small number of people raised concerns about specificTopicX." Journalists should be more aware of this!

On a separate note, for journalists and others who wish to communicate with the spec's author directly, his public website (which lists a personal email) is one of the other repos on the Github profile under which the specification was published. It's painfully absurd that he wrote this sentence 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 to install, I had to pay $99 for a developer account. Come on Apple, I know you want people to use the app story but this is just a little cruel. I basically have to pay $99 a year now just to keep using my little app.

[0] https://benwiser.com/blog/I-just-spent-%C2%A3700-to-have-my-...

◧◩◪
120. wsgeor+Kb[view] [source] [discussion] 2023-07-26 13:08:10
>>maxloh+n6
Not sure why you're getting downvoted, but this is a big deal IMO. We're here because Chrome has been the better product for a long time. Firefox not doing things people want well enough will hurt its adoption, which will impact its capacity to influence the Web.

Add to Mozilla's perceived not-very-good management and you have a death spiral on your hands, and more power to Google and Apple to shape the Web towards their interests.

FWIW, first-class profiles support matters a lot: https://medium.com/sort-of-like-a-tech-diary/profiles-the-on...

◧◩◪◨⬒
128. thesup+gc[view] [source] [discussion] 2023-07-26 13:10:17
>>kalleb+87
>> The same technology could easily be applied to simply blocking anyone who isn't verified

Sounds like a great way to enforce censorship:

- websites can deny access to unverified web browsers / web clients

- WEI-enforcing web browsers / web clients can refuse to go to unverified websites (not a stated goal, but it is a logical next step to boost website adoption of WEI APIs once a critical mass of clients is reached)

Google wants to build a wall around the Web and have their own walled garden:

https://youtu.be/Ag1AKIl_2GM?t=57

◧◩◪◨⬒
134. thejos+Nc[view] [source] [discussion] 2023-07-26 13:12:27
>>jgraha+3b
Sorry, this was wrong. I was a fool to post that without providing context and I apologise. I have updated my comment. I sometimes forget there are real people on the other side of the computer sometimes.

It was this thread, where you mentioned emailing: >>34639212

137. btown+Wc[view] [source] 2023-07-26 13:13:13
>>topshe+(OP)
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 to install, I had to pay $99 for a developer account. Come on Apple, I know you want people to use the app story but this is just a little cruel. I basically have to pay $99 a year now just to keep using my little app.

The double-think is absolutely astounding.

[0] https://benwiser.com/blog/I-just-spent-%C2%A3700-to-have-my-...

◧◩◪
151. mwill+0e[view] [source] [discussion] 2023-07-26 13:18:18
>>Pareto+n5
https://github.com/RupertBenWiser/Web-Environment-Integrity/...
◧◩
152. Alifat+3e[view] [source] [discussion] 2023-07-26 13:18:29
>>scott_+Bd
This is about WEI, Web environment integrity. The article below sums it up pretty good.

"The proposal suggests that websites should be able to request an attestation from the browser about its “integrity”. Such attestations are to be provided by external agents, which – presumably – examine the browser and its plugins, and issue an approval only if those checks pass.

The attestation is sent back to the website, which can now decide to deny service if the agent did not give approval." [1]

1. https://interpeer.io/blog/2023/07/google-vs-the-open-web

In other words, websites can now force you to comply with their shitty behaviour in order to allow you access, otherwise you get denided access.

158. encody+oe[view] [source] 2023-07-26 13:19:44
>>topshe+(OP)
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.

◧◩
162. pimter+Be[view] [source] [discussion] 2023-07-26 13:20:29
>>london+P6
That's currently just an idea in the 'Open questions' section of the spec, but there is already pushback against it from others closely involved in the spec & discussion around this (https://github.com/RupertBenWiser/Web-Environment-Integrity/...) and notably the attestation feature Google already shipped on Android for native apps in the same situation does _not_ do this.
◧◩
167. amalco+Se[view] [source] [discussion] 2023-07-26 13:21:07
>>ailef+73
This is essentially a backdoor attempt to TiVoize[0] web browsers. The only difference is that, instead of directly using hardware to prevent you from running a modified browser, the intent is to use network effects to accomplish the same thing.

[0]- https://en.wikipedia.org/wiki/Tivoization

◧◩◪
170. 38+Xe[view] [source] [discussion] 2023-07-26 13:21:28
>>foobar+M4
https://support.github.com/contact/report-abuse?category=rep...
◧◩◪
179. tomsch+Pf[view] [source] [discussion] 2023-07-26 13:25:15
>>coldpi+Hb
The FTC isn't going to do anything as Google/Alphabet is a big donor to the Democrats.

https://www.opensecrets.org/orgs/alphabet-inc/recipients?id=...

Here is them lobbying specifically around antitrust reform legislation: https://www.opensecrets.org/federal-lobbying/bills/specific_...

◧◩◪◨
184. coldpi+3g[view] [source] [discussion] 2023-07-26 13:26:12
>>soumya+Id
Citation for what, increased anti-trust activity from the FTC over the last two years? Sure, here's one article:

> Private equity deals and transactions in the healthcare and technology sectors continue to attract heightened antitrust scrutiny...

> The US agencies have also demonstrated an increased interest in challenging vertical transactions.

> In January 2022, for example, the FTC sued to block Lockheed Martin's US$4.4 billion proposed acquisition of Aerojet, which the parties subsequently abandoned.

> Increased enforcement, combined with the agencies' reluctance to approve remedies, has created an uncertain environment where commercial parties should be increasingly prepared to litigate mergers.

> The ramping up of antitrust enforcement in 2022...

https://www.whitecase.com/insight-our-thinking/us-ma-fy-2022...

Here's another:

> Since 2020, the Federal Trade Commission (FTC) and U.S. Department of Justice (DOJ) have filed multiple lawsuits against major tech companies...

> "The agencies have started laying the foundations for a more interventionist stance over the last two years, and this year is when we'll start to see some of those efforts come to fruition -- or be stopped in their tracks by the courts," Kass said.

https://www.techtarget.com/searchcio/news/252528606/FTC-push...

I'm sure you can find more.

◧◩
187. kmeist+bg[view] [source] [discussion] 2023-07-26 13:26:38
>>london+P6
The antifraud company that worked with Google on the WEI proposal is already calling for the removal of holdouts from the spec[0], because:

- Attestation does not work as an antifraud signal unless it is mandatory - fraudsters will just pretend to be a browser doing random holdout otherwise.

- The banks that want attestation do not want you using niche browsers to login to their services.

[0] https://github.com/RupertBenWiser/Web-Environment-Integrity/...

◧◩◪◨
201. coldpi+Sg[view] [source] [discussion] 2023-07-26 13:29:27
>>tomsch+Pf
So are Amazon:

https://www.opensecrets.org/orgs/amazon-com/recipients?id=D0...

and Microsoft:

https://www.opensecrets.org/orgs/microsoft-inc/recipients?id...

And yet we see high profile activity against them from the current FTC.

◧◩◪
224. zoul+qi[view] [source] [discussion] 2023-07-26 13:35:36
>>insani+1i
Similar feature is already in production Safari, alas: https://httptoolkit.com/blog/apple-private-access-tokens-att...
◧◩◪◨
225. anders+vi[view] [source] [discussion] 2023-07-26 13:35:45
>>lagran+hd
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-...
230. A4ET8a+5j[view] [source] 2023-07-26 13:37:49
>>topshe+(OP)
Can you give me an idea as to why WEI is a bad idea for the web? Granted, it is morning, but as I am going through the notes linked ( https://googlechrome.github.io/OriginTrials/developer-guide.... ), I am not sure I understand why it is that bad.
◧◩◪◨⬒⬓
233. coldpi+oj[view] [source] [discussion] 2023-07-26 13:39:36
>>Mounta+5i
Okay, here's your alarm clock going off:

"FTC rewrites rules on Big Tech mergers with aim to ease monopoly-busting"

https://arstechnica.com/tech-policy/2023/07/ftc-rewrites-rul...

"FTC prepares “the big one,” a major lawsuit targeting Amazon’s core business"

https://arstechnica.com/tech-policy/2023/06/ftc-prepares-the...

"The Federal Trade Commission sued Amazon today, claiming the online giant violated US law by tricking consumers into signing up for the $14.99-per-month Amazon Prime subscription service and making it annoyingly difficult to cancel."

https://arstechnica.com/tech-policy/2023/06/ftc-sues-amazon-...

"FTC files to block Microsoft’s $69B Activision Blizzard acquisition"

https://arstechnica.com/gaming/2023/06/report-ftc-will-file-...

"A Federal Trade Commission lawsuit filed yesterday accused Ring, the home security camera company owned by Amazon, of invading users' privacy"

https://arstechnica.com/tech-policy/2023/06/ftc-amazon-ring-...

"Microsoft will pay $20 million to settle an FTC complaint that its Xbox platform illegally collected and retained information about children without their parents' consent"

https://arstechnica.com/gaming/2023/06/xbox-coppa-violations...

And that's all just from one news source, in the last three months.

◧◩◪◨
240. coldpi+Qj[view] [source] [discussion] 2023-07-26 13:41:05
>>Mounta+Ph
> How much of that involves the tech industry?

A lot. Here's a link where you can read about some recent activity in the tech industry (change it to sort by Date, I couldn't figure out how to do that in the URL): https://arstechnica.com/search/?ie=UTF-8&q=ftc You can probably find more on Google (or perhaps Duck Duck Go? :) ).

◧◩◪◨⬒
251. kyrra+Qk[view] [source] [discussion] 2023-07-26 13:44:32
>>coldpi+3g
Except they keep losing cases. ex:

https://www.reuters.com/legal/us-appeals-court-opens-docket-...

Or Judges fast-tracking lawsuits to allow those being prosecuted by the FTC to get things over quicker, ex: https://www.reuters.com/legal/illumina-wins-fast-track-appea...

And I think the biggest blow may actually come about because of the SEC lawsuit that will be heard this upcoming term at SCOTUS: https://www.reuters.com/legal/us-supreme-court-decide-legali..., which will likely heavily reign in the power of administrator judges and the ability for an agency to keep initial fights in-house (blocking litigants from taking fights to the normal courts).

253. lolind+Yk[view] [source] 2023-07-26 13:44:55
>>topshe+(OP)
As wonderful as it has been to have a platform that the entire world is on at once, I'm beginning to conclude that the only way to get back to the web as we knew it is to go back to the days when only a small, geeky subset of the population spent time on here. Back then it wasn't worth it to create massive amounts of garbage content in order to serve ads to unwary search engine users—there weren't enough of us to make money off of!

I think it's time to establish a successor to the web that we can once again call home. This doesn't mean we need to give up on the web or stop using it—it can run in parallel to the mainstream, a niche home for hackers and techies and people who care about freedom. It needs to be simple, like Gemini [0], but also have enough interactive features to enable old-school social apps like HN or the old Reddit. It should have a spec and a governance process that discourages rapid changes—we've learned from hard experience that more features does not mean better.

I realize this sounds like a cop out, and that getting people to use such a thing in sufficient numbers would be extremely difficult. But I'm pretty convinced at this point that the web as we knew it will never come back unless there's a reset—unless we create a new niche tech that isn't big enough for corporations to want to take over.

[0] https://gemini.circumlunar.space/

◧◩◪◨⬒
268. kmeist+Gm[view] [source] [discussion] 2023-07-26 13:51:51
>>tenpie+n7
Yes. Cloudflare was irresponsible in fighting to keep 8chan, Daily Stormer, and Kiwifarms up as long as they did. Every other ISP with a competent abuse desk dropped them. If you don't think that's bad, then let me remind you that back in 2012, Malwarebytes actually had a policy of blocking all Cloudflare services specifically because they were hosting malware and refused to remove it[0]. The excuse Cloudflare used for not removing malware from their network was the same language used to justify keeping the aforementioned sites operational. If Cloudflare was paid to run the Great Firewall of China they'd bend over backwards to try and claim it was to protect Xi Jinping's freedom of speech.

Remember that moderators can be abusive not just in terms of removing content that shouldn't be removed, but also by forcing you to accept things that harm you. Moderation is a trust relationship because I'm delegating my own personal decision to accept or block traffic/content/etc to someone else. Cloudflare is not trustworthy.

Cloudflare also used to be a big pain in the ass for Tor/VPN users because competent DDoS protection requires some kind of traceable identity. Their solution was Privacy Pass - an extension that let you pre-solve their CAPTCHAs. However, this wasn't good enough, so their next solution... was to literally partner with Apple to implement Web Environment Integrity, years before Google even proposed it. Nobody noticed this - not even me - because it was sold as a way to make CAPTCHAs less annoying. It was literally the trojan horse Google could only dream of building.

[0] https://forums.malwarebytes.com/topic/108447-my-site-using-c...

◧◩◪◨
274. qjx+4n[view] [source] [discussion] 2023-07-26 13:53:03
>>jjoona+v6
Yoav Weiss has a blog post from 6 days ago on his website. https://blog.yoav.ws/

for a personal blog it has quite a lot of PR speak

◧◩◪◨
278. refulg+kn[view] [source] [discussion] 2023-07-26 13:54:36
>>tomsch+Pf
? This is provably false. FTC filed 6 months ago.

https://www.nytimes.com/2023/01/24/technology/google-ads-law...

n.b. I've found a lot of comfort by conciously rolling away from any subject that leads me to do "They"-ing, i.e. name an enormously large group, then talk about them as a unit. The more I avoid it, the more I realize how prevalent it became and drives how a lot of us feel society shifted.

◧◩
280. easyTh+sn[view] [source] [discussion] 2023-07-26 13:54:56
>>tolmas+We
Quite frankly, the W3C stopped having any say on the matter when the WHATWG supplanted the XHTML standard with the HTML5 committee.

They had enough weight at the time to say "The Web is XHTML2, you can make your own internet if you want " compared to what they can bargain for these days.

Maybe at the time it was a somewhat reasonable decision to abdicate their responsibility over to big internet companies, but that's what brought us to the current state where we're basically going back to original version of The Microsoft Network[1].

[1]http://www.codersnotes.com/notes/the-microsoft-network/

◧◩◪◨⬒
281. burkam+un[view] [source] [discussion] 2023-07-26 13:55:01
>>coldpi+Sg
And Meta: https://www.opensecrets.org/orgs/meta/recipients?id=D0000335..., https://www.ftc.gov/legal-library/browse/cases-proceedings/0...

And Intuit: https://www.opensecrets.org/orgs/intuit-inc/recipients?id=D0..., https://www.ftc.gov/legal-library/browse/cases-proceedings/1...

And Epic: https://www.opensecrets.org/orgs/epic-systems/recipients?id=..., https://www.ftc.gov/legal-library/browse/cases-proceedings/1...

etc. etc.

286. ricard+Xn[view] [source] 2023-07-26 13:57:07
>>topshe+(OP)
fwiw I found Vivaldi's overview a good primer on the situation.

https://vivaldi.com/blog/googles-new-dangerous-web-environme...

◧◩◪◨⬒⬓
288. coldpi+9o[view] [source] [discussion] 2023-07-26 13:57:48
>>yyyk+Ll
I don't see anything significant from the FTC specifically regarding Google, but there is an ongoing DOJ lawsuit. Possibly they don't want to step on that? I admit I don't really understand the roles of the DOJ versus the FTC regarding anti-trust enforcement. https://www.justice.gov/opa/pr/justice-department-sues-googl...
290. danlin+jo[view] [source] 2023-07-26 13:58:35
>>topshe+(OP)
The web is not dying, it is being killed. And the people that are killing it have names and addresses.

Shame on Rayan Kanso <rayankans@chromium.org>

Shame on Peter Pakkenberg <pbirk@chromium.org>

Shame on Dmitry Gozman <dgozman@chromium.org>

Shame on Richard Coles <torne@chromium.org>

Shame on Kinuko Yasuda <kinuko@chromium.org>

Shame on Rupert Ben Wiser: https://github.com/RupertBenWiser/Web-Environment-Integrity

Google needs to be broken up.

◧◩
309. mdibai+0q[view] [source] [discussion] 2023-07-26 14:03:58
>>encody+oe
For people who want to put something like this, here is the code snippet:

  <span id='browser' class='hidden'>
    This website is designed for <a target="_blank" rel="noopener noreferrer" href="https://firefox.com/">Firefox</a>, a web browser that respects your privacy.
  </span>

  <script>
    if (window.chrome) {
      document.getElementById('browser').className = '';
    }
  </script>
Class .hidden must hide the element somehow, in this case I do:

  .hidden { display: none; }
◧◩◪◨⬒⬓
315. bradle+Lq[view] [source] [discussion] 2023-07-26 14:06:58
>>jsjohn+2b
As someone who worked in this space at the time (Webmaster at Spry, Inc. in 1994), and we sold a web browser in the 1994-ish timeframe https://en.wikipedia.org/wiki/IBox, no, saying "almost 3 decades" isn't hyperbolic at all. 29 years is close enough.
◧◩◪◨
320. zaggyn+9r[view] [source] [discussion] 2023-07-26 14:07:53
>>xyzal+Ag
Have at it: https://european-union.europa.eu/contact-eu/write-us_en

I'm having trouble grasping how WEI works, providing examples of what would and could happen and what to ask/tell the EU specifically.

From my limited understanding it would mean the lockout of people with non-compliant hardware/software, greatly increase the fingerprinting of web browser users and further vendor lock in to Google as a company?

◧◩◪
349. otikik+Lu[view] [source] [discussion] 2023-07-26 14:21:59
>>larata+S5
https://www.purewow.com/wellness/what-is-tone-policing
◧◩◪◨
352. Utopia+av[view] [source] [discussion] 2023-07-26 14:23:24
>>Renaud+xk
In addition to just using Firefox, people can donate to the Mozilla Foundation. I give a few bucks every month.

https://foundation.mozilla.org/en/who-we-are/

◧◩◪◨⬒⬓
374. notpus+1y[view] [source] [discussion] 2023-07-26 14:35:14
>>coffee+Tm
How about Jitsi? https://meet.jit.si/

It's free and open source, works everywhere, has stuff like background replacement, and doesn't require signup at all.

◧◩◪◨⬒
405. nobody+6C[view] [source] [discussion] 2023-07-26 14:51:18
>>qjx+4n
HN Discussion of the blog post:

>>36857676

85 points by KoftaBob 1 day ago | flag | hide | past | favorite | 109 comments

◧◩
417. dontre+tD[view] [source] [discussion] 2023-07-26 14:56:42
>>devsda+Iu
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/...

◧◩◪
456. beckle+8N[view] [source] [discussion] 2023-07-26 15:27:36
>>asciim+Dc
Getting some "PLEASE DRINK VERIFICATION CAN" vibes...

https://imgur.com/dgGvgKF

◧◩◪◨
464. smarx0+pP[view] [source] [discussion] 2023-07-26 15:35:43
>>38+Xe
I think the right avenue is to complain to W3C instead. Especially in the light of https://www.w3.org/TR/2023/DNOTE-w3c-vision-20230725/#princi... and violation of CoC https://www.w3.org/Consortium/cepc/#unacceptablebehavior ("Sustained disruption of discussion.")

The problem is that the proposal has not yet been brought to W3C.

482. pzo+CU[view] [source] 2023-07-26 15:53:27
>>topshe+(OP)
Not sure how exactly ad fraud works but why this WEI supposed to even prevent it? There are many tools that allow to control your mouse and keyboard programatically like pyautogui [0].

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

[0] https://github.com/asweigart/pyautogui

[1] https://github.com/bsiever/microbit-pxt-blehid

◧◩◪◨⬒⬓⬔
485. teddyh+vV[view] [source] [discussion] 2023-07-26 15:56:12
>>Pawger+oy
Is it still slow for you? Have you tested it recently?

<>>35458746 >

◧◩◪
491. teddyh+NW[view] [source] [discussion] 2023-07-26 16:00:19
>>userbi+Rg
Even before that, there was “The Digital Imprimatur”: <https://www.fourmilab.ch/documents/digital-imprimatur/>
◧◩
498. strix_+lY[view] [source] [discussion] 2023-07-26 16:05:27
>>Pannon+Dg
Agreed - if anyone else is curious to see Google's "side" (motivations, technical or otherwise), here's the explainer:

https://github.com/RupertBenWiser/Web-Environment-Integrity/...

It's nakedly user-hostile. A blatant attempt to invert the "user agent" relationship such that the agent works for the advertiser/corporation/government to spy on the human behind the screen. The way the intro paragraph tries to disguise this as something users need or want is frankly disgusting:

> Users often depend on websites trusting the client environment they run in. This trust may assume that the client environment is honest about certain aspects of itself, keeps user data and intellectual property secure, and is transparent about whether or not a human is using it. This trust is the backbone of the open internet, critical for the safety of user data and for the sustainability of the website’s business.

Ugh. Here's a fixed, honest version:

Corporations like Google often depend on advertisers knowing as much as possible about their users. Their revenue may depend on fingerprinting the client environment, tracking their behavior and history, and attesting that a human with sufficient disposable income is behind the keyboard. This personal data mining is the backbone of Google's business model, critical for their continued dominance of the web and for the sustainability of their enormous margins.

◧◩◪◨⬒⬓⬔
503. saurik+IY[view] [source] [discussion] 2023-07-26 16:06:40
>>Bizarr+tR
The same thing can be said about the opposite stance you are taking. The question is: do we already know things, and how easy are the things we don't already know to look up?

Regardless, I have Googled this for you: please return the favor by helping others learn to use search engines in the future before leaving comments insinuating that they are lying.

The tldr (as you'll probably insist on that also) is that Firefox finds Mozilla, not the other way around, as the latter is a non-profit while the former is a FOR-profit, so Mozilla actually can't directly fund Firefox.

https://www.reddit.com/r/firefox/comments/ow9k0y/is_there_a_...

https://www.reddit.com/r/firefox/comments/a98gmi/donations_t...

>>24200395

512. 4oo4+X31[view] [source] 2023-07-26 16:28:12
>>topshe+(OP)
Don't just comment and complain, contact your antitrust authority today:

US:

- https://www.ftc.gov/enforcement/report-antitrust-violation

- antitrust@ftc.gov

EU:

- https://competition-policy.ec.europa.eu/antitrust/contact_en

- comp-greffe-antitrust@ec.europa.eu

UK:

- https://www.gov.uk/guidance/tell-the-cma-about-a-competition...

- general.enquiries@cma.gov.uk

India:

- https://www.cci.gov.in/antitrust/

- https://www.cci.gov.in/filing/atd

◧◩
516. hot_gr+l61[view] [source] [discussion] 2023-07-26 16:36:05
>>c0l0+h3
Just saw https://github.com/chromium/chromium/pull/187/files

It's even funnier with the auto-reply "Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA)."

◧◩
527. dang+le1[view] [source] [discussion] 2023-07-26 17:04:49
>>c0l0+h3
> constantly and relentlessly shame and even harass all those involved in helping create it

Not on HN, please. I realize that you're trying to protect something you care about (and that maybe we all care about) but this leads to ugly mob behavior that we don't want and won't allow here.

https://news.ycombinator.com/newsguidelines.html

◧◩
528. dang+6f1[view] [source] [discussion] 2023-07-26 17:07:19
>>danlin+jo
No personal attacks, please. It's not what this site is for, and destroys what it is for.

You can make your substantive points without that, as most other users in this thread have been doing.

You may not owe web-destroying $MegaCorp better, but you owe this community better if you're participating in it.

https://news.ycombinator.com/newsguidelines.html

◧◩◪◨
557. slig+3n1[view] [source] [discussion] 2023-07-26 17:34:48
>>matkon+zj1
Less than 5% of global usage [1], and no presence whatsoever on mobile. Pretty much dead.

[1]: https://radar.cloudflare.com/adoption-and-usage And CF stats doesn't depend on JavaScript.

564. rolph+6p1[view] [source] 2023-07-26 17:41:33
>>topshe+(OP)
https://www.ftc.gov/about-ftc/contact
◧◩
574. dang+Kq1[view] [source] [discussion] 2023-07-26 17:46:11
>>ricard+Xn
Thanks. Let's discuss that article here: >>36875940 .
◧◩
579. dang+rs1[view] [source] [discussion] 2023-07-26 17:51:29
>>ep103+k5
We detached this subthread from >>36876504 since that thread broke the site guidelines and this one didn't.
◧◩◪
580. burkam+us1[view] [source] [discussion] 2023-07-26 17:51:43
>>hoover+oi1
My email:

Google has proposed a new Web Environment Integrity standard, outlined here: https://github.com/RupertBenWiser/Web-Environment-Integrity/....

This standard would allow Google applications to block users who are not using Google products like Chrome or Android, and encourages other web developers to do the same, with the goal of eliminating ad blockers and competing web browsers.

Google has already begun implementing this in their browser here: https://github.com/chromium/chromium/commit/6f47a22906b28994....

Basic facts:

1. Google is a developer of popular websites such as google.com and youtube.com (currently the two most popular websites in the world according to SimilarWeb)

2. Google is the developer of the most popular browser in the world, Chrome, with around 65% of market share. Most other popular browsers are based on Chromium, also developed primarily by Google.

3. Google is the developer of the most popular mobile operating system in the world, Android, with around 70% of market share.

Currently, Google's websites can be viewed on any web-standards-compliant browser on a device made by any manufacturer. This WEI proposal would allow Google websites to reject users that are not running a Google-approved browser on a Google-approved device. For example, Google could require that Youtube or Google Search can only be viewed using an official Android app or the Chrome browser, thereby noncompetitively locking consumers into using Google products while providing no benefit to those consumers.

Google is also primarily an ad company, with the majority of its revenue coming from ads. Google's business model is challenged by browsers that do not show ads the way Google intends. This proposal would encourage any web developer using Google's ad services to reject users that are not running a verified Google-approved version of Chrome, to ensure ads are viewed the way the advertiser wishes. This is not a hypothetical hidden agenda, it is explicitly stated in the proposal:

"Users like visiting websites that are expensive to create and maintain, but they often want or need to do it without paying directly. These websites fund themselves with ads, but the advertisers can only afford to pay for humans to see the ads, rather than robots. This creates a need for human users to prove to websites that they're human, sometimes through tasks like challenges or logins."

The proposed solution here is to allow web developers to reject any user that cannot prove they have viewed Google-served ads with their own human eyes.

It is essential to combat this proposal now, while it is still in an early stage. Once this is rolled out into Chrome and deployed around the world, it will be extremely difficult to rollback. It may be impossible to prevent this proposal if Google is allowed to continue owning the entire stack of website, browser, operating system, and hardware.

Thank you for your consideration of this important issue.

◧◩◪
581. dang+Ms1[view] [source] [discussion] 2023-07-26 17:52:29
>>foobar+M4
> the best place to shame?

Please don't do this here. It's not what this site is for, and destroys what it is for.

Edit: I suppose I need to add—no, we're not pro-$MegaCorp or pro-$web-destroying-dystopia. We're just trying to have an internet forum that doesn't suck, and you guys need to make your substantive points without degenerating into mob behavior.

https://news.ycombinator.com/newsguidelines.html

◧◩◪◨
584. dang+gt1[view] [source] [discussion] 2023-07-26 17:54:12
>>jjoona+v6
Please don't do this here. It's not what this site is for, and destroys what it is for.

Edit: I suppose I need to add—no, we're not pro-$MegaCorp or pro-$web-destroying-dystopia. We're just trying to have an internet forum that doesn't suck, and you guys need to make your substantive points without degenerating into mob behavior.

https://news.ycombinator.com/newsguidelines.html

◧◩◪◨
588. dang+7u1[view] [source] [discussion] 2023-07-26 17:57:05
>>MSFT_E+lt
Please don't do this here.

More explanation:

>>36881929

>>36881081

>>36881034

◧◩◪◨
592. dang+xu1[view] [source] [discussion] 2023-07-26 17:58:17
>>pseg13+Ai
Please don't do this here.

More explanation:

>>36881929

>>36881081

>>36881034

In addition: could you please stop posting unsubstantive comments and flamebait generally? You've unfortunately been doing it repeatedly. It's not what this site is for, and destroys what it is for.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

◧◩
600. DanHul+Nv1[view] [source] [discussion] 2023-07-26 18:02:59
>>4oo4+X31
Canada: - https://www.competitionbureau.gc.ca/eic/site/cb-bc.nsf/frm-e...
◧◩◪
603. Eduard+Bw1[view] [source] [discussion] 2023-07-26 18:05:30
>>solard+ai1
> The W3C is already irrelevant, not that it ever mattered much.

This sounds myopic, or what do you mean? W3C is not only about HTML and CSS innovation, but is responsible for and/or involved in a diverse set of relevant standards — many of which "big companies" don't show as much interest in contributing to.

https://en.m.wikipedia.org/wiki/World_Wide_Web_Consortium#St...

605. aaronc+Kw1[view] [source] 2023-07-26 18:05:55
>>topshe+(OP)
I'm curious what Brave says to my issue: https://github.com/brave/brave-browser/issues/31897
644. rolph+nD1[view] [source] 2023-07-26 18:30:09
>>topshe+(OP)
How to Email to the President and Members of Congress

https://www.einvestigator.com/government-email-addresses/ [2022]

this abuse of tech, potentially goes beyond antitrust, and damages global economic wellbeing, as well as impoverishing information systems on global scale, generating isolation, ignorance, division, and radicalization.

657. esafak+EF1[view] [source] 2023-07-26 18:38:33
>>topshe+(OP)
WEI stands for Web Environment Integrity:

https://en.wikipedia.org/wiki/Web_Environment_Integrity

◧◩◪◨
675. burkam+HM1[view] [source] [discussion] 2023-07-26 19:04:58
>>minsc_+fl1
No, Google has plenty of skilled engineers that can make spoofing an attestation extremely difficult. It will probably rely on hardware that you cannot modify. See details of a plausible implementation here: >>36859465
◧◩◪◨⬒⬓⬔
683. nobody+RR1[view] [source] [discussion] 2023-07-26 19:25:20
>>solard+nq1
>If we're arguing about whether 4% global usage constitutes dead, then yes, it's truly dead and Mozilla is completely irrelevant. Even Microsoft is more important these days (again).

According to these folks[0], Firefox has a 3.29% market share globally. They also claim there are 4.66 billion browser users globally.

If those numbers are correct, Firefox has a bit more than 150,000,000 users worldwide.

If my software had 150,000,000 users, I'd consider that wildly successful.

Other folks have different ideas/takes on that, I suppose. But it's food for thought nonetheless.

[0] https://backlinko.com/browser-market-share#worldwide-browser...

Edit: Fixed prose.

◧◩◪
688. danShu+AV1[view] [source] [discussion] 2023-07-26 19:41:31
>>izacus+vx
> and you all were quiet as a mouse as well, with HN actively defending Apple Safari monopoly with this feature enabled

Citation? To be sure, there was not universal outrage over Safari's attestation implementation, but out of curiosity I looked up the only thread I was aware of, in part because I couldn't remember what my reaction was at the time. That thread was a year ago and the overwhelming sentiment of the comments section is critical: >>31751203

Here were my comments at the time:

- >>31752980

- >>31753257

- >>31752431

They're less forceful than they are now with Google, partially because I know more now about how attestation works than I did over a year ago, and partially because (as some people have also pointed out) Chrome's implementation is straightforwardly more dangerous than Apple's is.

But HN "actively defending" Safari? That's not the impression I get from the overall comment section and it's definitely not what I personally was doing. There are a lot of people in these comments calling Apple's implementation DRM. So I'm a little skeptical of the "nobody on HN cared about this with Safari" narrative that has sprung up; from what I can see media coverage was fairly positive, but people on HN were rightly critical. I'm not sure the facts match the narrative: Safari was criticized for this.

It's a fair critique that there wasn't a coordinated attempt to outright stop Apple, but I would once again remind everyone that attestation in Chrome is way more dangerous than attestation in iOS. The market matters, that's not context that can be ignored. So it's not really all that weird to me that people are more willing to react more strongly to abusive behavior in Chrome.

◧◩
699. ethanj+S22[view] [source] [discussion] 2023-07-26 20:08:28
>>4oo4+X31
Thank you so much for your call to action; just emailed antitrust@ftc.gov.

For any experiencing barriers for writing the email, my method is below; Bing Chat generated an excellent email that only needed a bit of editing.

1. Open https://vivaldi.com/blog/googles-new-dangerous-web-environme... page in (ugh) Edge.

2. Open Bing Chat sidebar (top right corner); it auto-summarizes the article.

3: My prompt: Using the that webpage summary, please write a letter reporting Alphabet for antitrust violation. Please include the following [this language is from the ftc.gov site]:

Q: What companies or organizations are engaging in conduct you believe violates the antitrust laws? A: Alphabet

Q: Why do you believe this conduct may have harmed competition in violation of the antitrust laws? A: [use the article]

Q:What is your role in the situation? A: I'm a user of the Firefox browser

[edit: line breaks for readability]

◧◩
705. bfelbo+j72[view] [source] [discussion] 2023-07-26 20:26:09
>>4oo4+X31
I think https://competition-policy.ec.europa.eu/antitrust/procedures... would be better for contacting EU antitrust.

Here you can specifically create new antitrust complaints.

◧◩◪◨
707. arakna+G82[view] [source] [discussion] 2023-07-26 20:31:37
>>burkam+us1
Thanks for sharing! I just sent to https://competition-policy.ec.europa.eu/antitrust/contact_en
◧◩◪
712. strong+3h2[view] [source] [discussion] 2023-07-26 21:07:50
>>hannia+jB1
Not exactly a nutshell, but here's an explainer:

https://github.com/RupertBenWiser/Web-Environment-Integrity/...

And here's why it may be bad:

https://vivaldi.com/blog/googles-new-dangerous-web-environme...

And the HN discussion on the latter:

>>36875940

◧◩◪◨⬒
728. square+VG2[view] [source] [discussion] 2023-07-26 23:33:47
>>slig+3n1
Linux market share on the desktop was 3.08% on June (source:0). I don't see it dying anytime soon because of that. Firefox isn't pushed by Google, hence the much smaller adoption; it's not about quality but rather which one is being advertised the most.

0: https://gs.statcounter.com/os-market-share/desktop/worldwide

◧◩◪
730. cpeter+GJ2[view] [source] [discussion] 2023-07-26 23:52:47
>>freedo+tx1
Mozilla posted its position on Google’s Web Environment Integrity API here:

Mozilla opposes this proposal because it contradicts our principles and vision for the Web. Any browser, server, or publisher that implements common standards is automatically part of the Web. ... Mechanisms that attempt to restrict these choices are harmful to the openness of the Web ecosystem and are not good for users.

The full response is here:

https://github.com/mozilla/standards-positions/issues/852#is...

◧◩◪◨⬒⬓
733. cpeter+0M2[view] [source] [discussion] 2023-07-27 00:08:47
>>rileym+nb
If a website doesn’t work in Firefox (due to a bug in Firefox or the website or because the website blocks Firefox), please file a bug report on https://webcompat.com/

Mozilla developers will then try to reach out to the website’s owners, add a fix or workaround in Firefox, or (as a last resort) spoof Chrome’s User-Agent string to bypass the website’s Firefox block.

◧◩◪◨
739. anders+TZ2[view] [source] [discussion] 2023-07-27 01:48:30
>>calgar+tV2
Perhaps this specific proposal is only Google's doing, but the concept in general, absolutely.

For example, these provide essentially the same attestation service for native apps consuming APIs, validating that the phone is not rooted, and the OS and app are unmodified:

https://developer.android.com/google/play/integrity

https://developer.apple.com/documentation/devicecheck/

Apple and Cloudflare combined to take it to the browser last year and basically no one noticed:

https://blog.cloudflare.com/eliminating-captchas-on-iphones-...

Of course that will be hooked up to Google's new thing as soon as possible!

Microsoft has also been preparing it with the whole TPM integration in Windows 11 and mandatory inclusion of such hardware in all prebuilt PCs since ~2015. That's what the Chromium integration builds on - Google can't actually do the foundation for this themselves on Windows.

You can absolutely bet that all of these companies are on board with whatever Google is doing.

◧◩◪◨⬒⬓⬔
752. troupo+2o3[view] [source] [discussion] 2023-07-27 05:32:59
>>joshua+BX2
>>36884155

And this particular feature? They want to pretend it's s standard. You don't create a spec proposal for a feature you don't just develop internslly

◧◩◪◨⬒⬓⬔⧯
760. notpus+GM3[view] [source] [discussion] 2023-07-27 09:03:24
>>FooBar+UC
I've watched Louis Rossmann's video on Jitsi a couple weeks ago: https://www.youtube.com/watch?v=Nzt0tzsaWDE

He provides a nice piece of anecdata there: for one-on-one meetings, you can just send people a link and usually they just join. Even if they've sent a link to Zoom or Meet or whatever, you still can say “hey, join this instead” and it will work. I haven't tried this yet, but sounds plausible to me.

◧◩◪◨
773. dang+9o5[view] [source] [discussion] 2023-07-27 17:24:12
>>propog+RE4
We didn't shadowban it. We told you we were banning it and why: >>36134639 .
◧◩◪◨⬒⬓⬔⧯▣
780. troupo+T69[view] [source] [discussion] 2023-07-28 18:43:08
>>joshua+3I5
> You seem to be taking things that are factual, normal, everyday, aspects of the WHATWG working process and trying to imply that chrome is doing something unusual, or untoward with its process here, but it isn't. It's doing what is necessary to make a proposal with WHATWG: have a trial.

And yet, we've seen many such proposals go through this process because Chrome is paying lip service to it. Whatever Google wants it ships. And Google wants this.

As an adjacent (ads- and tracking-related) example: Google's FLoC flopped, hard. So they immediatey shipped the replacement Topics API [1] despite there being no consensus. E.g. Firefox is against [2] (but Chrome presents Firefox's position as "No signal" in the feature status). And despite the fact that its status is literally "individual proposal, not accepted" [3]

Do not assume any good intent on Google's part when it comes to Google's business interests. Their intent is always malicious until proven otherwise. And there have been fewer and fewer cases when they have been proven otherwise.

[1] https://chromestatus.com/feature/5680923054964736

[2] https://github.com/mozilla/standards-positions/issues/622

[3] https://github.com/patcg-individual-drafts/topics

◧◩◪◨⬒⬓⬔
783. derefr+uCh[view] [source] [discussion] 2023-07-31 15:25:09
>>ddalex+vv4
Even in that case, your computer is still an arbitrarily-programmable Turing machine; it contains this one hardwired + proprietary component that the remote end is looking to speak to, but that component isn't in control of the system; rather, it's controlled by the system. This just moves the job of deception one target over. Rather than just turning the logic sent by the remote end into a "brain in a vat" fed a false reality by your Cartesian https://en.wikipedia.org/wiki/Evil_demon of a custom OS, you also turn its local emissary, the DRM TPM chip, into another "brain in a vat" fed lies by an enclosing evil-demon hardware platform.

The only way this attack can even be avoided in principle is to restrict distribution of the DRM TPM chip — ala Nintendo's NES CIC lockout chip that never left Nintendo's hands except in the form of finished first-party-assembled game cartridges. But even that only prevents mass production and sale of devices that defeat your DRM; any sufficiently motivated attacker can still buy a legitimate device from you that includes the DRM TPM chip, rip the DRM TPM chip out, and feed it to their evil-demon hardware to enable it to faithfully attest a lie over the network.

In short: if this was truly a practical additional layer of defense, there'd be tons of use-cases for it — game consoles, set-top boxes, kiosk computing (e.g. ATMs), etc.

But you don't see anyone using DRM TPM chips for these systems, because it's not a practical additional layer of defense: such chips would increase BOM for these systems, while only defending against attacks that weaker defenses (namely software DRM, or programmable-firmware DRM like Intel SGX) already defend against; and while not doing anything more to stop the truly motivated attackers than current layers of defense already do — as your Netflix pirate media-scraping bots, your EVE Online gold-farming bots, etc. all have the monetary incentive and capital to invest to build exactly these evil-demon systems.

[go to top]