Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T

terraincognita

@ terraincognita @lemmy.world

Posts
1
Comments
17
Joined
15 hr. ago

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • I agree, though there is a difference in case you rovided and mine. It is a human-directed work. Thousands of libraries, Kubernetes, Kubernetes still live and license is valid.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • Thanks for the suggestions, those are good points.

    CSP is something I plan to tighten over time, but enabling a strict policy right now would require refactoring some inline JS patterns used in the templates. It’s definitely on the roadmap as part of security hardening.

    Regarding CORS, the application currently runs as a same-origin server-rendered app rather than a cross-origin API, so CORS headers aren’t enabled by default. If external clients or integrations are added in the future, I’d likely introduce a restricted allowlist for specific API routes.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • I use Android, my wife - iOS. So many things that on F-Droid are simply unavailable to her (yes, I tried to convince her to go to our side). So I searched for living projects with self-hosting idea, did not find one and decided to create one. I have a CS background, though my professional work today is mostly in finance as a senior analyst where I write code to automate and optimize workflows. Ovumcy started as a personal project exploring a self-hosted approach to cycle tracking.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • Yes, I’m aware of those apps. They’re great local-first mobile trackers. Ovumcy explores a slightly different approach - a self-hosted web app that can run on infrastructure you control and be accessed from multiple devices.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • I see that we face it all over the world now.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • As a non-native speaker, I had to use LLM to get that joke)

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • It is a greap project, mine is not a replacement, but a little bit different approach. It's a self-hosted web application that you run on infrastructure you control and access from multiple devices. In Drip you can export or import data, but this step is a payment for privacy. Mine offers privacy but from a different perspective.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • You can see that I use some of metrics, like test coverage, estimates and so on to prove its validation as potentially serious project, that will grow from a pet one.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • Partially agree, but I do know how to code and use it as a tool.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • Appreciate that!

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • Ovumcy isn’t trying to replace them. The idea here is to explore a self-hosted, web-based approach that focuses on running the app on infrastructure you control, with simple deployment and cross-device access through the browser.

    Different tools optimize for different things. Native apps like Drip or Mensinator are great for fully local tracking, while Ovumcy explores a self-hosted model that can be accessed from multiple devices without relying on a third-party service.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • I answered earlier, that I use AI and this is just a commit skill for an agent.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • Well, not stealing, being inspired)

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • The benefit over a purely local app is mainly cross-device access and easier syncing/backups, while still avoiding a third-party service storing your data.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • I do use AI tools while developing this project, but I also have a BSc in Computer Science. AI is a productivity tool.

    Security is something I take seriously, especially since the project deals with health data. All code has test and you're welcome to inspect the repository yourself or point out any specific security concerns if you notice them.

    Regarding licensing: the AGPL license applies to the project as a whole regardless of the tools used to write parts of the code.

    If you have concrete technical feedback or security issues, I’d genuinely appreciate it.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump

  • I like the naming:) and is there any chance to restore access to your account? It looks like it might have a future.

  • I built a self-hosted period tracker because I couldn't find one worth using

    Jump
  • Selfhosted @lemmy.world
    terraincognita @lemmy.world

    I built a self-hosted period tracker because I couldn't find one worth using

    github.com /terraincognita07/ovumcy