Thread

The only permissioned part still existing within this system would be IP addresses themselves. But apart from that you can totally do it

The question indeed makes very little sense, but the the problem becomes how on earth i am going to explain that to you. So lets say we have trains, and trains are cool for all kinds of reasons, but they are permissioned/centralized. So someone comes up with the idea of the car so its not permissioned/centralized. And your question would be: I see your vehicle requires users to steer and navigate themselves, so can't you put the car on rails? I.e. nip-05 is DNS, you suggest to use DNS to solve the drawback of the DNS-less system. Hope this helps.

See, I had no idea how nip-05 worked. This answer was great, thank you!

Good comparison indeed. Getting human-readable domains like you're suggesting is not the goal of this project. Something like that could live on top of this solution though.

5 hours really

Correct. In the current state of the code automatically inserting the certificate is still VERY risky because I haven't implemented certificate security checks yet. If the checks are not in place. any [npub].nostr could publish a self-signed certificate with *.google.com and your system would trust it. Allowing a MITM attack. Just be aware of this when testing. It's very experimental.

Probably, since you'll check on your machine the signature of the npub you wanna reach. It doesn't matter HOW the info got to you anymore. Which is why the internet is so broken, all these kind of exploits exist by the grace of 'trust me bro' networking.

Great video btw, thanks for sharing!

I'm not so sure. Dan Kaminsky only stop gapped the problem, didn't resolve it. If you're still running DNS, are you sure ? is still in my head :p challenge the folks at sov eng for me, cuz i can't be there will ya?

a Domain name without ICANN-DNS is way more valuable then sending sats around

This still needs updating though, the latest version is in the no-dns repo

hm nodns needs to sit on top of an conventional Resolver like Bind and handover nameresolution when it can't . a more human readable version for a Nostr domain would be handy

This solution can't solve the human readable part. It chooses security and decentralization over human-readable. I believe the human readable names to be a social problem to solve. They could perfectly well resolve to an npub's no-dns records. Meaning bob.nostr might resolve to one npub for me and a different one for you based on our differing social graph.

hm that doesn't work , the name must be worldwide unique like a npub

I disagree For uniqueness you either need to agree on a centralized authority like ICANN. OR Achieve global consensus by adding it to the Bitcoin blockchain. But to me, that seems expensive and unattainable for most people in the future. I don't like either of the former solutions. I think accepting that no globally unique owner of [short name].nostr and building for that is more realistic. You can give a name weight by putting PoW towards it or by social consensus, which is how the world has operated since forever and it works quite wel... If I say 'London', you probably know what I'm talking about and which coordinates it belongs to, despite there being multiple London's out there