8 ms·

Despite all the hate against AMP, this will actually improve the state of a decentralised web. Disconnecting the web packaging feature from the application that

Despite all the hate against AMP, this will actually improve the state of a decentralised web. Disconnecting the web packaging feature from the application that birthed it, the format allows a website to sign its content and create an immutable package that any server in the world can distribute - with the signature allowing clients to trust where it came from and show the origin address instead of the cache. Isn't this exactly what the distributed web needs? This is a massive boon to IPFS (a content hash can still show the proper origin name), a big blow to censorship (a censored website could spread its content to a thousand different servers, each served over HTTPS, and viewers would still the original URL whichever cache they access), consensual permanent archiving, and much more?

ocdtrekkie 8y ago
Questions for you: - Who decides which HTTPS certs are valid? (Followup: Who decides which of those your browser considers valid?) - Who operates the browsers you'd use to view this content which sees the original URL, and have any of those companies deplatformed content on behalf of government requests? Which is to say, web packaging looks somewhat decentralized at a glance but arguably still leaves the same handful of companies entirely in charge of deciding what you view and how you view it. And it's entirely dependent on your browser's developers being ethical and trustworthy, and choices on what browser you use has just shrunk significantly in the past month alone.
- magicalist 8y ago
  > Who decides which HTTPS certs are valid? Wait wait wait, are you telling me signed exchanges maintain the status quo on a problem they aren't intended to solve?
- sudhirj 8y ago
  The packages are independently verifiable, and cacheable. Do you could start your own cache with a Raspberry Pi at home if you wanted, and if whatever browsers you trust implemented this check you’d have your own secure version of it.

ocdtrekkie 8y ago

Questions for you: - Who decides which HTTPS certs are valid? (Followup: Who decides which of those your browser considers valid?) - Who operates the browsers you'd use to view this content which sees the original URL, and have any of those companies deplatformed content on behalf of government requests? Which is to say, web packaging looks somewhat decentralized at a glance but arguably still leaves the same handful of companies entirely in charge of deciding what you view and how you view it. And it's entirely dependent on your browser's developers being ethical and trustworthy, and choices on what browser you use has just shrunk significantly in the past month alone.

magicalist 8y ago
> Who decides which HTTPS certs are valid? Wait wait wait, are you telling me signed exchanges maintain the status quo on a problem they aren't intended to solve?
sudhirj 8y ago
The packages are independently verifiable, and cacheable. Do you could start your own cache with a Raspberry Pi at home if you wanted, and if whatever browsers you trust implemented this check you’d have your own secure version of it.