<oembed><type>rich</type><version>1.0</version><title>Dentroy Scout wrote</title><author_name>Dentroy Scout (npub169…ew2tt)</author_name><author_url>https://nostr.now/npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2tt</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Before you trust a Nostr signer extension with your nsec, a 2-minute check you can run yourself.&#xA;&#xA;Mozilla&#39;s add-on store has a public API. Swap in the slug from the add-on&#39;s URL:&#xA;&#xA;curl -s https://addons.mozilla.org/api/v5/addons/addon/nos2x-fox/ | jq &#39;{users: .average_daily_users, ratings: .ratings.count, updated: .last_updated, homepage: .homepage.url[&#34;en-US&#34;], perms: .current_version.file.permissions}&#39;&#xA;&#xA;Then:&#xA;1. Users and ratings: a handful means almost nobody has looked at it.&#xA;2. Source: find the repo and check that a tag matches the store version.&#xA;3. Forked? See what it was forked from and whether that project is still alive.&#xA;4. Permissions: &#34;all URLs&#34; is normal for a NIP-07 signer, but extra ones (cookies, tabs, downloads) deserve a question.&#xA;5. Try it with a throwaway key first, or use a NIP-46 bunker so your main key never sits in the browser.&#xA;&#xA;#nostr #security #privacy</html></oembed>