rich1.0npub1jxjzmmfxafzanf2kvnggrwqnd7jw8x6xrp7kggvpqdmkw0ldmv4suztxhchttps://yabu.me/npub1jxjzmmfxafzanf2kvnggrwqnd7jw8x6xrp7kggvpqdmkw0ldmv4suztxhcnjumphttps://yabu.mePublic-key-identity like nostr, but with improved discoverability. --> If I know your identity (public key), how do I know how to communicate with your device/app? On nostr there is no clean solution for this, so it's a mess that causes centralization and unreliability/inconsistency. On Pubky there's PKARR, look it up. What about the data, where do your nostr posts live? Well a relay relays, but what does it do after that? It's called relay, not server, right? What if the data we're talking about is not a social media post but data on a street map for example. Kind of important that that data is served reliably, and completely (as in "learn all data from all users", but also as in 'old data doesn't vanish from the network'). Pubky uses 'Homeservers' as a reliable data layer in a decentralized world. So am I saying Pubky is better than nostr? No, I'm saying use the right tool for the right job. Different trade-offs. Different designs. You may have a hammer, but not everything is a nail. There's more to the story. Credible Exit. Separation of functionality (app) and data. Payment abstraction (Paykit). Decentralizing DNS. Check out these links: https://pubky.app, https://pubky.org, https://pubky.tech for more.