🤩 after you spend the evening in a beer garden discussing bitcoin, after unexpectedly getting to a local meetup
Stack sats and build local communities
Still are 😎
The right to privacy is as fundamental as the right to private property.
The wallet address is nostr:npub12eqwteq2c2w9trgt95d3w4cky0quprprp42xefy8snw8tdexq5gsp9c5ek, not Wallet of Satoshi. Both are lightning ⚡ wallets.
But with Walletano, you can even transform your email address to a lightning address so you can actually have you@yourwebsite. com as lightning address.
Sorry, my mistake, I simply misread it... It is indeed @walletano.com!
Today I tipped my waiter in #Bitcoin.
I used nostr:npub12eqwteq2c2w9trgt95d3w4cky0quprprp42xefy8snw8tdexq5gsp9c5ek's Send to Email feature.
https://link.medium.com/9XloNCnvRAb
In 3 minutes, he had the wallet up and ready, SATs instantly showed up in his wallet and I even helped him set up his custom Lightning ⚡ Address.
Show him some love by sending him some SATs!
Done!
How come the LN address is at walletofsatoshi? Is that independent of #Walletano?
nostr:note1rfh47l2rupzcp250hx8lz3yp69qtdzh3n2a0ugzxnu4zd75vrhcq2clxek
One missed high ball was that how Satoshi was also driven by the reaction to the 2008 bailout, just as John confessed a few minutes before.
I think Marty was smart to be patient, he has a much better feel for the optimal sell-hard level.
John has confessed that he does not understand Bitcoin, but I wouldn't be surprised if that will change in 1-2 years (not necessarily suddenly though). He shares the root motivation, and that's the most important.
Many plebs understand the tech first, and need a long journey to understand the real motivations and implications; the opposite path could be less tedious.
When someone recommended me John's latest video, I though he'd be a good fit on TFTC... and next day it happened!
I enjoyed the show, as it was different style then his videos, here he told some of the conclusions which are only alluded to in his video. Also, nice thoughts about his personal motivation, and how to keep the spirits high.
User agents IDs open up the Pandora's box of differential treatment for client (based on user agent), which in long term ruins interoperability. A standardized user agent just makes misuse easier.
User agents are also bad from privacy point of view.
There should be a NIP to _ban_ user agents... :D
I'm looking for an LN Splicing message sequence diagram. Anyone?
(Dusty seems to have a nostr account, but not used nostr:npub1fuk7q4y0wzqw7vjrg7xeuuva79pg7ctg69a53zsxq6gepksufrrst9mzly)
Scam spam has reached my notes as well...
#grownostr poppies
Keystr now supports NIP46+NIP26 combo!
https://github.com/keystr/keystr-rs
nostr:note1nsa35d8d99s7aat2gd6zz7fw38qvemq5l5y93xz22qtdw0zqhv9qt0sla4
Are there any Nostr client apps supporting _both_ NIP46 & NIP26? I've added combo support to my Keystr signer app, and I don't know how to test with real-world apps...
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet
nostr:note1p9v29uxqr8gz6rnwndxs2w0g4uhg3l6l77az2nqfucgpmdp5pgdqs76em3
BTW, respect for doing the whole cycle of raising an animal, caring for it, and when the time comes, killing, processing, cooking and eating.
When I was kid occasionally we had to buy live chickens, although living in a big city, but there was food shortage. But other than that I'm closer to the 'food comes packed from the store' crowd.
There is a -- probably unfounded and definitely not based on experimentation -- commonsense saying that cats play with their pray before killing & eating them so that they taste better. I even heard logic that blood sugar goes up and thus they taste sweeter, but I think that's bullshit.
The reason I'm skeptic is that I see no evolutionary benefit from doing an action to change the taste of sg, rather, taste has evolved to improve the selection of what to eat, and derive evolutionary advantage from that. I doubt there is nutritional difference between a stressed out and normal version of the same prey.
Keystr now supports NIP46+NIP26 combo!
https://github.com/keystr/keystr-rs
nostr:note1nsa35d8d99s7aat2gd6zz7fw38qvemq5l5y93xz22qtdw0zqhv9qt0sla4
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.
Testing NIP46+26 combo, using Keystr
nostr:note120dqd8nv282wqtjxltp66s90t0trvjazvjqygpq38e3yevm4je0s6ssjm2
poppyflower