Next step in the Cashu Spilman channel system is to redesign the backend to make it easier to plug in any storage system that you like, e.g. sqlite, nostr, in-memory. I want to wrap up the functionality into easy-to-use high level functions, such as 'validate_payment', in order to make it very easy for service providers to start accepting payments via these Cashu channels. Some of those functions will need efficient ways to reach out to state management systems, but I don't want to hardcode one particular system into this library. The core code will stay in Rust for now, as that can be easily exposed (e.g. via WASM) to other languages. And I'll probably write these "bridges" for TypeScript [for continued use within the Cashutube blossom-server] and Python. So here's an LLM description of what I'll likely work on this evening, although I expect I'll want to convince the LLM to change some of the details of this plan before executing: == LLM description: == View quoted note →

Don't forget that you can learn from LLMs too, not just get them to write code for you. It added a bunch of CSS to my code that I didn't fully understand and got this great answer when I asked it to explain it: === Q: I want to you help me learn a lot more about CSS. can you explain thoroughly and thoughfully what all these do, including the flex and min-width that were there before you made that change: #left-column { flex: 1; min-width: 0; + position: sticky; + top: 0; + align-self: flex-start; + z-index: 100; + background: #1a1a1a; }

"Why does software privacy have such a great sound track?"