Icymi View quoted note →

Working on a kill switch for Signet. Phone lost? Server hacked? Keys compromised? Not a problem. Send a DM to any of your managed npubs and lock lock down your nsecbunker. Currently working, commands, "lockall" (all keys) "lockkeyname" (in screenshot below), and "lockapps" (suspend app permissions). Syntax is a work in progress. Will add key and app deletion as well. With this in place, dead man switch for all your keys a possibility as well.

I don't know who made this, but I'm dead lol

Just pushed Signet 1.3.0 to the repo (github.com/Letdown2491/signet) and @Zapstore. Notable improvements: 1. Lock/unlock keys 2. Suspend permissions on apps (time-based ACL) 3. One-time bunker:// URI generation with 5 min expiration and QR code generation 4. Daemon health monitoring and smarter restart logic 5. Tons more, just read the changelog lol

Once I release [redacted] I'm gonna rewrite Bloom and launch an Android app. Will probably just do web and Android for everything moving forward. Tonight, new Signet release...

I don't believe that clients should hold keys in any capacity but I can appreciate Primal trying to make this process a bit simpler. Of course, I believe only you should hold your keys which is why I've been working on Signet (just search on Github, I spam it here enough lol). View quoted note →

If you missed the demo video for this, here it is again: View quoted note →

Just released nip55-android, a library for Kotlin Android developers to implement NIP-55 Android signer support into their applications easily (about 20 lines of code).

GitHub

GitHub - Letdown2491/nip55-android: Library to easily implement NIP-55 Android signing support in Kotlin applications

Library to easily implement NIP-55 Android signing support in Kotlin applications - Letdown2491/nip55-android

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?