Content deleted Content added
→Reception: No need for bulleted list Tag: Reverted |
WP:Embedded Lists: "indenting the paragraphs in list form may make them easier to read, especially if the paragraphs are very short." Undid revision 1183502980 by PhotographyEdits (talk) |
||
Line 17:
== Reception ==
The proposal received widespread criticism for limiting general purpose computing, with some comparing WEI to [[digital rights management]] (DRM).<ref>{{Cite web |last=Amadeo |first=Ron |date=2023-07-24 |title=Google's nightmare "Web Integrity API" wants a DRM gatekeeper for the web |url=https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/ |access-date=2023-07-26 |website=[[Ars Technica]] |language=en-us}}</ref> Others have accused the standard of being evidence of Google abusing Chrome's near-[[monopoly]] of browser share.<ref>{{Cite web |last=Claburn |first=Thomas |title=Google Web Environment Integrity draft draws developer rage |url=https://www.theregister.com/2023/07/25/google_web_environment_integrity/ |access-date=2023-08-19 |website=[[The Register]] |language=en}}</ref> Some have issued official statements on the matter in 2023
* On July 25, [[Mozilla]] opposed it, stating "Any browser, server, or publisher that implements common standards is automatically part of [[the Web]]{{nbsp}}... Mechanisms that attempt to restrict these choices are harmful to the openness of the Web ecosystem and are not good for users."<ref>{{Cite web |title=Request for Position: Web Environment Integrity API · Issue #852 · mozilla/standards-positions |url=https://github.com/mozilla/standards-positions/issues/852 |access-date=2023-07-26 |website=GitHub |language=en}}</ref> * On July 27, [[Vivaldi Technologies|Vivaldi]] opposed it as "simply dangerous" and feared that attestation providers would not be trustworthy.<ref>{{Cite web |date=2023-07-25 |title=Unpacking Google's new "dangerous" Web-Environment-Integrity specification |url=https://vivaldi.com/blog/googles-new-dangerous-web-environment-integrity-spec/ |access-date=2023-07-26 |website=Vivaldi Browser |language=en}}</ref> * On July 29, the [[Free Software Foundation]] opposed it as "an all-out attack on the free Internet" and claimed it would significantly limit the browsers that could be used.<ref>{{Cite web |first=Greg|last=Farough|date=2023-07-28 |title="Web Environment Integrity" is an all-out attack on the free Internet |url=https://www.fsf.org/blogs/community/web-environment-integrity-is-an-all-out-attack-on-the-free-internet |website=Free Software Foundation |access-date=2023-07-28 |language=en }}</ref> * On August 1, [[Brave (web browser)|Brave Software]] announced they will not include WEI in their web browser.<ref>{{Citation |last=Snyder |first=Peter |title="Web Environment Integrity": Locking Down the Web |date=2023-08-01 |url=https://brave.com/web-standards-at-brave/9-web-environment-integrity/ |access-date=2023-08-29 |language=en |mode=cs1}}</ref> * On August 7, the [[Electronic Frontier Foundation]] opposed it as "a bad idea that Google should not pursue" and opposed its proposal of selecting a "small percentage" of random users to simulate behavior without WEI in order to prevent websites from blocking unattested users. The EFF claimed that "[m]any websites will consider that 'small percentage' of users an acceptable price to pay" and feared Google would set the percentage extremely low to combat [[ad fraud]].<ref>{{Cite web |last1=Doctorow |first1=Cory |last2=Hoffman-Andrews |first2=Jacob |date=2023-08-07 |title=Your Computer Should Say What You Tell It To Say |url=https://www.eff.org/deeplinks/2023/08/your-computer-should-say-what-you-tell-it-say-1 |access-date=2023-08-07 |website=www.eff.org}}</ref> * On August 11, the [[World Wide Web Consortium]] refrained from taking a stance as it was "not being worked on in W3C, nor has there been any submission [for W3C] review".<ref>{{Cite web |date=2023-08-11|url=https://www.w3.org/blog/2023/web-environment-integrity-has-no-standing-at-w3c/|title=Web Environment Integrity has no standing at W3C; understanding new W3C work|access-date=2023-08-11|website=www.w3.org}}</ref> == See also ==
| |||