Avatar
elsat 1y ago

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.

Reply to this note

Please Login to reply.

Discussion

Avatar
Sebastix 1y ago

Yes 👌🏻👀🤓

Avatar
PABLOF7z 1y ago

What do you mean “the 50% solution”?

Avatar
elsat 1y ago

See fiatjaf and will’s evaluation of outbox implementations to date

nostr:note1cgmcrmeeeum78xavgpmtq69vlcfyres83q8lws6rrc6h8lr7shfsqxhah4

nostr:note1g4sm49t359s33qtfmh3l2rqxcnxxzh0pcen8flzaxcj3exydvj4q0t7y4c

It seems:

-there are various implementations, which don’t fulfill fiatjaf’s criteria of finding the notes on the smaller relay

-there is lack of clarity surrounding the “correct” approach to implementation (if such a thing exists)

-there is some tradeoff between performance, data query volume, and finding notes/events

So it could be that the full solution is somewhere, and there is no or difficult to find documentation, or there is a partial solution with unanswered questions such as the above.

Avatar
Colby Serpa 1y ago

What are the other forms of the outbox model beyond NIP-65 gossip & relay hints? Just want to make sure I have the full list written down.

Avatar
DanConwayDev 1y ago

Looking for notes on people's fridges

Avatar
Colby Serpa 1y ago

Keep laughing

Avatar
hodlbod 1y ago

Read and write proxies and local relays are a way of coping with some of the technical challenges. There's also kind 10050 which is a different set of relays for nip 17 DMs, and simultaneously flags support for nip 17 DMs.

Avatar
PABLOF7z 1y ago

Don’t forget about pubkey e tag hints

Avatar
hodlbod 1y ago

I knew I was forgetting something important

Avatar
fiatjaf 1y ago

There is a misunderstanding here, I wasn't talking about any "incorrect outbox implementations", I was referring to clients that don't implement outbox at all and have not even tried, so it's more like a 0% solution.

I wouldn't be so much of an asshole to complain about the few heroes who have actually implemented some kind of outbox model, even if they have problems (as every software they probably have many).

Avatar
PABLOF7z 1y ago

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.

Avatar
tf 1y ago

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