Upgrading the Web
summary
Proposal upgrades the web by adding a transitional helper app that runs object-capability vats and uses secure JSON over TCP instead of HTTP/SSL, identifying endpoints by elliptic curve P-521 public keys and using AES-256 and SHA-3 for links. The plan targets eliminating passwords, containing third‑party code, and letting banks adopt it first; a Node‑based message server plus a GPU‑accelerated cute UI implement the idea. No demo code exists yet; work is ongoing.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:28Apology
- 1:36Security
- 10:00DNS
- 11:56Certificate Authorities
- 17:25Document Object Model
- 21:36Many Have Tried • Microsoft, Apple, Adobe, Oracle, many more. • In most cases, the technology was much better. In most cases, the solution was not open. • There was no transition.
- 23:56Upgrade the Web Keep the things it does well.
- 24:32HDTV
- 27:58Helper App
- 31:51Risk mitigation will compel the other secure sites.
- 37:24ECC521 public keys as unique identifiers
- 43:51Trust Management Petnames
- 45:29Cooperation under mutual suspicion.
- 45:57JavaScript Message Server
- 48:27The Old Web: Promiscuity The New Web: Commitment
- 50:06There's nothing new here.
- 50:37In the meantime, keep doing what you're doing.
related talks
37mUpgrading the Web (Keynote)
45mThe Seif Project
09mThe Seif Project
05mThe Paradigm Shift to Verifiable Computing and Self Sovereign ID
35mThe Web Capabilities Project – Better, Smoother, Sexier
21mRethinking Web UX with Webauthn and Project Fugu
38mUnlocking New Capabilities for the Web
22mThe (Abundant) State of the Web