Nostr Web Client

Damus still uses a legacy unspecified format (as do/did many clients like Amethyst) where the list of relays is set on the content field of kind 3 follow lists. You cannot specify which ones are used for reads and which ones are used for writes. It’s on my list of things to do to fix for Damus on iOS, as part of my plan to support the outbox model.

Daniel D’Aquino 7mo ago

nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf this has migrated over to NIP-65, (but without full outbox support). Some relevant new files of this migration would be `UserRelayListManager.swift` and `NIP65.swift`.

We still use the legacy format as a fallback, but give preference to NIP-65 lists.

Reply to this note

Please Login to reply.

Discussion

Terry Yiu 7mo ago

Oh, that’s news to me. Great!

Derek Ross 5mo ago

TIL that Damus is using your NIP-65 relays if you have them setup. Full outbox and inbox isn't working yet, but this is a nice start!

nostr:nevent1qqs2plsna6zqzufq9hmv7hvfqpjkaxx3y6xpug4ay0wg3sf8akkxhccpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyz9jhc9q456gqhtkv7f89s52wld7m6dde07u5jxxs8kgkcj2zgy2vqcyqqqqqqgau4ent

Vitor Pamplona 5mo ago

For the love of God, just make sure to NOT add the kind3 list directly into the NIP-65 lists. This has created so many issues for outbox systems because each relay list becomes MASSIVE.

jb55 5mo ago

i was thinking of adding a relay limit when adding relays. I've seen users add like 69 relays

Vitor Pamplona 5mo ago

I am adding the kind3 stuff into new lists which I called Proxy and Broadcasting as below. Terrible names, but it separates the information that followers need to know (which should be in NIP-65) from the relays the user wants to use for his own feeds/broadcasting. Separating the two is paramount in my mind.

https://github.com/nostr-protocol/nips/pull/1985

▓▒░[Danielsan256]░▒▓ 5mo ago

Mandatory "nice" activated 🤭