this post was submitted on 24 Jul 2023
198 points (97.1% liked)
Explain Like I'm Five
13896 readers
17 users here now
Simplifying Complexity, One Answer at a Time!
Rules
- Be respectful and inclusive.
- No harassment, hate speech, or trolling.
- Engage in constructive discussions.
- Share relevant content.
- Follow guidelines and moderators' instructions.
- Use appropriate language and tone.
- Report violations.
- Foster a continuous learning environment.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So the person you cross posted this from does not seem to have read this.
This is not impactful of extensions or different browsers. The main point of this actually seems to be replacing captcha.
The dumbed down version is, attestation of the software stack such that it is reasonable to assume a human is actually using it and not an automated process.
Quite frankly, as a web dev I can already prevent certain browsers from accessing my webpage by trying to access unique functions of a browser as a condition of loading the rest of the content.
So what the other user is concerned about already exists, in fact Google meet already does this to prevent Firefox users from accessing certain features, changing user agent doesn't change the outcome of whether or not the features are available. (In this case it's because Firefox will crash, but most of the time this is done is for bad reasons).
Edit: this is the most reasonable criticism https://github.com/RupertBenWiser/Web-Environment-Integrity/issues/44
I do agree with it completely (that the proposal can't actually work)