ava on Nostr: Shame he's such a bigot. It's a good model. #cybersecgirl ...

Shame he's such a bigot. It's a good model.

#cybersecgirl

quoting nevent1q…7x9y

I'm trying to establish a better understanding of OUTBOX and INBOX model as it pertains to relays to work in improvements to the BoostZapper project for greater reach.

Good longform post by Mike Dilger for those looking for a succinct explainer
https://habla.news/a/naddr1qvzqqqr4gupzpms35h0lgrqe542lg8ly9dy0qrnp3jgjy43z4cmmds4mv7mkcnjfqqxnzde3xycngdpjxg6nqdfs3tegz3

"Later, NIP-65 made a new kind of relay list where someone could advertise to others which relays they use. The flag "write" is now called an OUTBOX, and the flag "read" is now called an INBOX."

Note that NIP-65 does not refer to this anywhere as the OUTBOX or INBOX. None of the Nostr NIPS refer to OUTBOX or INBOX apart from a reference in NIP-04 regarding users receiving messages in their inbox under another context. If OUTBOX and INBOX are intended as user interface terms, this should probably be expressed in some recommendation NIP

My plan is to follow the implementation advice given by Mike in his article. I'll just be internalizing as a read relay, or write relay.

#grownostr #nips