#grownostr poppies

What's the difference between NIP-46 Nostr Signer and NIP-26 Delegation, and how can they be combined? Both solutions deal with the scenario when you want to use a Nostr app without entering your secret key, and a 'keystore' app which only deals with your keys. In the Signer solution, every single time the app needs a signature (posting a note, a like, a follow, etc.), it reaches out to the Signer for a signature. Communication happens over Nostr events. In the Delegation solution, on the other hand, you first create a delegation, which allows the app to post on the behalf of the user without the secret key. Typically a delegation is restricted for some period (e.g. one month). Signing the delegation requires the key, and the delegation has to get to the app. The two approaches can be combined: the app can request the Signer to sign a delegation, and it can use the delegation right away to post on behalf of the user, without needing to further contact the Signer. I hope to see more apps supporting both NIP-46 and NIP-26 in the future.

View quoted note → I was wondering if the lightning channel construct could be generalized to 3 (or more) parties; I've found the/an answer in this bitcoin.stackexchange.com question.

Got thinking about Nostr Connect (NIP46) setups, triggered by @nQuiz . There are two apps involved: [1] client app (wants to sign, has no sec key) [2] keystore app Different setups are possible: - client in browser, keystore in browser extension (like Alby) - client in desktop browser, keystore in mobile app: display/scan QR code - client in mobile browser, keystore in app (same device) -- ? maybe deeplink+NIP89 app handler Manually swtiching to the app and copypasting connect string is a fallback, but terrinle UX.

View quoted note → NIP-89 rules!

People often nuke their Nostr contact list. This can happen e.g. when a client uses a not-recent version of the contact list, and reposts it. For examples, check out messages of this bot: @Contact List Deletion Watcher Bot

View quoted note → nsecbunker by Pablo, keeper of nostr keys

View quoted note → Nostr Army Knife, little tool to parse any nostr ID.

nostr web army knife

View quoted note → Primal caching server. There was an explanation on the OSS caching servers by Primal.

Bitcoin must be *both* sound store of value *and* medium of exchange. Without the second, it's like a deserted castle where nobody visits, without the first, it's like a castle built on sand.

Fire up your old miners in the basement, the BRC20 crowd is streaming sats to the miners!

Can't zap!!! 💀 Is WoSatoshi having issues?

Nostr and Bitcoin key handling is very similar on the tech side. But there is an important difference: with Bitcoin one usually uses multiple pubkeys or even clients, and want to hide any relationship between those. In Nostr, one mostly wants the same identity (pubkey) across different clients.

How many users are on Nostr? Well, it doesn't really matter, the fact is it's growing! Recently I've heard numbers like 250k or more. With a little crawling (follows lists) I found ~160k pubkeys.

In here there are about 320 pubkeys with over 1k followers, the top having 24k (as found by a little crawling). Nostr is huge, but plenty of room to grow. #nostr-follows

Pizza Day Prague less than a month away!

In @gossip, I often have chicken-and-egg problem: - it cant fetch anything until I manually enter some relays - relays used are picked based on follows list, if the follows list is empty, it does not connect to a relay - even after I add relays, it often has difficult getting my meta, or my follows list

Cashu -- ecash+BTC/LN combo -- is a great idea. As I see, it combines the drawbacks of - self-custody solutions (you can lose your funds) - custodian solutions (they can rug you) :))) Still, it's a great idea!