I can't believe I bothered reading that. Luckily the discussion of the client side encryption feature request gave me enough context to immediately stop.
As with all of these types of boards, it ships with some oddball u-boot bsp version, and from what I can tell upstream efforts for u-boot are going slowly (https://lore.kernel.org/u-boot/?q=lichee). YMMV. If you want to play ball with the shipping LicheePi4A bsp u-boot, you have to specially put firmware bins in /boot so that u-boot can slurp em and load em.
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?
I personally would wait to show it until it's usable. The self-hosting docs say "forthcoming". I'm quite interested to learn more, whenever that might be.
It is usable right now and beta customers have been using it in production for a while, just not in the self-hosted version. You can sign up here and try it right now: https://transitiverobotics.com/.
My CC company has been happy to handle this for me. A gym in a country I no longer reside in ignored all attempts to reach them to cancel a renewing, but non-contract, gym membership. The CC did a charge back and stopped future charges. Took a few minutes on the phone.
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.