mofosyne

Ah good to hear!

Well regarding how CSV didn't quite work for you. Have you checked out recutils?

Its a GNU Project and at least does basic relational database operations on plain text files. You can easily install it in most linux package managers.

https://en.wikipedia.org/wiki/Recutils

Instead of having to regenerate a zip file everytime you add/delete a memory... could we just use a git repo of markdown pages?

This buys you incremental writes, commit hash pinning and diffs for free. In addition to having a git archive outputting a zip export as well?

Main wrinkle is you would need to gitignore the sqlite database as it doesn't store very well in git (binary, changes lots per insert). But it's easy to regenerate anyway as a rebuild-able cache.

Found this video quite interesting. One bit was a bit funny where telling the AI model to not think about it, it ends up thinking about the concept in it's J-Space and the word "Dammn" as well

Wonder if textlog have an ssh interface as well

Reminds me of when railways attempted to attach linear barcodes on their train and read it using a similar method

Can this trans-compile to C? (And vice versa?)

Got the Prusa MK3S+ and it's been perfectly reliable for years

Religion and Automation is not a new thing... cue...

https://en.wikipedia.org/wiki/Prayer_wheel

Kinda like the demoscene of the pathogen world

There's a youtube video about this OS if you want to see what it visually looks like

https://www.youtube.com/watch?v=jNWx1Rn76Gg

The Linux Distro For Writers --- Mr and Mrs Linux

Wonder if this problem would be reduced by some mechanism of incurring cost on job positions that advertise for more requirements. (A heavy handed approach would be to charge an additional fee/tax if you require university educated persons for a position not requiring one)

Hopefully it has at least a checksum

I'm sure there's a general rule of thumb where this approach works best as an approximation (such as a simple on/off switch)... which may give us opportunities to simplify the BOM list further with cheaper parts at cost to accuracy which wouldn't apply to PCB anyway.

Where I mostly seen this approach is with 3D printers where we just want to know if the nozzle is touching the print base.

But if we can quantify the general worse case variation between most PCBs then maybe we can create a recommended strain sensor element with a semi-quantified level of accuracy so it's not just an on/off sense.