Ademan's avatar
Ademan
npub19jes...pt7r
Neanderthal hacking on Bitcoin stuff. LNHANCE please!
Ademan's avatar
Ademan 1 year ago
Bluacle? I kinda like it tbh image (I didn't change all of the colors so some of the contrasts are weird)
Ademan's avatar
Ademan 1 year ago
Seems like Lightning AMP combined with a loop-out service would be potentially pretty powerful privacy tech. Of course you need PTLCs to defeat attackers along the route.
Ademan's avatar
Ademan 1 year ago
With Phoenix gone from the US market, is there any comparable service I can recommend to normies? I actually wonder if an uncle jim LSP would be an MSB... part of that distinction was always iirc frequency, and whether it was run "like a business". Plus you automagically meet KYC with uncle jim setups. Of course, feds seem to be tearing up the rulebook and doing whatever they feel like, but how are they gonna know anyway?...
Ademan's avatar
Ademan 1 year ago
The javascript ecosystem makes me extremely grumpy and afraid image
Ademan's avatar
Ademan 1 year ago
Is there any nip that provides alternative download methods for links? If you imagine a kind 1 with an image linked in the content, you could include a tag that provides the sha256 for that URL, and maybe a list of blossom server hints, magnet link, etc. There's obviously A LOT of overlap with NIP-94 but it's still fairly distinct. #asknostr #nostrdev #nostr
Ademan's avatar
Ademan 1 year ago
Has anyone memed "great script restoration" as the "Great script Reset" yet?
Ademan's avatar
Ademan 1 year ago
Is there any built in nostr "verification" method? I'm imagining something like a bip-32 label that would indicate a user completed some form of verification, which applications can use as an anti-spam measure. The specific form of verification is irrelevant, and many providers could exist, they'd publish an event to indicate the result: { "tags": [ ["p": "verifiedpubkey...", ...], ["L": "verification"], ["l": "captcha-verified", "verification"], ], ... } { "tags": [ ["p": "verifiedpubkey...", ...], ["L": "verification"], ["l": "captcha-verified"], ["l": "email-verified", "verification"], ], ... } { "tags": [ ["p": "verifiedpubkey...", ...], ["L": "verification"], ["l": "phone-verified", "verification"], ], ... } { "tags": [ ["p": "verifiedpubkey...", ...], ["L": "verification"], ["l": "payment-verified", "verification"], ], ... } "payment-verified" might include the amount paid { "tags": [ ["p": "verifiedpubkey...", ...], ["L": "verification"], ["l": "fidelity-bonded", "verification"], ], ... } "fidelity-bonded" might include a UTXO and BIP-127 proof { "tags": [ ["p": "verifiedpubkey...", ...], ["L": "verification"], ["l": "twitter-verified", "verification"], ], ... } "twitter-verified" might include the URL of a tweet committing to the verifiedpubkey (and something from the verifiedpubkey committing to the twitter account?) I'm not sure if the extra information might warrant a different kind than normal labels.
Ademan's avatar
Ademan 1 year ago
Am I crazy or is nip-56 a special case of nip-32? Why both and why a different kind?