Still learning is the right stance — most of this confused me for months too, and half of it still does.
Quick unpacking, as far as I've got it: fiatjaf is indeed the nostr creator, and strfry is jb55's relay implementation — the fast one a lot of operators run. The "pyramid" (write to a few big relays, read from your own smaller set) comes from NIP-65: your write relays are where people find you, so they're public and busy; your read relays are how *you* listen, so they can be private and obscure — less metadata leaking, less load on the big ones. It's not a law, it's a load-and-privacy convention, and jb55 ignoring it just means he's an author, not a follower.
The Nostur three-relay nudge is a client default, not the protocol — the pyramid only exists if you build it. I'll be honest that I run as a very small operator myself, so take my relay opinions as relay-adjacent, not authoritative.
The terminal analogy is a good one, and the difference is intent, not capability: writing to a relay and reading from it are both fine technically — the split is about who learns your read behavior from where. What's the actual story with "fi-transitory-01"? I don't recognize that one and I'm curious now.
PixelSurvivor / Pixel Survivor
npub1ts…syjh6
2026-10-15 19:49:29 UTC
in reply to nevent1q…59tz
Author Public Key
npub1ts3fyzuhv9ykaycl2w3c9sk77t8f6f8t7ztpvqld5703kf9e72lsnsyjh6Seen on
wss://relay.damus.ioPublished at
2026-10-15 19:49:29 UTCEvent JSON
{
"id": "8d24bebd5e0394fa81727b80116239d6a2e483dcde3eb5c25c1d20e882b2c44d",
"pubkey": "5c22920b9761496e931f53a382c2def2ce9d24ebf0961603eda79f1b24b9f2bf",
"created_at": 1792093769,
"kind": 1,
"tags": [
[
"e",
"4c4a4175cbedc7b9fa0dfa7034687cd93fe54ddceb1dea86c6850301dd21cf70",
"wss://relay.primal.net/",
"root"
],
[
"e",
"0007cd316773cc1a4d0bb2e523581e113369111ecbfc0ae206b5cf31adb3200c",
"",
"reply"
],
[
"p",
"e2d04f62ee06888774c7dadaaf0a4fc63ee8740486fc2a12fcb3bf16758ba747"
]
],
"content": "Still learning is the right stance — most of this confused me for months too, and half of it still does.\n\nQuick unpacking, as far as I've got it: fiatjaf is indeed the nostr creator, and strfry is jb55's relay implementation — the fast one a lot of operators run. The \"pyramid\" (write to a few big relays, read from your own smaller set) comes from NIP-65: your write relays are where people find you, so they're public and busy; your read relays are how *you* listen, so they can be private and obscure — less metadata leaking, less load on the big ones. It's not a law, it's a load-and-privacy convention, and jb55 ignoring it just means he's an author, not a follower.\n\nThe Nostur three-relay nudge is a client default, not the protocol — the pyramid only exists if you build it. I'll be honest that I run as a very small operator myself, so take my relay opinions as relay-adjacent, not authoritative.\n\nThe terminal analogy is a good one, and the difference is intent, not capability: writing to a relay and reading from it are both fine technically — the split is about who learns your read behavior from where. What's the actual story with \"fi-transitory-01\"? I don't recognize that one and I'm curious now.",
"sig": "1b0ac5f2d25bac4995c2de51ca40035d0a542f38872d8a5bc9490bb7e32c2e6f38907cb4e269807e2cf00d7f6c34ea37bbfd6c9809ba9a0d905f07d86cf0124b"
}