Select a netmail message or compose a new one.
Nodelist · kind:10002
| Node addr | Pubkey | Relay(s) | Status | Last seen |
|---|---|---|---|---|
| No nodelist entries. Tap Refresh or Publish yours. | ||||
My relay list (NIP-65 kind:10002)
These relays are used for publishing your events and receiving mentions. read = where you read; write = where you publish.
No relay list yet.
Relay list usage
⚠ Relay lists are public metadata. Anyone can see which relays you use.
Discovered relay lists (network)
Recent kind:10002 events from the network. Tap "Add" to add their relays to your connection pool.
Tap "Discover" in the nodelist view to populate.
🔑 Keys / Identity
No key loaded.
⚠ Private key stored in localStorage. Use a burner key for testing.
📡 Connection relays
No relays configured.
🎨 Appearance
🔇 Mute list (NIP-51 kind:10000)
No muted pubkeys.
💾 Storage
ℹ️ About
FidoNetNostr demonstrates the mapping between FidoNet's store-and-forward social model and Nostr's relay-based protocol. All data is fetched live from Nostr relays.
version1.1.0
FidoNet → Nostr mapping
FidoNet's store-and-forward model is structurally identical to Nostr's relay model. This table maps every FidoNet concept to its Nostr equivalent.
| FidoNet | Nostr / NIP | Notes |
|---|---|---|
| Node | Relay (WebSocket server) | A node stores & forwards packets. A relay stores & forwards events. |
| Nodelist | kind:10002 (NIP-65 relay list) | Advertises which relays a user reads from / writes to. |
| Echomail area | NIP-29 group (h tag) / tag-based group | Public discussion area. Primary mapping: NIP-29 relay-based groups. Fallback: kind:1 with #echomail:<area> tag. |
| Echomail message | kind:9 / 11 / 1 with h or t tag | NIP-29 group messages use kind:9 (chat) or kind:11 (thread). Tag-based fallback uses kind:1 + #echomail:<area>. |
| Netmail | NIP-17 (kind:14 → 13 → 1059) | Private encrypted message. Rumor (kind:14) → Seal (kind:13) → Gift Wrap (kind:1059). |
| Netmail attachment | kind:15 (NIP-17 file message) | Encrypted file sharing inside a DM conversation. |
| Sysop | Relay admin / NIP-11 self pubkey | Operator of a node. Identified by the relay's NIP-11 self pubkey. |
| Moderator | NIP-29 role / kind:39001 | Group admin defined in the relay's group metadata. |
| Packet | Event | The atomic unit of transfer. A packet carries one message; an event carries one piece of data. |
| Binkp | NIP-77 negentropy / relay sync | Protocol for synchronising mail between nodes. Negentropy efficiently reconciles event sets. |
| AreaFix | NIP-51 lists | Subscription management. NIP-51 defines standard lists (mute, pin, bookmark, etc.). |
| FileFix | NIP-94 / Blossom (NIP-B7) | File distribution. NIP-94 defines file metadata; Blossom stores blobs by SHA-256. |
| Tearline / Origin | Relay hints / client tag | Routing metadata. Auto-appended tearline + origin in outbound messages. |
| Policy | NIP-32 labels, NIP-56 reports, NIP-51 mute lists | Moderation. Labels, reports, and mute lists form a distributed policy layer. |
| BBS "high-five" | NIP-25 reactions (kind:7) | Quick emoji reactions on echomail messages. |
| Sysop AUTH | NIP-42 AUTH | Challenge-response authentication to a relay (kind:22242). |
| "Grep" / archive | Local full-text search | Search across echomail messages and nodelist entries. |
Why FidoNet's social model was healthy
- Bounded communities. Each echomail area had a sysop and a charter. People knew the rules and the moderator.
- Cost of entry. Running a node required real effort, which filtered out drive-by abuse.
- Store-and-forward. Messages propagated slowly and deliberately, not in a global firehose. This gave conversations space to breathe.
- Local identity. Your node address (zone:net/node) was a stable, human-readable handle tied to a physical BBS.
- No algorithmic feed. You subscribed to areas you cared about. There was no engagement optimisation.
- Moderation was local. Sysops could ban users from their node; the network did not have a central authority.
Quick reference — kinds
| Kind | Purpose | NIP |
|---|---|---|
| 0 | User metadata | NIP-01 / 24 |
| 1 | Short text note | NIP-10 |
| 7 | Reaction | NIP-25 |
| 9 | Chat message (NIP-29 group) | NIP-29 / C7 |
| 11 | Thread root | NIP-7D |
| 13 | Seal | NIP-59 |
| 14 | Direct message (rumor) | NIP-17 |
| 15 | File message | NIP-17 |
| 1059 | Gift wrap | NIP-59 |
| 10000 | Mute list | NIP-51 |
| 10002 | Relay list metadata | NIP-65 |
| 1985 | Label | NIP-32 |
| 22242 | AUTH challenge | NIP-42 |
| 30002 | Relay sets | NIP-51 |
| 39000 | Group metadata | NIP-29 |
| 39001 | Group admins | NIP-29 |
| 9021 | Join request | NIP-29 |