Decentralized React states - using IPFS to sync, store, and recover state
summary
Claims that React apps can be offline‑first and peer‑to‑peer by using IPFS + libp2p + IPLD to content‑address assets and exchange encrypted updates, and demonstrates a working stack: React/React Native clients, interplanetary event logs feeding CRDT‑style sync, and threads (mutable DBs over IPFS) for multi‑user state. Examples include a peer‑to‑peer werewolf game, a notes app that syncs without central servers, and hosting Wikipedia mirrors to resist IP address censorship; demos show real synchronization and local recovery across devices.
AI-written summary · about
chapters (42)
- 0:00Intro
- 0:40About Textile
- 0:52About React
- 1:27Simple apps
- 1:39Werewolf
- 2:31Building a simple app
- 3:00Problems with building apps today
- 3:35Building peertopeer apps
- 3:56Good news feed
- 5:26Health care apps
- 7:25Infrastructure
- 7:57We are all in the same room
- 8:28The virtuous cycle
- 9:19Lets talk about IPFS
- 9:53What is IPFS
- 11:20All data can be interlinked
- 12:06Distributed hash tables
- 12:55IPFS
- 14:04Location Based Addressing
- 14:59IP Addresses
- 16:50Contentbased IP Addresses
- 18:49Cloud Flair
- 19:09Wikipedia
- 20:29Selfassembly networks
- 20:49Link data
- 21:00Nested data
- 21:29Algorithm
- 22:13IPFS with React
- 22:42Using IPFS with React
- 24:09Hosting entire applications on IPFS
- 24:24Gateways
- 24:59Dynamic Data
- 25:26interplanetary event logs
- 26:02encryption
- 26:31Threads
- 27:19CRDTs
- 28:06Online
- 28:38Database
- 28:55Thread
- 29:32GitHub repo
- 29:48Challenges with IPFS
- 30:31Thank you
