Makes sense to move to "DNS over Nostr", in fact I may start publishing relay IPs with kind 103 soon

Reply to this note

Please Login to reply.

Discussion

or 53. noone seems to use 53.

Let's go. If you publish it, i will use it.

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

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

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).