Immutable offline webapps
summary
Shows concrete hacks and working demos: using the cache manifest to make pages survive when the server is killed and even intentionally brick a site by setting max-age 100 years, a peer-sync chat using iframes and a shared worker called pageb that keeps working after the server dies, an offline public‑key flow called key booot that generates local keys and signs requests, and a log/replication store Fork DB that merges offline edits by linking hashes; all demos run live and actually sync.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:07How the Web Works
- 4:41Fully Brick a Server
- 9:24Doing Authentication without Servers
- 9:41Asymmetric Crypto
- 12:19Fork Db
related talks
45mOffline First (Web) Apps
30mOffline First: Making Your App Awesome When the Network Isn't
31mI'm offline, cool! What now?
38mMoving seamlessly through offline and online
29mGive Apps Online Superpowers by Optimizing them for Offline
35mOffline is the new black
52mGoing offline
56mGetting off(line): appcache, localStorage for HTML5 apps that work offline