:)

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!

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 here are a few of different areas:

Appreciate the kind words, thank you.

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!

Honestly, not automagically. CookTrace’s bulk importers today handle JSON, HTML, schema.org Recipe markup, and full-backup zips from Mealie / Tandoor / Paprika. Plain text, RTF, and PDF aren’t on that list yet, and there’s no “point at a folder and import everything” mode.

What works today for the same end goal:

• Photo Import — point Trace AI at an image of any recipe (including a PDF you’ve screenshotted) and it extracts it. Fine for a handful, probably painful for hundreds.
• Trace AI chat — paste the recipe text into the assistant and ask it to create a recipe. Same idea, no image step.

A proper OCR import is a worthwhile feature. I created a feature enhancement request in the GitHub repo, so that in the near future I can set aside some time to explore how feasible it would be to implement.

That URL should import cleanly; it’s a standard food blog with the markup the importer expects.

TikTok though, honestly, no. TikTok pages don’t expose the recipe text to scrapers and the AI fallback has almost nothing to work with. A real TikTok URL importer would need to call TikTok’s caption API and transcribe the video audio, which isn’t built yet.

Workaround that may possibly work today: screenshot the recipe overlay (or the comment where the creator wrote it out) and use Photo Import the AI extracts the recipe from the image. Two taps, same result.

Not right now. I want to get all my apps past the RC stage and into stable GA but will certainly consider it in the future.

The app is primarily aimed at lifting weights but does also account for body weight exercises such as pullups, pushups, etc. with respect to walking/running/cycling etc, i have that incorporated into my other app which is primarily focused on nutrition/wellness called NutriTrace.

just added. Was a request for my other NutriTrace App so made sure to add it here as well.

Appreciate the tip. Thanks!

Cookidoo has no public API and their ToS prohibits scraping, so a direct integration would be both legally fragile and maintenance-heavy (the scraper breaks on every UI change Vorwerk pushes). The indirect path that works today: Mealie is a self-hosted recipe manager that imports Cookidoo URLs as one of its many recipe sources, and NutriTrace has Mealie integration built in (Settings → Mealie). Your wife adds recipes from Cookidoo into Mealie once, and they show up as searchable foods in NutriTrace with full nutrition.

Also worth mentioning: I’ve got a sister app called CookTrace (may not be final name) in development as a purpose-built self-hosted recipe manager that pairs natively with NutriTrace (same UI patterns, same AI assistant, federation already wired between them). It has a schema.org Recipe scraper for URL imports, though Cookidoo itself is gated content so it’d still need either a Mealie middle layer or manual entry. Currently private; aiming for a public release in the next month or so.

That is correct, and it is called out in the README under Apps → iOS and in the Support section at the bottom. iOS needs a Mac, an iPhone, and a paid Apple Developer account, none of which I currently have. The Support section is where I mention that donations go toward exactly that. Apple Health sync specifically needs a native iOS wrapper since the data isn’t exposed to PWAs, so it has to wait on the same blocker. I hope to someday get this out to the community.

Nice work, exactly the kind of bridge that makes leaving MFP a lot less painful for self-hosters. Would you be OK with me linking the gist from the NutriTrace README (under Foods & Meals) and from inside the Bulk Food Import modal? Happy to credit it as your script with a link back to the gist.

Either way, thanks for putting it together.

Thank you so much! I appreciate it!

Yes! Settings → Backup → Nutrition Import. Built-in adapters for MyFitnessPal, Cronometer, LoseIt, and a generic CSV shape. Export your diary from MFP (it’s a CSV in their account settings), upload it, preview, commit. Skip / Merge / Replace per-date semantics, so you can re-import safely without overwriting.

Open Food Facts (OFF) for barcodes. Free, open license, community-edited. Their API: https://world.openfoodfacts.org/api/v2/product/<barcode>.json