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/

  • tigerhawkvok@startrek.website
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 hours ago

    I have no use for this (my wife’s periods are medically irregular), but I’m definitely going to take both your initial question and this response to heart when, in perhaps a month (maybe as little as two weeks), I share an AIP with this sub.

    Even the motivator is similar — I’m android, my wife is iOS, and shareable notes are really dismal under that banner. A lot of “almost”, but nothing quite nails it. So for now an AIP it is, well into the dogfooding stage. (I just want to iron out what I’m sure people will bring up, but it’s at web and Android minimum viability already. iOS will be last because I’ll need to monopolize my wife’s laptop 😅)

    • terraincognita@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 hours ago

      Thanks, do post it when it’s ready. People here will poke holes in it, but mostly useful ones. Last time the first thing I got hit with was security, so maybe have something written up on that before you post. Good luck with the iOS part

      • tigerhawkvok@startrek.website
        link
        fedilink
        English
        arrow-up
        3
        ·
        5 hours ago

        Security isn’t actually too bad for me. The core brainwave for this project is that I (and I believe most people) nearly always want fairly boring notes, and sharing is kind of a conversation; so, the project is essentially a UI and UX wrapper around Signal! The host is Signal’s mock server, and the clients Signal’s clients; and sharing is just group chats, and revisions are history; rich text is Markdown. Internal application security is therefore already deeply vetted.

        Your post reminded me I should add a second layer of TOTP on top, though, especially because the access pattern is different.

        If you or anyone else here is interested in the alpha stage before I seek deeper feedback here, let me know.

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

          Building it on Signal is a smart call, the hardest part comes already vetted. Yes, send me the alpha when it’s ready.