Funny... I speak... I was thinking of nfbd and why land & wine made there own it seems. also what the hell is fi-transitory-01? Why is strfry the stand? or is it really? because I think the creator of nostr is @fiatjaf, although I can be wrong. there's always a story. Anyway, why aren't you talking about using the pyramid with fiatjaf? is that the pyramid? using only three relays like Nostur wants u to use? Why does @jb55 not subscribe to the theme of what u write to you don't read to and what you read to you don't write too. Like why??? in terminal what u write to u can surely read. so why and not read and write to the same relay. I can go on>>> stilll learning πŸ‘€

Replies (1)

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.
↑