Youre arriving to pubky's design in your own argument ... it *is* just PKDNS pointing to websites (domains, or IP addresses, or wherever). Pubky protocol work is making sure that actually works, and works in a way that others can do it with you. It's more work than you realize, but yes, Pubky (and nostr) are just websites on servers... but that is not a useful framing if your goal is to refute Pubky, because Pubky (pk) domains are actually censorship-resistant at scale, whereas Nostr, and ICANN, are not.

Nostr use cases are a subset of Pubky use cases.

Users only need to control their keys. They can use a trusted host for their data. If their host misbehaves, they can switch hosts or host themselves. Hosting yourself will be as easy as running an app your computer (still working on that being easy).

It's true that the only honest solutions for root-key rotation are going to all be shaped either as "backups i have somewhere else" or "here's a list of other keys I use if you need them" -- shamir social sharing is one way, but i think users wont like it.

You are still speaking very ignorantly about topics you seem to care about. Pubky.org is filled with good info, don't be scared to learn things yourself by reading. This method of passive-aggressively trying to poke holes in my answers is a waste of time if you don't even know what you are saying. Respect means trust, and you don't believe anything I say.

It is correct that you do not understand what is wrong with zaps, and that you do not understand me or our work. The rest is you projecting your own ignorance and discomfort.

BIP 110 is an IQ test.

Pubky uses public keys you control as domain names. PKDNS. It is powered by the millions of nodes that power torrents. You can host anything this way, not just posts.

Learn at pubky.org

I dunno, I still think you could cry harder.

Zaps are not interesting.

How hard can you think?

you deserve your loser life, you earned it, remember that