Yo. Come chat on Pubky.app
Its architecture is superior to nostr
carvalho's nostr competitor is not superior. here's claude's take:
The "credible exit" marketing claim reduces to: move your data to a new homeserver, resign your PKARR record, republish to the DHT. That is structurally equivalent to updating a DNS A record, and weaker than the Nostr outbox model in one important way — a Pubky identity points to one homeserver at a time (mirrors exist for reads only), whereas a Nostr npub writes to N relays simultaneously. Single writer endpoint is a worse censorship surface, not a better one. Mainline DHT records also expire in hours and require republishing, so liveness dependency is moved, not removed.
as far as i can tell, adding p2p DHT transport methods to nostr clients would close the gap on where you are hosting from completely. that's not even in scope for nostr protocol itself though, that's network transport.
The "credible exit" marketing claim reduces to: move your data to a new homeserver, resign your PKARR record, republish to the DHT. That is structurally equivalent to updating a DNS A record, and weaker than the Nostr outbox model in one important way — a Pubky identity points to one homeserver at a time (mirrors exist for reads only), whereas a Nostr npub writes to N relays simultaneously. Single writer endpoint is a worse censorship surface, not a better one. Mainline DHT records also expire in hours and require republishing, so liveness dependency is moved, not removed.
as far as i can tell, adding p2p DHT transport methods to nostr clients would close the gap on where you are hosting from completely. that's not even in scope for nostr protocol itself though, that's network transport.
3
