2025-11-16T18:00:00Z https://nostr.now jorge https://nostr.now/npub1xpq2h8xgevveqzukrwz2l7w2uyz4emm0h0m2e0r8jepvj2pkh9dszpjjl7 https://nostr.now/nevent1qqsz6ygd63fzq5rdqq0qywv0ud55f7k2au5z3ynmj99vghh7zx6t7xqzyqcyp2uuer93nyqtjcdcftleetss2h80d7aldt9uv7ty9jfgx6u4k5vw24x In reply to <a href='/nevent1qqsqqq9pn36yzca07gq0j7kk0jmea974rdkgd0rpkclhkr8g5ah98vgh9qzll'>nevent1q…qzll</a><br/>_________________________<br/><br/>This is gonna be unpopular but I need to say it anyway. There are legit reasons for using multiple keys:<br/><br/>1. I want to avoid a single point of failure. In case my &#34;twitter&#34; nsec is ever compromised, I don&#39;t want my whole Nostr life gone.<br/><br/>2. If app ownership needs to be transfered to someone else, how would I do it when everything is tied to my personal omni-key?<br/><br/>3. Imagine a company where many people are involved in the development/deployment of the app(s). Which key should it use? The one of the CEO? Or the most popular employee&#39;s one? It makes perfect sense to me to have app-specific keys.<br/><br/>4. Web of trust is nice but how does it work for people who are just starting? Even their most popular npub doesn&#39;t have enough reputation.<br/><br/>5. Similarly to #4, some people might not even be beginners but just aren&#39;t very active on social networks. Same impact for their npub.<br/> 2026-10-25T08:03:04Z