Former mountain unicyclist here. Longest distance unsupported off road is 45km
Cashu Cashu nostr:note1smzcvxmrq8d0k4p7qj6slyx4vff8tlcpcdpctya590rctmupm7ysft94me
I sent you some more sats. My wallet implementation now auto-detects an entered npub and automativally figures out the Lightning address to send to.
The main stage Nostr panel from nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r is now available.
Just watched. Nice panel discussion! My favourite line: ‘If you have a technical problem, DM Derek.”
This was pretty funny. When Bank of Canada asked Canadians to stop Spocking the $5 bill. 
After a six-week out-of-country hiatus, getting my bike legs back. Venturing further out into the countryside. Into the hills tomorrow. 
So happy for you! Will do whatever I can to make Cashu a globally-accepted ecash protocol.
I have no idea where I got this from.
This was in response to nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a on X regarding zaps. Can someone help me understand this criticism? #asknostr
https://x.com/csuwildcat/status/1801949551709810696?s=61&t=pyD0Ss7rz5OYSJvOmUo0XQ
‘Play the board, not the opponent’ (former tournament player, here)
Yup.
A npub on its own is just a npub. That’s why I believe NIP-05 is a good start, though not the eventual solution. Reputation is a function of context: over time, the events that a npub emits, over relationships: the ‘web’ in which the npub is judged to be a good part.
Not sure we have the solution yet, but what is encouraging is that, with #nostr, we have a different starting point than other so-called solutions that have a permissioned starting point.
How do we counter that? IMHO, develop a protocol that is decoupled from IP/REST (though it may still use it)
That's the unspoken core issue. Many believe that you can't manage your own reputation and it needs to be left to others to manage.
Super news! IMHO, I believe that #cashu along with #nostr is the big game-changer.
Congratulations nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg and thanks to nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f for the LTS! nostr:note1jf8ckdug36wl9q7724q5f5x8cnfv2a4wzyxxr73wge4tfxc6vzmqkn80n2
I never knew I'd have so much fun reading IETF RFCs.
Their datatracker for each RFC is actually a really cool way to visualize changes over time as well. https://datatracker.ietf.org/doc/rfc9420/
Would love to see something like this for NIPs.
Yup. I am a co-author on this RFC, inspired by what I learned from implementing NIP-05
https://datatracker.ietf.org/doc/draft-carter-high-assurance-dids-with-dns/