What's next for Pubky?
🚀 1. Launching a relatively feature-rich version of our our flagship "Pubky App": Private beta first, then public beta Q1 2025.
🔑 2. Prototyping & launching a new authenticator app for managing keys, sessions, and DHT records.
🌱 3. Launching initiatives to cultivate an ecosystem of exceptional builders using & contributing to Pubky Core.
This is just the beginning. Our 2025 roadmap is (overly) packed with exciting plans.
Get ready to take back the web with Pubky in 2025.
"Your public key is your self-sovereign domain name"
I like the idea of pubky and pkarr storing key-value pairs in a dht, but don't I get something similar with a nostr npub and publishing a kind 0 event with metadata?
This image depicts sample distribution of the millions of Mainline DHT nodes that are Pubky-compatible.
What do you think this map would look like for Nostr relays? What do you think it will look like in 5 years?
In the end, I recommend you to use the best tool for whatever problems you are trying to solve, and that can be different for everyone.
"In the end, I recommend you to use the best tool for whatever problems you are trying to solve, and that can be different for everyone."
This sounds like obvious advice, but I'm always amazed at how many people apparently don't find simple truth to be self-evident. More often, I encounter people who discover some "cool" solution, and then try to figure out how to make it fix their problems.
I see how pubky can complement nostr. Pubky can be the ‘trust anchor’ that is stable over time. Npubs can point to a pubky and a pubky can point to a npub for strong binding. This is similar to nip05, except that pubky uses the mainline DHT to store records instead of DNS. I see it as a complement/alternative to nip05.
So far, Nostr elders do not seem interested in bridging or breaking the key model, but yes, any platform or protocol could use the pkarr method, and it would almost certainly improve censorship resistance.
My guess is that, once you do something like that, people will just find it easier to use Pubky keys/apps/servers, as they will have all the tools needed to make it easy to maintain your dht records, swap servers when needed, etc, and bridging doesnt seem to usually be a popular feature to maintain.
It would be nice to standardize “pubky” to be in the kind0 event to be presented on a profile, similar to nip05. I’d be happy with that.
It would also be nice to standardize the resource record formats to be the same for DNS/DHT records.
I totally get the value have a trust anchors in other systems. I see nostr as being fairly transient, so if I compromise a nsec I can rotate easily, because everyone to trust the corresponding npub they would check the pubky trust anchor first.
