Please do! Google Keep was my go to, and for self hosting i did enjoy Blinko. I feel this is the best of both worlds! Let me know your thoughts. I do my best to continue to improve my apps and implement bug fixes, new features, and be as responsive as time allows me.
Yes of course. I will look into and hopefully release in the very near future.
Thank you. Alot of time was put into this locally, prior to releasing anything on github… and happy to look into your request! To help me track it, would you mind submitting a feature request on the GitHub repo? I appreciate your input!
One thing I wish ai would teach vibe coders is how to use semantic versioning.
Trying to infer state of project from versions in ai-assisted software is an exercise in confusion.
Thank you. Hoping to continue to improve the products in meaningful ways. Always appreciate your continued support!
yes both are included as an available option to enable/disable!
Yeah, unfortunately that’s a Google account/billing thing, not a playback thing. Fathom only fetches the video stream on your machine; it doesn’t touch your account or Premium. That “verify your country” check is much stricter than playback and wants a residential IP in the country, so datacenter VPN ranges like Proton’s can get “flagged”. Nothing i think a media client alone can get around.
Interesting idea, but that’s out of scope for this app, Fathom is just a Jellyfin/YouTube/Seerr client, with no torrent or P2P layer, so there’s nothing for I2P to integrate with.
Unfortunately, it’s Jellyfin-only. Emby and Jellyfin came from the same codebase originally, but their APIs and auth have drifted apart enough that Fathom’s Jellyfin-specific calls won’t work against Emby. No Emby support planned, the focus is Jellyfin, alongside the Seerr and YouTube pieces.
Yes, the YouTube side is fully client-side, the app resolves and fetches the stream directly, the Jellyfin server isn’t involved at all. So YouTube sees the connection of whatever machine is running Fathom, using that machine’s IP and location. Fathom doesn’t spoof anything itself, but because it’s client-side, running it at home or behind a VPN is what should decide the location YouTube sees.
yes here are a few of different areas:
Appreciate the kind words, thank you.
Happy to hear! You are very welcome!
Updated, thank you.
Thanks for pointing this out. As I’ve mentioned before, I have always been transparent about utilizing AI assistance to help develop my apps. I wasn’t aware of the requirement to include a specific tag for them, but I appreciate you letting me know. I will make sure to include [AIP] in the title of my posts going forward.
Thanks for giving it a chance. Alot of time, effort, and testing went into this self hosted app. I am a longtime Mealie user and though its an absolutely great recipe manager, there were a few more things i wanted to see in an app like this, and thus CookTrace was born. Feel free to report any bugs or feature requests on the github page.
RC2 now includes improved import functionality. I believe this will address your concern above!
should now be addressed in latest RC6.
Genuinely useful feedback, thanks for taking the time. Walking through each:
Per-exercise sharing. Real gap. The exercises table is already structured cleanly enough to dump one as JSON; adding a “share this exercise” button that produces an importable file is small. The community-repo idea is good too: a separate awesome-lifttrace-exercises repo where people can drop contributions, and the in-app importer can read from a URL. Going on the roadmap.
Custom equipment + searchable tags. The schema already supports arbitrary equipment strings; the UI just defaults to a fixed list. Adding a “+” in the equipment picker plus a “what’s available today” filter chip set on the Exercises page is genuinely useful, especially for travel and home-gym use. Adding to the roadmap as a near-term candidate.
Per-exercise timer for time-based work. Real gap. The rest timer infrastructure exists but doesn’t currently cover “do this exercise for N seconds with a countdown and a cue.” That’s a meaningful addition for anyone doing carries, planks, isometrics, hangs, or hybrid stuff. Sharing the same audio + haptic plumbing as the rest timer keeps it cheap. Roadmapped.
Per-set / per-round rest in HIIT-style circuits. Currently rest is global with per-exercise memory, which doesn’t cover the “20s between reps, 2 minutes between rounds” pattern you described. That’s a structural change to how sets express rest. Going on the list to think through together with the time-based timer above, since they share infra.
Heart-rate data. The export direction you called out is the cheap win, and you’re right that PWA makes it easy. I’ll push a CSV export of the completed workout (sets, reps, weights, RPE, timestamps, rest durations) in a near term RC. That covers anyone who wants to feed an external analysis pipeline. Live HR ingestion from a BLE chest strap is the heavier direction and goes on the roadmap.
Thanks again for your valuable feedback. Appreciate the level of detail.
Yes. You can share any note or checklist with other people on your server, with view or edit access. Pins, labels, colors and reminders stay personal to each person, so a family member can pin the grocery list without it jumping to the top of your grid.
It isn’t live yet, though. Changes sync rather than stream. The Android app syncs every 30 seconds and whenever you open it, so a checked-off item shows up on the other phone within about half a minute. In the web app, changes from someone else show up when you refresh, reopen the note, or pull down on the list.
If you both edit at the same time:
Live updates, where a tick or edit shows up on the other person’s screen within a second or two, are very doable, and I’d like to add them. If you open a feature request for it, it goes on the list and you’ll get a notification when it’s in: https://github.com/TraceApps/notetrace/issues/new?template=feature_request.yml
A couple of lines about how you’d use it (for example, two phones on one shopping list at the store) will help me with envisioning how this should work.