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/

  • communism@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 hours ago

    It’s common to self host a service for a group of people. Not all period havers have a server lying around, or the skills to self host a sync server. If I hosted this for my friends I wouldn’t want to be able to read their period data.

    Also, there are other reasons one might want encryption. It could be that you’re hosting this on a VPS or otherwise not your own infra and don’t want the hosting company to know your cycle data. And in jurisdictions where abortion is illegal, this would be data wanted by the cops—through warrants to hosting providers, or seizure of devices in your home, in which case you want both encryption at rest on all devices and encryption in motion to prevent someone from reading intercepted sync data.

    Fine if law enforcement is not in the threat model of this app, but “nosy hosting provider/admin” should be imo. It’s still health data which is private and sensitive, even if it’s not evidence of a criminal offence.

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

      the web version is made for one person or a household on their own box, the threat model says straight out that whoever runs the server is trusted. you can host it for friends but then they trust you, same as with any server you run for someone. and with a VPS you pick the provider and the country yourself, the readme warns that a host can read what’s on its servers. encrypting in the browser wouldn’t really help here anyway, the same server sends the page code, so an admin you don’t trust could just change it and grab the key