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 (@rimu@piefed.social)

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 (@Fmstrat@lemmy.world)

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 (@baner@lemmy.zip)

Done. French, German and Italian came with it.

Import from other apps (@CameronDev@programming.dev)

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/

  • DionNam@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    12 hours ago

    If your wife actually uses it, that’s a better test than what the skeptics think. Thanks for telling me how the tag went.

    • terraincognita@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      Agreed, real use is the test that counts most. Besides that, there is the automated side:

      • unit and integration tests (handlers run against a real database);
      • end-to-end tests that click through real user flows in a browser (Playwright): the full suite on Chromium, a smoke spec on Firefox and WebKit;
      • property-based tests and reference vectors for the cycle math;
      • fuzzing of the parsers and validators, also in CI;
      • mutation testing: a weekly job breaks the code on purpose and checks that some test fails. Last measured, 93-98% of the mutants were killed, depending on the package.

      The details, and the limits of all this, are written up here: https://github.com/ovumcy/ovumcy-web/blob/main/TESTING.md

      None of it proves the design is right, of course. For that, people using it and reading the code are still the better check.