Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Request for Mozilla Position on an Emerging Web Specification Specification Title: Web Environment Integrity API Specification or proposal URL (if available): https://rupertbenwiser.github.io/Web-E...
But how can it trust you’re a person when it just confirms that you’re running an in-modified site. It takes a hash of the site, then make sure your local view of the website matches that hash.
This disables add blockers, custom css, etc; but I don’t see how this standard would prevent bots…
It’s not just checking that you’re running in an un-modified OS, that’s just one part of it.
It doesn’t disable ad-blockers or custom css btw. And anyway, websites can already detect when you’re using an ad-blocker and not show you their content. This isn’t needed for that.
The only real benefit to users that I can think of is that it could eliminate the need for captchas.
It really wouldn’t
If the point is so websites can trust that you’re a person then the captchas aren’t needed.
I don’t even trust that I’m a person sometimes.
But how can it trust you’re a person when it just confirms that you’re running an in-modified site. It takes a hash of the site, then make sure your local view of the website matches that hash.
This disables add blockers, custom css, etc; but I don’t see how this standard would prevent bots…
It’s not just checking that you’re running in an un-modified OS, that’s just one part of it.
It doesn’t disable ad-blockers or custom css btw. And anyway, websites can already detect when you’re using an ad-blocker and not show you their content. This isn’t needed for that.