Oddbean new post about login | logout A better question is to ask yourself what nostr solves. Nostr sends notes, and other stuff, from one user to another, using relays (web servers) in realtime. This is better than the status quo, because if one relay goes down, you can use another, and you (hopefully) have not lost everything. #pubky is provably censorship-resistant DNS. It has millions of nodes, and 15 years of track record, most famously via Bittorrent mainline. Censorship resistant DNS is a big idea because it allows anyone to express themselves. To stop it you would have to take down 20 million nodes (as opposed to 2-3 relays) and then 100s more would spring up. Each project does different things. Nostr improves on the status quo by relaying notes. Let nostr be nostr. #pubky solves a big idea which is to decentralize DNS, which has become the acchiles heel of the web. It also gives access to dozens of massive nettworks (e.g. git) many bigger than nostr already. Since they both use the same private key users can have one or both if they choose. There is a powerful intersection that some of us are now exploring. My mind is blown with the possibilities.
I'm definitely going to study it. Quite interesting...
Do! It repays the effort.
We spoke about this ☝️ @avgsolipsist https://pubky.org/
Very keen to check out #pubky this weekend.. I've no idea 20 million nodes were actually floating around! Are they in direct oposition to ICANN and are they part of OpenNIC? I know someone approached a group of nostriches recently about securing and using the .nostr tld potentially with opennic. I've felt for a while that DNS servers maybe tied to nostr relays could be a foothold into a more decentralized and freedom of speech. I really like the idea of #pubky using the same private key!
There aren't millions of pubky nodes, pubky has no concept of nodes. Pubky uses pkarr.org, which is just a spec for using Mainline (Bittorrent) DHT and especially BEP0044 to publish DNS packets. According to Pkarr, public keys ARE the TLD. Controversial design decision I know, but I stand by it. So no plans to beg ICANN for a TLD. Gnunet begged for .gnu and ICANN refused. We need them even less, given that we use 52 characters TLDs, there will never be a collision with ICANN tlds.
20 million nodes are part of Bittorrent main net, which #pubky reuses More info here. https://pubky.tech
What happened to handshake? Never heard of openNIC 'til now... thx!
Handshake premined shitcoin with airdrop. I avoid.
Are you saying that pubky could improve censorship resistance of nostr but is not offering alternative solutions to communication protocol?
#pubky, like the internet, is a layered solution, designed to scale. Nostr does one thing well, transmitting notes and other stuff, from one user to another, using relays (which are web servers). Pubky tackles DNS, which nostr could import to allow every pubky to own a their own piece of the internet, in a censorshp-resistant way. This would be great for users, but, understandably, a bit scary for others. Pubky can also use web server, and they could use nostr relays, or even tor, because it's a layered solution. It's not really in competition.