gm, thinking of ways a client can bootstrap a list of relays and test that they're minimally trustworthy in some way. maybe we end up defaulting to nip-05 relay recommendations - if that happens, would providers injecting their own relays into a user's records be helpful or viewed as an attack vector?

maybe a canary bot that tries to send restricted samizdata - 3D PDW files, politcally sensitive speech, financial transactions to blacklisted addresses - through a list of relays and testing end-to-end delivery would be useful?

Reply to this note

Please Login to reply.

Discussion

NIP-65 > NIP-05 relays publishing.

Because with NIP-05 you trust the domain/web operator to set the relays, as you already stated.

awesome, thanks for the pointer, didn't know that nip existed!

A pleasure!

🫂

Why not use kind 3 for relays?

Kind-3 is supposed to be used just for the Contact List:

https://github.com/nostr-protocol/nips/blob/master/02.md

Although it's used also for Relay List by some clients right now.

That it's causing some problems with relays or contacts 'disappearing' when a user change between clients, as some are publishing the kind-3 'too soon'.

See:

nostr:note10ttnuuvcs29y3k23gwrcurw2ksvgd7c2rrqlfx7urmt5m963vhss8nja90