Solving the Nostr web clients attack vector
One problem Nostr still has to deal with is the fact that web clients are "owned" by someone, because they rely so much on the domain name they're served from.
Everything is fine with, say, https://coracle.social/, until
With native apps that problem isn't so big as updates aren't mandatory, automatic and invisible as in the case of web apps (although there is still a problem with malicious app stores such as Google Play, but we can't solve everything at once).
Maybe the correct way to approach this would be to treat Coracle as a subjective thing, not "whatever is on the coracle.social domain", but "this version of Coracle I use represented by this hash".
Any decent Nostr web client must be capable of running entirely on the client side, as a "static" webpage made of just HTML, JS and CSS, so it should be possible to have these files hosted on Blossom and referenced by the hash of the "index.html".
The hard part is how to get users to use not https://coracle.social/ directly, but their chosen version of Coracle, which they update voluntarily whenever