nostr:nevent1qqsz3yed3r5l5szxu5lazhmp2n4skac40xd2m02nuwmjl5yry75gcqqpzpmhxue69uhkztnwdaejumr0dshsz9mhwden5te0vf5hgcm0d9hx2u3wwdhkx6tpdshsz8thwden5te0vfhhxarj9e3xjarrda5kuarcda4k7tnrdakj7pm2gnh

The "outbox model" was not a modification of the protocol nor a new invention, nor it is a new optional NIP. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn 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 (nostr:naddr1qqzkummnw3eqzythwden5te0ve5kzar2v9nzucm0d5pzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqvzqqqr4gusz7vna) 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?

Reply to this note

Please Login to reply.

Discussion

I find this a strange argument. It sounds like you are saying the most sane effective way to comply with the protocol *yet discovered*, was not an invention, it was “always in the protocol” because it had to be in the protocol for things to work. While also admitting it was never described anywhere precisely enough until a client dev used their creativity to solve a problem you hoped they would solve with creativity.

And also it sounds like you are annoyed other client devs are dragging their feet at implementing the same solution to the problem that you hoped client devs would solve in a number of different creative ways? Do I have it right? 😀

🤦‍♂️

You get it right that I was mostly wrong in my expectations as most clients didn't really implement the protocol in a way that was true to its principles. Some clients have implemented it nicely though (Coracle, Gossip, Snort, Highlighter, Voyage) and some other clients seem to be working on it.

Do personal proxy relays that connect to many other relays (and your clients connect to this _one_ relay if yours) help here?