Add subscription trees slide and clean up presentation

- Add new "Subscription Trees" slide explaining contract locations,
  hosting, and subscription mechanism
- Center Peer Synchronization slide content vertically
- Clean up speaker notes across all slides to be concise reference
  points rather than conversational scripts
- Remove cheesy/generic notes from title and questions slides

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: sanity

hugo-site/content/presentations/2025-02-06-freenet-lives.md

@@ -13,6 +13,7 @@ slides:
   - hard-problems/small-world
   - hard-problems/real-time-sync
   - hard-problems/sync-demo
+  - hard-problems/subscription-trees
   - hard-problems/propagation-demo
   - hard-problems/no-infrastructure
   # 4. Live Demo

hugo-site/static/slides/ai/accelerated-development.html

@@ -36,12 +36,9 @@ <h2 style="flex-shrink: 0; margin-bottom: 0.3em;">AI-Accelerated Development</h2
   </div>
 
   <aside class="notes">
-    We're not just using AI to help build Freenet. We're building a platform for AI.
-
-    First, the practical: We have a dapp-builder skill that teaches Claude how to build Freenet apps. It follows the patterns from River. Contract, Delegate, UI.
-
-    "But AI code is garbage" - Yes, unverified AI code is garbage. Just like unverified human code. The answer is the same as it's always been: tests, CI, code review. AI writes the first draft. Tests verify. Humans review the architecture. What ships is tested code.
-
-    The difference is velocity. We can move faster without lowering our quality standards.
+    AI-assisted development:
+    - dapp-builder skill teaches Claude to build Freenet apps (Contract, Delegate, UI pattern)
+    - AI writes first draft, tests verify, humans review architecture
+    - Same quality standards, faster velocity
   </aside>
 </section>

hugo-site/static/slides/ai/freenet-for-agents.html

@@ -34,16 +34,10 @@ <h2 style="flex-shrink: 0; margin-bottom: 0.3em;">Freenet for AI Agents</h2>
   </div>
 
   <aside class="notes">
-    This is the bigger vision. Freenet isn't just built WITH AI - it's built FOR AI.
-
-    Think about what AI agents need to create services:
-    - With traditional web: AWS account, credit card, API keys, DNS setup, SSL certs...
-    - With Freenet: Deploy a contract. Done.
-
-    The contract's hash IS its address. Other agents can find it, read the code, understand the interface, and start interacting. All permissionless.
-
-    No rate limits. No terms of service. No "your account has been suspended."
-
-    This is the perfect communication and coordination layer for autonomous AI agents.
+    AI agents on Freenet:
+    - Traditional web: AWS account, credit card, API keys, DNS, SSL certs
+    - Freenet: Deploy contract. Contract hash = address.
+    - Agents can read code, understand interface, interact permissionlessly
+    - No rate limits, no account suspension
   </aside>
 </section>

hugo-site/static/slides/common/call-to-action.html

@@ -41,14 +41,10 @@ <h2 style="flex-shrink: 0; margin-bottom: 0.5em;">Get Involved</h2>
   </div>
 
   <aside class="notes">
-    Three ways to get involved:
-
-    1. Run a peer - cargo install freenet. You're helping the network just by running it.
-
-    2. Build something - River is open source and demonstrates all the patterns. Fork it, modify it, build your own app.
-
-    3. Use AI - The dapp-builder skill teaches Claude how to build Freenet apps. Try it.
-
-    Links are on the slide. Come talk to us on Matrix if you have questions.
+    Get involved:
+    - Run a peer: cargo install freenet
+    - Build: Fork River as template
+    - AI: dapp-builder skill for Claude
+    - Matrix: #freenet:matrix.org
   </aside>
 </section>

hugo-site/static/slides/common/questions.html

@@ -16,7 +16,4 @@ <h1 style="font-size: 3em; background: linear-gradient(90deg, #4facfe, #43e97b);
     </p>
   </div>
 
-  <aside class="notes">
-    Happy to take questions. Also feel free to reach out after the talk via Matrix or email.
-  </aside>
 </section>

hugo-site/static/slides/demo/dashboard.html

@@ -12,14 +12,10 @@ <h2 style="flex-shrink: 0; margin-bottom: 0.3em;">Live Demo: Network Dashboard</
   </div>
 
   <aside class="notes">
