I hereby propose a gossip dev workshop at nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l to finish the started and incomplete gossip implementation, as it is clear the 50% solution is not a solution.
https://github.com/nostrworld/nostriga/issues/32
Testing interest among the devs
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p
nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe
nostr:npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9
nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf
nostr:npub1qlk0nqupxmlyxravg0aqscxmcc4q4tq898z6x003rykwwh3npj0syvyayc
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Lmk if I missed any nostr SDK/similar devs who have interest in gossip.
To be clear: outbox is not a spec; it can’t be a spec for the same reason you can’t soec how running should work, some people want to sprint, some people have longer legs, some people have flat feet.
Beyond defining running as “moving forward” and outbox as “getting events from relays where events might be” you’d start to define things too-narrowly.
Again, that is like saying you can't spec DNS ... you can, and you absolutely should for there to be web at all... at all
nostr:note1ft96trg7twwqx89zj5nuvjy0gcpfe2q5rz5l20jww088nqarhraswc2fqy
For nostr to be usable as a constellation of apps don't we need some degree of global relay configuration?
And doesn't that require a spec for outbox/inbox?
I'd agree though that NIP-65 does over-specify this :
Clients which implement the above cannot work with proxy relays as intended, and proxy relays as intended help with performance and security considerations for inbox/outbox
