A P2P Calendar
summary
Shows a working P2P calendar built on an append-only hyperlog with LevelDB, hyperlog-index and hyper-kv, plus parse-messy-time for recurring rules and a norcal CLI; claims avoid uploading personal data, notes a real-world pain point (Google Calendar: ~100 bytes of event data required ~3.5 MB to load; observed 31s satellite ping). Replication runs over stdin/stdout (demo uses dupsh) and successfully syncs events; privacy uses encrypted per-field capability keys so selective sharing and revocation are possible.
AI-written summary · about
chapters (21)
- 0:00Introduction to P2P calendar
- 1:07Problems with centralized calendars
- 3:33Peer-to-peer fundamentals
- 6:03Kappa architecture explained
- 8:10Hyper logs and data structures
- 10:39Materialized views with Hyper log Index
- 12:25Key-value store with multivalue registers
- 14:31Building the calendar database
- 15:16Time parsing challenges
- 17:23Calendar DB and queries
- 18:09Text-based calendar interface
- 19:11Combining text layers
- 19:32Demo of NorCal calendar
- 20:36Adding sync feature
- 21:18Peer-to-peer replication
- 23:25Privacy and granular sharing
- 24:49Capability systems with crypto
- 26:38Encryption for granular access
- 28:03Implementing capability system
- 30:11Revoking and re-encrypting access
- 31:35Q&A and summary
