5 ms·
>Additionally, the use cases listed depend on the ability to “detect non-human traffic” which as described would likely obstruct many existing uses of the Web s
by charcircuit 3y ago
>Additionally, the use cases listed depend on the ability to “detect non-human traffic” which as described would likely obstruct many existing uses of the Web such as assistive technologies, automatic testing, and archiving & search engine spiders.
Assistive technologies will still work as the browsers implement platform's assistive APIs.
Automatic testing will still work because a developer isn't going to add restrictions to their own tests from their site. Unless they are testing if a captcha gets shown from an unsafe environment.
Archives, search engines, and spiders should already be respecting robots.txt. Site owners can already block those things if they don't want their site crawled.
>This means that no single party decides which form-factors, devices, operating systems, and browsers may access the Web.
The proposal allows anyone to become an attestor. There would not be a single attestor who you would have to prove your trustworthiness to.
- kmeisthax 3y ago>There would not be a single attestor who you would have to prove your trustworthiness to. Either this protocol is useless for its intended purpose, or banks will only accept a small handful of attestors that promise not to sign for environments where the owner has control. Being able to create a new attestor means nothing because attestation is not valuable without pre-established trust. The fraud prevention use case requires that the browser matches what Google or Mozilla shipped, not what I choose to actually run. From 10,000 feet in the sky, there's zero difference between, say, someone who installed modified software on their phone to protect their privacy and someone who was tricked into installing malware[0]. Banks don't care about your freedom, they care about making your fraud someone else's fault. Some of the use cases explicitly call for locking the owner out of their device too. Anticheat in games is treated as at least beneficial to honest users, but it can still be user hostile[1]. Click fraud detection shouldn't even be something that a USER agent cares about - and it's not like Google cares about that anyway[2]. Practically speaking the only Linux distros that will get an attestor that anyone will actually care about will be Chrome OS and Play-certified Android. At best, Google agrees to attest for Chrome and Firefox on non-Chrome-OS Linux and it winds up being like EME did. At worst everyone has to buy a Windows license just to use most websites anymore. >Assistive technologies will still work as the browsers implement platform's assistive APIs. At least until someone says "we need to keep content from being data mined for AI training[3]" and AI scrapers find out how to automate those APIs. The underlying power dynamic of attestation means that websites can just demand attestors ban screen readers, in the same way that ebook DRM already does. [0] Casual reminder that Louis Rossman was harassed by the GrapheneOS developer for agreeing with someone that the developer asserted had harassed them. He uninstalled GrapheneOS specifically to avoid being pwned by its developer. [1] Let me remind you of the insane cat-and-mouse game where cheaters went into the kernel, so now anticheat is in the kernel, and now cheaters find vulns in the anticheat to hide their cheats in, which now malware can use as well. [2] https://www.theregister.com/2023/06/29/google_trueview_skepticism/ https://www.theregister.com/2023/06/29/google_trueview_skept... [3] Reddit
- charcircuit 3y ago>Being able to create a new attestor means nothing because attestation is not valuable without pre-established trust. It means that each site can choose who they trust instead of their being a single entity dictating what users are secure or not. >Click fraud detection shouldn't even be something that a USER agent cares about But it is something that the web standard should think about in order to make the web a better place. >Practically speaking the only Linux distros that will get an attestor that anyone will actually care about will be Chrome OS and Play-certified Android. I disagree. There are several Linux distros that support secureboot showing that Linux distros are capable of showing they are trustworthy enough to Microsoft.
- NoGravitas 3y ago> The proposal allows anyone to become an attestor. There would not be a single attestor who you would have to prove your trustworthiness to. And websites get to choose which attestors they accept. For an attestor to do what they are expected to do, they need control of everything from the TPM up. This means there will be effectively 3 attestors - the major operating system vendors.
- danShumway 3y agoMost of this comment is misreading Mozilla's objections, but I want to specifically call this out. > Assistive technologies will still work as the browsers implement platform's assistive APIs. Assistive technologies and APIs on devices should not be beholden to the platform owners. It is a problem for disabled communities to need to ask permission to build technologies that make their lives better. Native platform accessibility APIs are important because it's important for platforms to take steps to guarantee equitable access to sites and apps on their own platforms out of the box and for ordinary users who may not want to or be able to install additional software. However, officially supported native platform accessibility APIs are NEVER an excuse to remove the autonomy and agency of disabled communities. This shows up all the time in multiple situations -- from Reddit's exemptions of nebulously defined accessibility apps from its API pricing to circumventing assistive technologies in the name of adblocking, to the current proposal. It is an attack on the autonomy and agency of vision impaired or low-mobility users to force them to use only "approved" APIs in order to build assistive technologies or to force them to ask permission before deploying their solutions. It positions the platform as a kind of benevolent dictator, giving the platform an inappropriate level of power and control over disabled communities that should be (when possible) dismantled rather than reinforced.
- charcircuit 3y ago>However, officially supported native platform accessibility APIs are NEVER an excuse to remove the autonomy and agency of disabled communities. I strongly disagree. Being disabled doesn't mean that you should be able to bypass the security of any system. Also proposals like this help reduce the amount of captchas disabled users get meaning that they may have a better experience using the web if this proposal is accepted.
- danShumway 3y ago> Being disabled doesn't mean that you should be able to bypass the security of any system Correct, but only in the sense that everyone should have the right to bypass attestation checks, not just disabled users. > proposals like this help reduce the amount of captchas disabled users get Citation needed. Chrome's implementation of this API ties directly in the Play Integrity API. I am skeptical that style of attestation will have any measurable impact on the ability to automate requests from an Android phone, and I am skeptical that websites will actually reduce captchas rather than just add attestation requirements alongside them. Even if it did reduce captchas (which to be clear, it probably won't) disability accommodation should not be conditional. Low vision and low mobility users who run custom ROMs also deserve to access the web. If the level of captchas that are thrown in front of low vision users are problematic or inaccessible, that's a conversation we need to have about captchas more generally. It's not an excuse to restrict those users' autonomy over their computers.
- account42 3y ago> Automatic testing will still work because a developer isn't going to add restrictions to their own tests from their site. Unless they are testing if a captcha gets shown from an unsafe environment. Websites aren't the only party that might want automated tests. > Archives, search engines, and spiders should already be respecting robots.txt. Site owners can already block those things if they don't want their site crawled. robots.txt is not law. Archives, search engines, and spiders SHOULD ignore it in cases where they deem it the more moral action. After all, all of these are supposed to snapshot the web that humans see.