Hi all,

In March I posted Ovumcy here. It’s a period tracker I built because I’m on Android, my wife is on iOS, and I couldn’t find a self-hosted option that worked for both of us. That thread got 80 comments and a lot of them were criticism. Most of it was fair, so here’s what came of it, comment by comment.

Strict CSP and CORS (@[email protected])

CSP shipped a few days after that thread, with no inline scripts. CORS stays off since everything is same-origin.

“The README looks AI-generated” (also rimu)

You were right. The full disclosure is at the bottom.

Irregular cycles and reminders (@[email protected])

You can now tag cycle factors like stress, illness, travel, sleep disruption and medication change. Stats show which ones come up in longer or shorter cycles. It’s context, not a diagnosis. Reminders come three ways: an in-app banner, a webhook to your own ntfy/Gotify, or a private read-only .ics calendar feed.

Spanish (@[email protected])

Done. French, German and Italian came with it.

Import from other apps (@[email protected])

Still not there. Not forgotten.

“Why not drip / Mensinator?”

They’re good apps. If one phone is all you need, use them. Ovumcy is for when you want the same data from several devices and already run a server.

Also new since v0.3.1 (now v2.2.1): PostgreSQL besides SQLite, optional OIDC sign-in and TOTP 2FA, and packages for YunoHost, TrueNAS (community catalog) and StartOS (community). Every claim in SECURITY.md now has a named test behind it.

AI disclosure (rule 8)

  • Design: Pair. I decide what the app does and the security model.
  • Implementation: Generated. Claude Code agents write most of the code, one PR per change, directed and reviewed by me.
  • Testing: Generated. CI runs unit tests, Playwright e2e and mutation testing.
  • Documentation: Generated, edited by me.
  • Review: Pair. Automated review agents plus me before every merge.
  • Deployment: Assisted.

I know this sub has mixed feelings about that. All I can offer instead of promises: everything is public, and if you find a hole I’ll fix it and credit you.

If you want to help

  • A ⭐ on GitHub is the easiest way. That’s how people looking for a private cycle tracker find it.
  • Bugs, ideas and missing features go to Issues. Feedback from people who actually track their cycle is the most valuable.
  • Translations are welcome. If your language isn’t there yet, CONTRIBUTING.md explains how.
  • If you know someone who wants a tracker that keeps their data at home, send it their way.
  • Donations are possible too, see ovumcy.com/support, but a star and an honest bug report help just as much.

Repo: https://github.com/ovumcy/ovumcy-web

Site: https://ovumcy.com/

  • terraincognitaOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 hour ago

    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).