Content deleted Content added
That's a separate action as part of being abandoned. The locking was before. Undid revision 1253968321 by Dwmalone (talk) |
→Reception: add refname to initial register coverage and furnish the citation |
||
Line 16:
== 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 name="register">{{Cite web |last=Claburn |first=Thomas |date=2023-07-25 |title=Google's next big idea for browser security
* 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>
| |||