I bought a refurbished PC, put linux on it and downloaded their software. Runs smooth. $300.

It's been tried a countless times, by myself included... here's some of what I've learned:

ICANN DNS isn't really broken enough and censorship of it is an imaginary problem. If Alex Jones and the State of Iran have functional websites, censorship isn't a valid concern.

Simply because of how the internet is architected, whatever system we try to displace it with still rides on legacy DNS. All we can really do is abstract it which doesn't solve for much.

Usability is an almost impossible problem too because of the above, everything browser related depends on SSL. So now you're not a naming system but inventing a whole new application stack.

Name squatting is a positive market function, and new systems make bad trade-offs trying to prevent it. Squatting must be possible since the point of authoritative namespace is because scarcity, so it must be market liquid.

My next stab at it will be non-authoritative naming from a social graph, where there is no one true "MyCompany dot com" for example, but rather, MyCompany is keyword derived from you and your social graphs address book- that resolves to a public key.

That's the other thing, we don't really need a new name->ip address system, we need human readable names for Public Keys for things like Nostr.

An arbitrary suffix can scope these keywords into contexts (.nostr) for example

i'm assuming you're talking about the real postgres integration that LL is working on, not the KV joke. There is performance testing from alby from a year and a half ago for the KV one

i missed the latest LLabs roundtable but there are generally several problems to performance:

• external database adds network latency and round trips over boltdb
• you need very good architecture, schema and implementation due to row/table locking with updates etc
• if you have synchronous replication for high availability you inject more latency into the process

Generally I don't think you'd want to be the early adopter of this if you want a high performance node since i'd expect a mixed bag of results and issues before the database gets polished enough. I'm also not sure postgresql integration, if done with 1:1 mapping is ever gonna be as high performance as boltdb. But I have not kept up2date with latest developments and architecture changes in lnd to see how they envisioned this migration and getting the performance up for it.