You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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....
From #12
The text was updated successfully, but these errors were encountered: