That sounds very inderesting

Kind of why I'm pushing for Nomen, but people generally shoot it down for (gist quotes) "it's hard / we can make people move to this" or nostr peeps "it isn't scalable"

Habla

The ICANN Problem, Solved with Bitcoin and Nostr via Nomen - Freakoverse

Can the ICANN Problem (along with NIP-05) be solved by utilizing Bitcoin and Nostr with Nomen?

💯

Brainstorming! Objectives: Reduce dependency on traditional domains across my Nostr web app. Why: Traditional domains are centralized and controlled by governments. Not ideal for freedom tools/apps. Idea: Create a lightweight static website called "NostrHub," which will serve as a quick-access hub to all my other Nostr web apps. Plan: 1. First Step: Host the lightweight NostrHub website on Nostr relays and IPFS, making it accessible through TOR, IPFS gateways, Freenet, and other decentralized storage or P2P access options. 2. Second Step (my favorite, though a bit unorthodox): Convert the NostrHub website/code into an offline bundle that can be shared as a zip file. When unzipped and clicked, this bundle will open the NostrHub page in your browser, running locally without relying on domains or web hosting—essentially self-hosted. The offline website bundle also addresses a more fundamental issue with the web ecosystem. Unlike traditional websites, offline bundled sites can’t be unilaterally changed or modified by the developer, making them trustless and truly giving users full control over the website, its code, and any updates. This approach will eliminate the single point of failure posed by centralized domains, make all apps easily accessible, and provide users with a more private way to access them. This is a rough outline. Suggestions for improvements are welcome!

Love nomen but unfortunately I dont think it is still developed.

I believe #pubky is the first solution that will work here

This is exactly what I was looking for, thanks

Seems like pkdns relies on mainline DHT for censorship resistance. What are the censorship resistant properties of mainline DHT? It also requires users to use a particular DNS resolver, so it won't serve my website to 99% of internet users who don't know how / will never change their DNS resolvers. But we gotta start somewhere, and I'm not sure any other solution is any better place to start. Maybe if this or another decentralized system takes off, major DNS servers will start to support it and it'll become more usable. It bothers me that we have this beautifully censorship resistant thing, the bitcoin blockchain, and we still haven't figured out how to leverage that to get us out of the quagmire of centralized power that is ICANN/DNS. I know about nomen but it suffers from the same usability / specialized DNS resolver issue, among potentially other issues. Is there any way to bridge the gap so that the existing system of DNS resolvers will work on whatever the new namespace is? Until owen.bitcoin resolves automatically on my grandma's PC, without any special configuration, I think we're gonna keep failing to take off. If we can solve that, there are probably a half dozen decent decentralized solutions to do the rest.

That's an interesting one. Will research it. Will see if I can hopefully bring development of Nomen back to life. Issue was no client gave it a chance for some reason (perhaps I'll figure out why if I do, but will attempt at least). With that said, would be neat if both of these solutions combine somehow

Main issue was that fiatjaf and semisol were against it. So it had no real chance. For a project to be successful you need everything to go right. And with powerful people against you, it is likely to not a productive use of time. To bring it back you would need to write and put online the indexer. However the schema that is used to create the rules needs to be managed responsibility by someone who has the time. That's another challenge. What's good about #pubky is that its already a working system with millions of nodes. So hard for it to fail. There would need to be a tie-breaker system that ties names to pubkeys. There's emerged new ecosystems for that now, namely runes, or my soft-fork #glyphs. For me it just needs to be fair.

Ya that's what I noticed too. When I mentioned I'd see if I can bring it back to life is by implementing it, to be the first nostr client to implement seriously, hit up the creator to soft get back into it as a result and help a bit with financial burned as well as help with designs, and depending on the success of my client it would bring attention to Nomen in the scene (both positive and negative since it got shot down), then hopefully we'd see if it'd properly live or not. How I see Nomen is just that, a simple name indexer with an end user cost of cheap to expensive depending on traffic, and I wouldn't want control of who takes names and wouldn't want expirations on names either (if someone took google, and the actual company wants the name but aren't successful in buying it off the person, then their name would be google:1 or google:2, depending on when they got the name). Of course it'd also be used as a handle for nostr users. In regards to how people would check for names, well, a lot of people are already running Bitcoin full nodes, so a one time scan then keeping it running along with the node would be it. Sites/apps would link to such scanners to fetch names and that's it. One question I had in mind though, regarding pubky, is why another keypairs? Couldn't it be built on top of nostr and use it's keys?

One thing that will always be needed is pubkey.nostr as a domain. Because only one privkey controls, or can control, that record then getting a DNS doesnt matter too much where you get it from. Pubky are making proper eco system for this including 10 million Mainline nodes, so it truly is censorship resistant, rather than the small nostr public relay network. See also

dnstr.org

NIP-134

dnstr.org website

Main problem is that it's hard to get anything at all through nostr right now. So it's a dead end for most innovation. Attaching names to a pubkey is a two step process because more than one one pubky can claim a short name, you need a tie-breaker. But it's no good some small tie-breaker system that no one has heard of. For it to be fair it has to be well publicized and a level playing field, with some cost to getting names. Running a node and an indexer is one step (tho no one has done that right now) plus getting a good domain, then you have to publicize it, and then you need to ensure the rules are fair and stable. It becomes such a huge task, and with people against it, very little chance of success. As other solutions have emerged from other eco systems, it seems the path of least resistance to use them rather than to do it all yourself in an adversarial env.