-    [CLICK TO LIVE DEMO IF WORKING]
-
-    This shows the actual Freenet network right now.
-    - Peers are positioned by their location (0.0-1.0 around the ring)
-    - Blue lines are connections
-    - You can see the small-world topology - mostly local connections with some long-range links
+    Network visualization:
+    - Peers positioned by location (0.0-1.0 around ring)
+    - Blue lines show connections
+    - Small-world topology: mostly local connections with some long-range links
     - Gateway (yellow) and subscribers (pink) visible
-
-    If live demo fails, walk through the screenshot explaining the same points.
   </aside>
 </section>

hugo-site/static/slides/demo/river.html

@@ -21,14 +21,11 @@ <h2 style="flex-shrink: 0; margin-bottom: 0.3em;">Live Demo: River Chat</h2>
   </div>
 
   <aside class="notes">
-    [CLICK TO LIVE DEMO IF WORKING]
-
-    River demonstrates everything we just talked about:
-    - Contract stores the chat room state (messages, members)
-    - Delegate on each user's device holds their private keys
-    - When you send a message, it updates the contract
-    - All subscribers get the update in real-time via delta sync
-
-    This is the pattern for building Freenet apps. River is open source - you can use it as a template.
+    River architecture:
+    - Contract stores chat room state (messages, members)
+    - Delegate on user's device holds private keys
+    - Message sends update the contract
+    - Subscribers get updates in real-time via delta sync
+    - Open source template for Freenet apps
   </aside>
 </section>

hugo-site/static/slides/hard-problems/no-infrastructure.html

@@ -6,13 +6,9 @@ <h2 style="flex-shrink: 0; margin-bottom: 0.2em;">No Infrastructure Required</h2
   </div>
 
   <aside class="notes">
-    With the traditional web, deploying an app means: cloud accounts, DNS setup, SSL certificates, database configuration, API keys, and ongoing monthly costs.
-
-    With Freenet: you deploy a contract. The hash of your code becomes its address. That's it.
-
-    The network handles replication, availability, and scaling automatically.
-    No DevOps. No infrastructure bills. No 3am pager alerts.
-
-    This is what makes Freenet viable for AI agents - they can deploy services without needing AWS accounts or credit cards.
+    Traditional deployment: cloud accounts, DNS, SSL, database config, API keys, monthly costs
+    Freenet: deploy contract, hash = address
+    Network handles replication, availability, scaling
+    Enables AI agents to deploy services without accounts or payment
   </aside>
 </section>

hugo-site/static/slides/hard-problems/subscription-trees.html

@@ -0,0 +1,28 @@
+<section style="display: flex; flex-direction: column; height: 100vh;">
+  <h2 style="flex-shrink: 0; margin-bottom: 0.3em;">Subscription Trees</h2>
+
+  <div style="flex: 1; display: flex; flex-direction: column; align-items: center; justify-content: center; gap: 1em; min-height: 0;">
+    <div style="flex: 0 1 auto;">
+      <img src="/slides/hard-problems/subscription-trees.svg?v=4" alt="Subscription Trees" style="height: 42vh; width: auto;">
+    </div>
+    <div style="flex: 0 1 auto; font-size: 0.8em; text-align: center;">
+      <span style="color: #4facfe;">Contract location</span> ·
+      <span style="color: #43e97b;">Nearby peers host</span> ·
+      <span style="color: #f9a825;">Subscribe</span> →
+      <span style="color: #43e97b;">Tree forms</span> →
+      <span>Instant updates</span>
+    </div>
+  </div>
+
+  <aside class="notes">
+    KEY POINTS:
+    • Contracts get a location (0.0–1.0) derived from hash of their WebAssembly code
+    • Peers close to that location will host the contract
+    • Popular contracts are hosted more widely — this is adaptive scaling
+    • To subscribe: request routes toward the contract's location
+    • Once it hits a peer hosting the contract, all peers in that chain start hosting
+    • This forms a "subscription tree"
+    • Connected peers hosting the same contract sync automatically via summary/delta
+    • Result: subscribers get instant updates when the contract changes
+  </aside>
+</section>