Why do you need attestation? It seems to always either serve no real purpose (e.g. Bank apps) or be anti-user (DRM) (except for perhaps enterprise managed devices for companies with serious infosec requirements)
Replied below but TLDR (and not fixing myself) is that security requirements of the app are such that a compromised APK or rooted device running modified android could gain privileged access to sensitive information by bypassing/deep faking some auth mechanism. This isn't hypothetical: it's attacks observed in the wild that we've been forced to respond to.
Short answer: Dlog’s SEM is built for single-user, explainable, actionable inference. It estimates stable latent factors from many indicators, re-fits regularly to track changing effects, and ties coefficients back to your journal quotes so recommendations are grounded in lived data. SEM is computed on-device.
Why that matters? multiple indicators per construct (the 61 baseline items) reduce overfitting and let the model recover latent traits (Personality, Character, Resources, Well-Being) rather than relying on noisy single measures. AND, its not just the SEM, its mixed methods: dlog model's coefficients are linked to narrative evidence from your entries, giving both quantitative explanation and concrete journal quotes you can inspect.
I’m planning on adding a technical appendix and a white paper when I launch the Dlog Research edition for universities at some point next year. Meanwhile you can read the model summary here:: https://dlog.pro/#dlogModel and download an example mixed-methods report you can make in the Dlog Labs https://updates.dlog.pro/AnonDoe.pdf.
Thanks again for the interest; if you do register with Dlog email me at johan@dlog.pro and I'll give you a free perpetual license and 1 million tokens to test out Dlog.
This is a bug in zfs or in sqlite, sync=disabled should never cause actual corruption (it should at worst make existing corruption bugs in sqlite more likely & cause loss of committed sqlite transactions)
I highly doubt it's an SQLite bug, considering how thoroughly they test their code to behave correctly as long as their assumptions are filled. And those assumptions are clearly violated when SQLite runs on ZFS with sync=disabled (since writes may not be written to disk despite fsync).
