|
| 1 | +# Relay peering launch film — scene copy |
| 2 | + |
| 3 | +Source: [nostream#942](https://github.com/cameri/nostream/issues/942). Composition: `src/peering-film.ts`. |
| 4 | +40 s · 1920×1080 · 30 fps · 1200 frames. One job per scene; jobs-to-be-done only (no protocol tutorial). |
| 5 | + |
| 6 | +**Approval:** Draft for maintainer review before the peering release ships on the site. |
| 7 | + |
| 8 | +## Factual guardrails (#931, #932–#940) |
| 9 | + |
| 10 | +| Claim on screen | Spec / issue | |
| 11 | +|---|---| |
| 12 | +| **Flat or traffic-based** fees for a **period** the operator sets | #931 paid peering terms (`amount`, `unit`, `period` in NIP-11) | |
| 13 | +| **Never per event** | #931 out of scope: no per-event payments | |
| 14 | +| **Lightning**, **sats**, **between relays** | #931 / #937 settlement between peer relays | |
| 15 | +| **Cache window** operator-configured; “the last hour” is an **example** | #931 cache peers + rolling-window scope in NIP-11 | |
| 16 | +| **Ask an archive** outside the window | #931 cache miss must not imply “event does not exist” | |
| 17 | +| **Sell feeds** to other relays | #931 archive/backbone peers; paid terms | |
| 18 | +| No operator names, adoption stats, or network metrics | #942 production notes | |
| 19 | + |
| 20 | +--- |
| 21 | + |
| 22 | +## Scene 1 · PEOPLE (frames 0–240) |
| 23 | + |
| 24 | +**Beat:** Run a relay for your people, not the whole network. |
| 25 | + |
| 26 | +| Element | Copy | |
| 27 | +|---|---| |
| 28 | +| Kicker | `01 — YOUR PEOPLE` | |
| 29 | +| Headline | Run a relay for your people. | |
| 30 | +| Accent | Not the whole network. | |
| 31 | +| Card 1 | **SCOPE** · Your people · the people you follow | |
| 32 | +| Card 2 | **PEERING** · Their relays · the ones your people use | |
| 33 | +| Card 3 | **FETCHES** · The rest · on demand | |
| 34 | +| Payoff | Feel complete without ingesting everything. | |
| 35 | + |
| 36 | +**Issue gloss:** Community relay peers for its scope and fetches the rest on demand. |
| 37 | + |
| 38 | +--- |
| 39 | + |
| 40 | +## Scene 2 · WORTH (frames 240–520) |
| 41 | + |
| 42 | +**Beat:** Your archive is worth something now. |
| 43 | + |
| 44 | +| Element | Copy | |
| 45 | +|---|---| |
| 46 | +| Kicker | `02 — YOUR ARCHIVE` | |
| 47 | +| Headline | Your archive / is worth something now. | |
| 48 | +| Sub | Sell feeds to other relays — settled in sats. | |
| 49 | +| Panel | PEERING TERMS · **PER PERIOD** chip | |
| 50 | +| Terms | fee: flat or traffic-based — you set the terms · period: you set the length · settlement: Lightning, in sats, between relays · per event: **never** | |
| 51 | +| Payoff | A product, not a cost center. | |
| 52 | + |
| 53 | +**Issue gloss:** Deep history can be sold to other relays; completeness becomes a product. |
| 54 | + |
| 55 | +--- |
| 56 | + |
| 57 | +## Scene 3 · FAST (frames 520–760) |
| 58 | + |
| 59 | +**Beat:** Fast, everywhere. |
| 60 | + |
| 61 | +| Element | Copy | |
| 62 | +|---|---| |
| 63 | +| Kicker | `03 — HOT FEED` | |
| 64 | +| Headline | Fast, everywhere. | |
| 65 | +| Sub | The hot feed, near the readers. | |
| 66 | +| Track | OLDER THAN THE WINDOW · THE HOT FEED | |
| 67 | +| Note A | BEFORE THIS CUT · Ask an archive. · outside the window | |
| 68 | +| Note B | CACHE PEERS · A rolling window · the last hour, or whatever you configure | |
| 69 | +| Payoff | Small relays feel instant — without owning the firehose. | |
| 70 | + |
| 71 | +**Issue gloss:** Cache peers holding only the last hour put hot feed near readers. |
| 72 | + |
| 73 | +--- |
| 74 | + |
| 75 | +## Scene 4 · MIDDLE (frames 760–980) |
| 76 | + |
| 77 | +**Beat:** Relays that only talk to relays. |
| 78 | + |
| 79 | +| Element | Copy | |
| 80 | +|---|---| |
| 81 | +| Kicker | `04 — THE MIDDLE` | |
| 82 | +| Headline | Relays that only talk to relays. | |
| 83 | +| Accent | The network can grow a middle. | |
| 84 | +| Archive | Deep history · backbone infrastructure | |
| 85 | +| Cache | Rolling window · hot feed near readers | |
| 86 | +| Edge | **EDGE** · Readers connect · the relay readers connect to | |
| 87 | +| Payoff | Infrastructure behind. Users in front. | |
| 88 | + |
| 89 | +**Issue gloss:** Archives and caches as infrastructure; edge relays facing readers. |
| 90 | + |
| 91 | +--- |
| 92 | + |
| 93 | +## Scene 5 · CLOSE (frames 980–1200) |
| 94 | + |
| 95 | +**Beat:** Inversion — one thing well; the network assembles the rest. |
| 96 | + |
| 97 | +| Element | Copy | |
| 98 | +|---|---| |
| 99 | +| Contrast | Today, every relay tries to be everything. | |
| 100 | +| Headline | Each relay gets to be one thing well. | |
| 101 | +| Accent | The network assembles the rest. | |
| 102 | +| Lockup | [nostream mark] nostream relay peering | |
| 103 | + |
| 104 | +--- |
| 105 | + |
| 106 | +## Site |
| 107 | + |
| 108 | +After render: `pnpm run media` in `website/site` → `public/media/peering.mp4`, `peering-poster.webp`. |
| 109 | +Home section: `#peering` (`Peering.astro`). |
0 commit comments