GM ☀️ Yesterday they flipped the switch on social media for under-16s. The real lesson isn’t the age limit. It’s that any government can kill “social media” overnight. Because social media has a front door. A handful of companies you can knock on (or threaten). Nostr has no front door. It’s not even social media. It’s an open protocol, like email or the web. Social media is just one thing people build on it. You also get marketplaces, blogs, long-form, payments, communities, and whatever else people dream up. Your identity and data live with you, not in some corporate database. Apps like (iOS) and (Android) make it dead simple and secure: they keep your key safe in your phone’s hardware and let you sign into lots of Nostr clients without pasting , creating accounts, or signing up. No foreground app required. And the best part: they’re not social media apps. They’re keys to the entire open Nostr world. Sovereignty isn’t coming. It’s already here.

Shipping a small-but-satisfying fix in Clave 🔑 and an proposed update to NIP-46 The problem: when you connect an app to a Nostr remote signer over a bunker:// link (NIP-46), the signer had no way to know *which* app was connecting — so theconnection showed up nameless/generic. You'd approve signing for "some app" with no idea who. The fix: the client can now include its name, URL, and icon right in the connect request — the same info nostrconnect:// already carries, brought to the bunker flow too. Clave reads it and labels the connection properly. It's live end-to-end: Clave (signer) reads it, and our experimental client jank.army (client) sends it. Pair them and the app's real name shows up. We've proposed it as an extension to NIP-46 so any signer or client can adopt it. https://github.com/nostr-protocol/nips/pull/2381 Backward compatible — apps that don't send it connect exactly like before. cc https://clave.casa

Clave 🔐 0.2.0 Build 100 New in this build: • Bug fix: Low-trust signing now waits instead of failing. Set an app to "ask every time," post from it (e.g. jank.army) — it should stay pending until you approve in Clave, then go through. Deny = clean rejection. • Switch accounts right on the Share Bunker Code screen. • Connection detail now shows activity live. Live in TestFlight now. Open source, still beta. https://clave.casa

Thank you 🙏 Reach out to this account or if you have any issues!

“But where does my key actually go?” is the question we get most about Clave. So we wrote a plain-language FAQ. A preview: • Is my key on your server? No. Your nsec never leaves your iPhone. Our server just nudges your phone “you’ve got a request” — it can’t read anything or sign as you. • Why iOS only? Android has Amber; iOS had no equivalent, because Apple’s background rules block the way Amber works. Clave is built around them. • Should I use my main key? Your call. The honest version’s in the FAQ. The short of it: it’s one app holding your key instead of the dozen you’ve pasted it into. Full FAQ, no jargon → github.com/DocNR/clave/blob/main/FAQ.md