nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c can probably describe better, but I think by Gossip Model we generally mean that the app figures out where to get posts based on the author's write relay list. The amount of connected relays changes significantly over time. That initial description could be expanded to using any relays that are declared in the event kind you are looking for. Public Chats, for instance, should be based on the preferred relay of the channel metadata + relays from your follow lists (so you never miss a follow's chat post even if it's not in the main relay of the channel).

Reply to this note

Please Login to reply.

Discussion

Right, but aren’t there like 3 kinds that can store relay information associated with an npub? Or do you specifically mean the version of relay lists that allows read/write specification?

Ahhh is it nip-65? I think this may be different than the relay lists I am familiar with.

https://github.com/nostr-protocol/nips/commits/master/65.md

You can use both. No need to be shy :)

I guess I need to catch up on nips!

#[1]

πŸ”₯ Shiba Airdrop Round 2 Is Live.

πŸ‘‰ https://telegra.ph/Shiba-Airdrop-Round-2-Is-Live-06-16 Claim your free $SHIB.

#[1]

πŸ”₯ LayerZero ($ZRO) Token Airdrop, Earn $30,000 For Free.

πŸ‘‰ https://telegra.ph/LayerZero-ZRO-Token-Airdrop-06-16 Claim your free $ZRO.

πŸŽ‰ Improve Eligibility for Potential LayerZero Airdrop.