How could nostr use #pubky decentralized DNS?

Easy. Instread of connecting to the relay URL which is governed by DNS.

You can connect directly to the relay pubkey. If for some reason the relay DNS is taken down. It can move to another site, or a hidden service. Users are automatically updated.

To prevent this you would have to take down 20 million nodes all over the world (much harder than silencing a relay). And even then, 100s can pop up in minutes, using existing software installed on 100+ million computers.

That's just one use case. #pubky has 100s.

Reply to this note

Please Login to reply.

Discussion

Pubky docs?

I truly Google pubky and get nothing

I'm confused and worried. Should I be deleting nostr and using pubky?

The app is not publicly released yet so you have some time to say your goodbyes ;)

I wonder why they did not build on Nostr keys and events. Anyway, the pubkey-dns resolver is super cool! It should be complemented with a browser extension for looking up public keys in your social graph.

Pubky coupled with something like NIP41 [1] would be a formidable stack. NIP41 allows for key rotation.

1. https://github.com/nostr-protocol/nips/pull/829

I believe #pubky are working on rotation as a first-class use case. Some good bits and some bad bits in NIP-41. I favour #subkeys right now. Let's see how it develops, though.

Agreed subkeys are another good solution.