• 2 Posts
  • 14 Comments
Joined 9 months ago
cake
Cake day: March 7th, 2026

help-circle





  • These are fair, and the misconfigured server one is the strongest. Client-side encryption would limit the damage there, I can’t argue with that.

    The group case is outside what I built this for. It’s meant for a household. If you run it for other people, you become their hosting provider, and the docs say that plainly: the app keeps your records from other accounts and from the network, not from whoever administers the machine.

    The VPS point is true, but it applies to everything on that box, not just this app. If you don’t trust the provider with it, the answer is hardware at home.

    I won’t promise it, but optional encryption for the web version is on my list to look into now.

    On design mistakes: agreed, tests and fuzzing don’t catch a wrong decision. But the SSH example cuts both ways. That code was written and reviewed by very experienced people and it still got through. Nobody is immune, so what matters is whether mistakes get found and fixed in the open. That has already happened here: tonghuaroot reported a hole in the webhook address filter, it was fixed and published as an advisory (GHSA-hg2x-v5cc-m384).




  • Good questions, thanks for actually looking at the site.

    Encryption: client-side encryption is for services run by someone else, where you can’t be sure nobody reads or leaks your data. A self-hosted app has a different threat model. The data sits on a machine you control, behind a login and 2FA, and how the server side is protected is described in the docs. So for your own server it was never the goal. The sentence you quoted is about the hosted option, which exists for people who find setting up a server too hard. There someone else holds the data, so the site says it plainly. For those who want client-side encryption anyway, I’m working on a mobile app with encrypted sync. It isn’t released yet.

    The vote counter: you’re right, it can be spammed. That’s the price of collecting nothing about visitors, and I chose that on purpose. So far nobody bothers, bots included. I treat it as a rough signal and still decide myself what to build.

    AI and security: no code comes with guarantees, whoever wrote it. What I can offer is that all of it is public, with tests, fuzzing and static analysis in CI, and a SECURITY.md if you find something. If anything looks wrong, tell me and I’ll fix it.






  • English isn’t my first language, so yes, AI helps me write. That’s in the title.

    But nobody nods their way into fuzzing, mutation testing, signed releases with build provenance and 2FA with recovery codes. You have to want those things and keep pushing until they’re in. That has been my job for nine months and 3,400 commits.

    As for the README, it tells you how to verify the image signature before you run it, what every config option does and how predictions are calculated. For an app holding health data, I’ll take exact over personal.

    The code is public. Show me where nobody was steering and I’ll answer for it.