Litestream looks interesting but they are still in beta, and seem to have not had a release in over a year, although SQLite doesn't move that quickly.

Is Litestream still an active project?

Thought about it, decided to start with simpler and good enough option. The goal here is not to beat Redis anyway.

Any time someone shows only HTMX examples without error handling I feel like they have not tried it in an actual use case. To me it feels non-obvious how to handle these non-happy-path things without having to write client-side code which is what I understood HTMX promised to do away with.

In the traditional browser model that HTMX espouses to emulate and improve on we have form resubmitting (with a warning that it will resubmit data), we have different errors for if the server returns an error or if your wifi disconnected, etc. Those errors are perhaps not well designed, but they are there and explain what is happening. With HTMX (at least when I tried it) it just got swallowed and one had to write client side code to handle it.

I read the K (K9) manual[0] and it points to https://shakti.com/ as the authoritative place to download K, but the download link is gone and Wayback Machine hasn't helped

[0] https://estradajke.github.io/k9-simples/k9/Introduction.html...

This was also a huge obnoxious issue when I think GitHub was offering some kind of promotional T-shirt for a certain number of open source related pull requests.

There needs to be a way to setup a filter that auto denies comment only based PRs, unless it comes from a dev with a certain minimum "reputation / contribution" threshold score.

EDIT: It looks like something that mostly addresses my problem, “strict tables”, was added in 2021. Thank you everyone.

It seems this rewrite would not have addressed my biggest gripe with SQLite: Surprisingly, it is not actually type safe.

    SQLite uses a more general dynamic type system. In SQLite, the datatype of a value is associated with the value itself, not with its container.

https://www.sqlite.org/datatype3.html

That’s right, the type you give to a column when creating a table is merely a suggestion. This means at some point, TEXT may make it into a column where a NUMERIC is expected.

This actually caused a large scale problem in production once.

I still love SQLite, it’s the very best at what it does, but I’m a bit more careful now. The same documentation says SQLite uses dynamic typing so that you can “do more things” than with other databases, but for me this is akin to saying you can “do more things with assembly than with a high level language” (in both cases that’s mostly not even true).

I expect my SQL database to keep data from taking the wrong form. It looks like the SQLite 4 rewrite would at least have enabled constraints by default…

I think many would appreciate a “no surprises” strict, type safe mode in SQLite 3, for me this would complete it. Maybe that exists already?