This is just a test

Key locking and time-based app permission suspension coming to Signet this week...own your Nostr keys.

Wow @Bitcoin Art Magazine, really great presentation, can't wait to dive in https://blossom.primal.net/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Working on the next version of Hyper utilizing the new unreleased backend. Since clients are Nostr-agnostic, expect an Android client the same day I push the new web client. It's gonna be worth the wait.

Spending hundreds of hours and failing is fine if you figure out why you failed and spend thousands of hours succeeding. Don't give up, fuckers.

Any idea why Jumble requests DM permissions when it doesn't do DMs? Or did I totally miss that?

Imagine a world, where you can write a Nostr website or application on any platform using your language of choice without any knowledge of the procotol and WITHOUT using AI. Still a work in progress, but here's a NIP-17 DM client I whipped up in about an hour using just HTML/Javascript/CSS as a single HTML file so it can be hosted on a Blossom server and served via nsite. More details soon.

Self-hosting your signer is not only important and super cool, but the way I designed Signet allows anyone to not just create their own frontends, but it also means you can approve/deny requests, and control app access and keys from anywhere. Lost your phone? Not a problem. Switched devices? Easy peasy. View quoted note →

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.