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/

  • blitzen@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 hours ago

    I have no need for a period tracker in my life, but I understand why a truly private one is necessary.

    I’ve noodled around the idea of a period (as in time period, not cycle) tracking so that it could be used by non-uterus hackers. Like, right now everyone who uses one has a uterus. In my hypothetical app, anyone could use it to track things like getting a hair cut or mowing the grass. The idea is for people with privilege to add noise to the signal so that any reproductive use used by people who may be at risk would be slightly masked by those who are not.

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

      ha, took me a second to get the “period” thing. interesting angle, never thought about it as noise. thanks for reading even though you don’t need the app

  • DionNam@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 hours ago

    Going back through the old thread comment by comment, with links, is a great way to close the loop. Did putting the AI disclosure at the bottom change how people reacted compared to the March thread?

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

      Thanks. Yes, it changed things. The March post had no disclosure at all, and someone pointed out the README looked AI-generated. This time it’s in the title tag and at the bottom, and a few people stopped at that and never got to the app.

  • ComradeMiao@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 hours ago

    Evidently disagreeing with the need for this “app” and calling this slop will get your comment removed. Wild.

  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    9 hours ago

    Whoever administers [hosting provider’s servers] can read your records.

    Why not encrypt things locally before they get sent to the server? This is standard practice for most “privacy-first” applications nowadays.

    Counts one anonymous click. No email, no cookie, nothing about you is stored.

    For the “what to work on next”. How do you prevent bots spam clicking buttons multiple times?

    These are just two things that jumped out to me upon browsing your web site. But honestly, using AI to write code that handles such intimate data is a huge red flag to me - you have no guarantees that it is secure.

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

      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.

      • SavvyWolf@pawb.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 hours ago

        A self-hosted app has a different threat model.

        I can think of other cases where even if it’s self hosted, you still want this sort of encryption. What about the use case of a mother setting it up for a group of other mums in a group chat. The other mums would still want their data to be private. The hosting provider thing is valid, and I think actually extends further than you think. I may trust my own server, but I don’t know if I trust Linode or Hetzner or whoever I buy my server from to not snoop in my files. There’s also the fact that if I fuck up the configuration on my server, at least they aren’t going to get that data in the breach. (“I” in this case being an abstract person wanting to use the server. I don’t have any use for a tool like this).

        The vote counter: you’re right, it can be spammed.

        That’s fair, just be aware of it. The amount of people that make decisions based on flawed customer data is a big problem for software development.

        What I can offer is that all of it is public, with tests, fuzzing and static analysis in CI

        The recent SSH bug had all of this and let a security exploit slip through. The reason was that people made a sensible sounding but ultimately flawed design decision. Those are the types of errors that AIs love to make and that inexperienced users can let slip through.

        • terraincognita@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours 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).

  • smiletolerantly@awful.systems
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 hours ago

    I get the AI hate, but I’m still acknowledging that the output can be useful in some cases. I can also see that this might be one of those cases for a lot of people.

    That being said, this post being AI generated kills any interest from me. “I’m not an experienced programmer / I don’t have the time besides the job to do this myself…” I can get, but not being able to DESCRIBE your project in your own words is just a step too far. Also makes it seem like you did not, in fact, direct everything, but instead asked Claude what to add next and then nodded along to its suggestions.

    Readme and ads for the project being LLM is worse than the entire project being slop except for the README. At me.

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

      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.

      • Appoxo@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 hours ago

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

        I don’t know where the notion comes from that it’s either 100% perfect Oxford english or needing an AI to write it for you to the same degree.

        So what if it’s a bit broken english with broken grammar? If one can read and got the point across?

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

          Nothing wrong with broken English, agreed. For me it’s less about grammar. It’s faster, it helps me structure a long post and not forget things, and I can ask it to read the draft the way a user would. I get that it puts some people off.

    • ComradeMiao@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      11 hours ago

      I did not catch that about the post beyond formatting being weird. That 100% makes this trash.

  • tigerhawkvok@startrek.website
    link
    fedilink
    English
    arrow-up
    3
    ·
    12 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
      3
      ·
      12 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
        2
        ·
        11 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
          ·
          10 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.

  • Bongles@lemmy.zip
    link
    fedilink
    English
    arrow-up
    24
    ·
    21 hours ago

    Up front, I don’t care that you use AI.

    But man I hate what AI has caused me to do every time I read something.

    it’s context, Not a diagnosis

    Whether it is or not my brain immediately goes “AI wrote this”. Just because “it’s not X, it’s Y” or “it’s Y, not X” is such an overused AI phrase. Plus, the newer thing is “honestly? Sentence…” Which obviously people say, me included.

    There’s not really a point to this comment, I guess I’m just kinda ranting.

    • greybeard@feddit.online
      link
      fedilink
      English
      arrow-up
      10
      ·
      21 hours ago

      I get the feeling too. It’s made it harder for my own writing, because the second I use “it’s X, not y” thing, or a derivative, I have to stop and edit it back out and ask myself if I only did it because I’ve been too exposed to AI writing. It’s silly but still a struggle.

      Even with that last sentence, I was going to say “but still a real struggle” and decided that sounded to much like Claude. I spend a lot of time looking at marketing copy from a variety of software vendors, and it’s stunning how few of them are bothering to have a human touch. Marketing material has always been slop, but now it is extra soulless. Like, I didn’t know it was possible to have less soul than marketing copy pre-AI, but now it’s a soul vacuum.

  • Jayb151@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    16 hours ago

    I don’t have much to say, but I did set up a Ovumcy instance, and it looks really promising. I haven’t been able to get my wife to use it regularly though.

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

      Thanks for giving it a try! Yeah, that’s the hard part with any tracker. Adding it to the home screen helps a little since it then opens like a normal app. If she ever says what bugs her about it I’d love to hear it

  • AntOnARant@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    ·
    18 hours ago

    I don’t have much use for a period tracker but I applaud anyone that contributes their time to open source projects. Thank you for your efforts.

  • Rimu@piefed.social
    link
    fedilink
    English
    arrow-up
    15
    ·
    22 hours ago

    Wow. It’s always hard to know how many of those feedback requests are genuine and which are just spam. This one was real :)

    All the best with your app.

    • terraincognita@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      8
      ·
      21 hours ago

      Thanks! Your CSP suggestion back in March was one of the most concrete pieces of feedback in that thread, and it shipped a few days later. Appreciate you coming back to check, and thanks for PieFed too.