How do we establish who owns a name in this DNS over Nostr? I guess you need to explicitly Trust whoever publishes the event.

Reply to this note

Please Login to reply.

Discussion

There will be no names anymore. Code will import another event id directly.

good question! and the security of the publishing keys is becoming more important too

No names anymore. What does that mean, please, nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ?

Instead of including a domain+file name,

We would do this:

This syntax is ugly, better nostr://event/id (it's time to standardize this, isn't?)

What’s the // for? What would you be building with this?

Is used to standardize the access of web resources (aka URL). Imagine open any web browser and type "nostr://event/id" and suddenly see your requested data.

Well we can’t just copy stuff cause it looks pretty. RFC 3986 specifies that the double slash precedes the authority part of a URI ( user info @ domain : port ).

"userinfo@" is optional (but we can find out how this can be used by Nostr urls).

Owner of the domain can add a TXT record in the regular DNS records. Put his npub in there. Or the hex of it.

But I thought that’s what we are trying to get away from. Any dependency on the existing DNS infrastructure defeats the purpose.