On Nostr I just spray and pray that a Relay will store my data and that other users will connect to one of the Relays that sotred my data. In Pubky my Keypair is a censorship resistant DNS record that tells users where I store my Data (PKDNS). This offers a guarantee that I have all of the data that a User published, that I get the newest published version (mutability is still a big pain point in Nostr as Relays don't always respect updates or might not pick up on them) and on top of this is much easier to scale to a much larger Userbase. While both systems will to a certain degree rely on certain centralized data aggregators, on Nostr most Data will end on a handful of Relays. In Pubky you're likely going to see Indexers aggregate the Data from many Homeservers to build your Social Graph. Replacing an index that malbehaves is a matter of seconds. Replacing a few centralized Relays that host most of the data is much harder at scale. Regarding pubky.app, which is basically the first pubky-core based social application, there are some cool features like tags available with many more on the Roadmap for this year.

One truth many people on here are not ready to face: Pubky beats nostr in almost every technical aspect. https://pubky.app/post/gujx6qd8ksydh1makdphd3bxu351d9b8waqka8hfg6q7hnqkxexo/0034M0VM2ETV0

Allow JIT and it should work.

Yep. Pubky Tech is on another level.

needs to understand this is as well. The initial pubky.app prototype only pulled from Synonyms Homserver - this is not the case anymore. Pubky.app uses the Nexus indexer as to server your feed. Nexus keeps track of any Homeserver/User that it knows of. If you update your pkarr record (switch your homeserver) Nexus will automatically pull the data from your new Homeserver. Pubky.app is absolutely not tied to a single Homeserver. Long term the Goal is obviously that multiple Indexers and Apps are available that fetch from different Homeservers but all have the same Data. Trusting an indexer to build your feed is actually a lot more efficient than connecting to each Homeserver by itself. This is basically what a lot of Nostr apps (AFAIK Primal does something similar) are doing by connecting to a bunch of Realys. It will be very obvious if your indexer censors anything and at some point Clients will certainly allow you to set which Indexer you want to use (even host your own one). Different Indexers might also monitor Homeservers different Content-Types. Some Clients could opt to only monitor a single Homeserver and not use an Indexer, if they wanted to. There's a put-endpoint that allows you to ingest a Pubky ID for indexing in Nexus. https://nexus.pubky.app/swagger-ui/#/Bootstrap/put_homeserver_handler

Your Keypar can become your domain thanks to pkdns https://docs.pubky.org/Explore/Technologies/PKDNS

Second this. Pubky DX is actually already very good and will become a lot better this year. Had a blast working on https://eventky.app

+1 pubky is great

We should start using PKDNS https://pkdns.net/ https://docs.pubky.org/Explore/Technologies/PKDNS