No dang, I don't care about the spirit of the site when absolute ludicrous mindrot garbage is up voted here constantly. You'll note on the Wayland thread that, despite being the 30th Wayland thread, the only substantive reply agreed with me. It's a joke.

Don't worry, I'm changing my password to a random guid, you'll be free of me in 45 seconds.

I love Rust, I'm a big fanboy, but we need to stop pretending there aren't glaring blind spots.

thanks!

lol, literally less than 20 seconds.

> Then, when does reconciliation happen? When either party goes online? What if it is not a closed loop system? Then, reconciliation needs to happen for both parties independently. How long can either party stay offline and continue to make transactions? Is it both send and receive or only send on one side and only receive on another side? What if one party (merchant/receiver) is more likely to be online (almost always). Does it just become online payments problem then? NFC tap and pay is exactly this scenario.

Again, literally the exact problem statement and value proposition of Lightning, but stupid, stupid me for daring to mention it here, I guess. Feel free to ignore that the idea behind Lightning could be useful without being tied to crypto, but can't possibly have a conversation about that. Nope.

These warnings are like "make backups", "use a password manager". Afaict, people are either going to, and have, or they're going to be lazy and assume it won't hurt them until it does.

And yes, it works with Windows: https://virtio-fs.gitlab.io/howto-windows.html

Contrasted with VF2 which appears to maybe even now be bootable from upstream u-boot with NVME. Something not even yet true of Rock5B from Collabora's "hardware-enablement" repos. (https://gitlab.collabora.com/hardware-enablement/rockchip-35...)

I'm supposed to be forgetting this. Maybe passing on the trauma is my way of healing.

Something I am (why, someone stop me?) curious about is the differences in toolchains used. I've seen it reported in several places now that stock GCC produces noticeably inferior code to the optimized th1520 toolchain. Is that going to change/be upstreamed/ etc?

Additionally, I've taken to using my providers throwaway card generator to make site-specific ones that I can then one-click disable whenever I feel like it.

Granted, they only have this exposed through a fairly buggy browser extension, you can't just "do it" easily on the website, so I won't bother giving them the free marketing of mentioning them.