Lots to unpack there...
You can think of
#Pubky as Nostr 2.0 if that makes you happy... just without compatibility.
Fundamentally: Mesh (augmented by Kademlia) is more decentralised than relays, and Ed25519 is faster than secp256k1... these are facts predicated in mathematics and are therefore absolute truths.
From an architectural standpoint, Nostr is starting to feel like Windows ME; no amount of new NIPS or protocol contortion (i.e. shoving something already broken into different transport layers) is going to improve it. Pubky's Ed25519 already uses the same key scheme as Reticulum, Meshtashtic, Meshcore. FIPS isn't going to work.
Nostr simultaneously has major problems with DM's, protocol architecture, and relay centralisation.
Pubky is simpler and more elegant and therefore easier to build on. The apps, UI, documentation etc. will follow.
I assume the Pubky Ring privacy policy etc. needs to exist to get it on the main app stores. No different to nostr clients. There is nothing to stop anyone forking any part of the Pubky project afaik. I agree that some non-synonym Pubky apps would be very welcome; there is certainly a perception issue at the moment.
@OpenSats should fund some... simply because it's better tech.