Skip to content

What are we trying to achieve with the "authentic web"? #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lrosenthol opened this issue May 15, 2025 · 1 comment
Open

What are we trying to achieve with the "authentic web"? #16

lrosenthol opened this issue May 15, 2025 · 1 comment

Comments

@lrosenthol
Copy link

From #12

What are we trying to achieve with an "authentic web"? Is it to #12 (comment) in case they want to spend the time to verify them; to increase the chance that a person who visits a web page quickly develops the same beliefs as if they'd taken the time to investigate it; to increase the fraction of pages that are "authentic"; or something else?

@lrosenthol
Copy link
Author

I would put forth that you first need to define what you mean by "authentic". As I noted in #12 (comment) - authentic doesn't necessary mean true.

The web already has a way (TLS) to establish that the content being presented was unmodified from when it was sent, and it was sent from a "verified" site. What is missing there?

I would point out that such a system only gets you the primary content - but because of linking, iframes, scripting and the like, doesn't actually "guarantee" that what the author of the page created is what the end user is seeing. (and that doesn't into account browser extensions!). Approaches like SRI (https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) tried to address some of those limitations - but never saw adoption. I note that there work on an SRI-2 that just started (https://www.w3.org/TR/sri-2/), but who knows what will happen there....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant