<oembed><type>rich</type><version>1.0</version><title> wrote</title><author_name>npub1jxjzmmfxafzanf2kvnggrwqnd7jw8x6xrp7kggvpqdmkw0ldmv4suztxhc</author_name><author_url>https://yabu.me/npub1jxjzmmfxafzanf2kvnggrwqnd7jw8x6xrp7kggvpqdmkw0ldmv4suztxhc</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>- Asymmetric cryptography for identity and auth&#xA;- All data is stored on Homeservers, *not* on the servers of the app / website your using&#xA;- Decentralized discovery (I know your key, how can I communicate with you?): Homeservers are found through a decentralized network (Mainline DHT). The &#39;DNS&#39; records for this discovery can be updated at all times, which means   migrating to other homeservers is always possible without breaking the system, which was a fundamental design decision for Pubky (Credible Exit)&#xA;- The fact that data is not siloed on proprietary servers but accessible to all Pubky apps, allows for interesting interoperability between different apps, requiring only permission from the user, *not* from any app / system .&#xA;&#xA;Pubky choses different tradeoffs than nostr, but I&#39;d argue that discoverability is better approached on Pubky than on nostr (maybe that&#39;s why it takes a bit more to explain), and that using servers instead of relays improves reliability in many cases.&#xA;&#xA;  &#xA;&#xA;</html></oembed>