fiatjaf on Nostr: There are no NIPs that define this functionality because it kinda is Nostr itself. ...

There are no NIPs that define this functionality because it kinda is Nostr itself. Implementation details are left for the client developer.

quoting
nevent1q…67vj

nevent1q…2gnh

The "outbox model" was not a modification of the protocol nor a new invention, nor it is a new optional NIP. hodlbod (npub1jlr…ynqn) once said about the idea, "this is just the Nostr model, it is how Nostr has to work if it can ever scale" (https://t.me/gossipclient/605). Minutes after he came up with the name "outbox model" just so we could refer to this thing that Nostr clients should be doing but only Gossip was doing at the time.

The initial description of Nostr (naddr1qq…7vna) said: "you write a post, sign it with your key and send it to multiple relays (servers hosted by someone else, or yourself)" and under the "censorship-resistance" section it said "there will always be some Russian server willing to take your money in exchange for serving your posts".

Since you were supposed to write "to your own relay" or "to some Russian server" shouldn't it be reasonable to assume clients would be connecting to these relays to read your posts and the entire promise of censorship-resistance of Nostr rests on that possibility?

Implementation details were never specified because I think there are many ways to approach that and hoped clients would each have their own creative way of implementing it. Having the user manually specify a list of relays and then flood all relays in the list with queries for all people you're following was part of a very quick proof-of-concept I've implemented in (what was supposed to be the first version of) Branle in December 2022, but it should be obvious it's not a very user-friendly or scalable design, right?