jb55

Zero-JS Hypermedia Browser

avatar
jb55
_@jb55.com
npub1xtsc...kk5s
I made damus, npubs, and zaps ⚡️ Independent bitcoin core and lightning dev.

Notes (5)

“I work on bitcoin” “Oh so you’re a trump supporter?” the number of times i’ve had this conversation lately … just wow 🤦‍♂️
2025-11-22 03:56:59 from 1 relay(s) View Thread →
how i look coming off the last plane after 21 hours of flights image
2025-11-21 14:19:42 from 1 relay(s) View Thread →
one addition I want to make to this: user two-factor password and app salts this would allow you to add a two factor to your private data, associated with a specific app. if your key leaks you wouldn't get mass decryption of private notes. nostr:note1g8epn75k0lctmr0h6vj2uw6r7dt54n6c4tlaa348a23gt34h2k4stctxmq
2025-11-21 08:08:07 from 1 relay(s) View Thread →
this spec i made didn't get a lot of attention, but i think its pretty cool: https://github.com/nostr-protocol/nips/pull/1893 Private Note Storage is like giftwraps but: - Not spammable, author keys are pseudonoymous and deterministic from your main key. - Simpler wrapping. No seal is needed since the wrap key is deterministic. You just have the wrap and the internal rumor. - Only for your own notes - Zero public metadata tied to you. Giftwraps require a p tag of who is receiving the event. Since we are deterministically generating the private author key that is not tied to the master key, we can just query on that. Further improvements not defined in this spec: - HD keys (bech32) for creating private notes on new keys each time. No pubkey re-use for different private notes. Imagine having an HD keypath that stores a specific type of private note. There would be zero identifiable information on the public note. no p tags, just a random looking pubkey associated with a specific HD key path. I'm looking into this for storing private ai convos.
2025-11-21 07:28:16 from 1 relay(s) View Thread →