Nostr Web Client

Would you like something like a zone file or something simpler

Simpler. Maybe we start with a "wss://IP" in a "connect" tag? You just need to push that replaceable event to all other relays. Then a client connecting with one of them can see the IP change and update it's records accordingly.

Reply to this note

Please Login to reply.

Discussion

Cameri🐦‍🔥 2y ago

wss requires a valid SSL certificate, doesn’t it? Would wss://IP still work?

Vitor Pamplona 2y ago

The cert must be setup for the IP, but it's possible.

jascha 2y ago

We have been discussing nostr DNS for a while. Seems coukd do own ACME (like LetsEncrypt) for SSL as well, since would also need for root domains.

someone 2y ago

what do you think about this: kind 30053 meaning nostr name system (NNS).

tags:

[['d', 'nos.lol.nns.'], ['A', '88.198.51.48'], ['AAAA','ip:v6']]

in case there are multiple servers available in different continents:

[['d', 'nostr.mom.nns.'],

['A', '5.78.89.174'],

['A', '88.198.51.252']]

Then client can do pings and connect whatever it wants.

Vitor Pamplona 2y ago

Looks good!

pebble (b/acc) 2y ago

I think it makes sense to have provisions to define relays on a private network. There should be a way for a 192.168 address, for example, to seamlessly integrate with this new header.

Vitor Pamplona 2y ago

Very interesting