hodlbod on Nostr: A few months ago I asked nprofile1q…uxvl9 to sell me on using cashu. His argument ...

A few months ago I asked nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhks6tnwshxummnw3ezumrpdejz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uqsuamnwvaz7tmwdaejumr0dshsqgzsm98u9kzcp35zkpc62shck8335gqtq5yt4w26xwl0pp2a72qavvquxvl9 (nprofile…xvl9) to sell me on using cashu. His argument was focused on better payment UX, which is compelling.

But something I think is left out of the conversation around lightning/ecash is the funding UX, which can be very complex.

I recently started using routsr (and appreciate it), but it exemplifies this UX friction perfectly. I've written lightning and cashu integrations, and even I am confused by what the UI is telling me. This is not (entirely) the fault of the routstr developers, it's a result of the irreducible complexity of separate protocols for different technical tradeoffs.