Just like that, a spec compliant NIP-55 library for Android developers. The library is just 250 lines of code, and gives developers full login/signing/encryp/decrypt support with 24 lines of code. Video is of a small sample app I whipped up to test the library. Repo coming in the next day or two probably.

Chicken and egg problem...create NIP-55 compliant library that doesn't work with Amber or create hacky workarounds to support the de facto signer app on Anroid and support shit compliance. We want open, interoperable applications and yet we support shit like this. Just shameful.

It turns out, Amber is not NIP-55 spec compliant.

It turns out I'm just going to make my own NIP-55 Android Signer library so we have something that is actually spec compliant. See ya on the other side.

NostrHub

NostrHub | Discover and Publish NIPs

Explore official NIPs and publish your own custom NIPs on NostrHub.

Do Android Nostr apps that have "Login with Amber" support actually support NIP-55? The first repo I checked uses the Amber Flutter library but hardcodes Amber's package name as the signer instead of using nostrsigner: as per the spec. As far as I can tell, Amber Flutter does support theoretical NIP-55 signers (of which there are probably none) but gives preference to Amber, so just not a great implementation. Who wants to enlighten me before I go create my own library? #asknostr i guess.

I think it's time for me to write a longform post on nsec bunkers...I requested bunker support for a nostr client and was told it was too hard for users lol. Hold my beer.

Jumble is fantastic, but a bit noisy with the bunker requests...switching to X21 for a while, very similar UI.

Truer words have never been spoken. View quoted note →

Lots of bug fixes to Signet this morning View quoted note →

Spun up a new npub for @Signet to track development and post some educational content on Nostr, nsecbunkers, security, etc. The account is completed operated by a bot I whipped up but happy to personally interact there as well. View quoted note →

My wife asked me what I'd been working on. She is not at all technical and her eyes glazed over immediately, so I asked an LLM to ELI5 it and tailor it to her profession. Here we go: Nostr: You know how if the company switches banks, you have to set everything up from scratch with new signature cards, new logins, new everything? Nostr is like having one signature that works at every bank. You're not locked into any single institution—your identity belongs to you, not them. Your key: It's basically your signature authority. Whoever has it can sign off as you. So you really don't want to hand it out. Bunkers: Think of it like keeping your signature stamp locked in a safe that only you can open. When an app needs something signed, it sends you a request—like an invoice hitting your approval queue. You review it, approve or reject, and the safe applies the signature. The app never gets direct access to your stamp.

Signet now pushes events in real-time to any client on any device. Video showcasing this via both the web UI and Android app. Self-host your remote signer. Let's make bunkers great in 2026!

In the immortal words of Eminem... "Now you see why I don't sleep, not even a wink, I don't blink I don't doze off, I don't even nod to the beats I don't even close my fuckin' eyes when I sneeze"

Happy 2026! May it be as wonderful and beautiful as you let it be.

And so it begins... View quoted note →

And so we have an Android app on @Zapstore

Signet - Zapstore

Keep your Nostr private keys secure on a server you control. When apps need to sign events, Signet handles the request. Features: - Real-time push...

You've probably tried vibe coding, BUT have you tried drunk coding...working on Signet for Android until I run out of soju lol