Our great sponsors
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
ens
Discontinued Implementations for ENS core functionality: The registry, registrars, and public resolvers.
-
> - The plan appears that user names are delegated to the centralized DNS system (https://github.com/nostr-protocol/nips/blob/master/05.md)
DNS is not centralized, it is distributed. A name server can delegate authority to other servers. Every nation has their own, which I consider sufficient decentralization. (Although it does rely on IANA to list addresses of root name servers, which is perhaps the centralization you refer to)
Do you propose another naming system?
For this to happen clients will have to build this into the UI. I’ve got a work in progress concept for one client [0]. Basically let a user create arbitrary relay groups. When posting the user can choose which groups to post to. Users can then filter their feeds to specific relay groups.
[0] https://github.com/monlovesmango/astral/pull/93
One of the first applications of blockchains was DNS. (Namecoin) ENS is a modern form. (https://ens.domains)
I would say there's still some degree of centrality for ENS, but it is more decentralized than DNS.
These services exist outside of the protocol and depend on a few centralized and trusted authorities.
Another solution that is arguably more resistant to capture and censorship would be to use a blockchain to manage user name aliases - like Farcaster is doing with fnames.[1]
[1] https://github.com/farcasterxyz/protocol#22-farcaster-names