Repository navigation
Releases
Kilo Tracker 1.5.0
Kilo now knows where you are heading: set a goal weight and the dashboard shows how far it still is and roughly when you can reach it at your current pace. This release has a database migration, which runs by itself when the app starts.
What's new
- A goal weight. Under Settings you can set an optional goal weight. The chart shows it as a dashed line, and the axis stretches to include it.
- How far, and roughly when. The Current average box shows the goal and how many kilos are still to go. Hover over the box, tap it or tab to it to see when the goal can be reached. The estimate follows the change in your moving average over the last Goal date trend days (30 by default, set next to the goal). The chart's tooltip shows the same estimate under the goal.
- Honest about the estimate. No date is given when the trend is flat or heads the other way, when the goal would take more than five years, or while there are fewer days of data than the trend needs. Once your average passes the goal, the box says the goal is reached.
- Colours that follow your goal. With a goal set, the change boxes are green when they move towards it, whether you want to lose weight or gain it. Without a goal they work as before.
- On your public chart, if you want. A new Show my goal switch adds the goal to your public chart. It is off by default and needs Show my weight to be on.
- An About link on the public chart. The header of the public chart now links to the About page, on the right. It opens in a new tab, so a chart shown on another site stays where it is.
Translations
- The 11 new texts are machine-translated in all 14 languages. Corrections from native speakers are welcome (see TRANSLATING.md).
Self-hosting
- A new fail2ban jail,
kilo-probe. It bans an address for a day at its first request for a PHP, WordPress, phpMyAdmin, CGI or XML-RPC page, which Kilo never has. Scanners send their whole list within seconds, sokilo-notfoundbanned them only after they had finished. To use it, installdeploy/fail2ban/filter.d/kilo-probe.confand the updateddeploy/fail2ban/jail.d/kilo.local, then reload fail2ban. - The example logrotate rule explains how to keep every old log instead of 8 weeks.
- CI now also runs the tests on Python 3.15. The development tools were updated: pytest 9.2, coverage 7.17, Playwright 1.64.1 and ruff 0.17.3.
Upgrading
This release has a migration (0004: four new columns on the user table). It runs by itself when the app starts. Existing accounts get no goal, so nothing changes for them until they set one. There are no new requirements.
- Back up the database first, for example
sqlite3 instance/weight.db ".backup weight-before-1.5.0.db". git pull.pybabel compile -d translations(new texts in every language).- Restart the app.
Afterwards the About page shows v1.5.0, and sqlite3 instance/weight.db "SELECT * FROM alembic_version" shows 0004.
Full changelog: v1.4.0...v1.5.0
Kilo Tracker 1.4.0
Kilo now tells visitors and search engines what it is. The front page explains Kilo below the sign-in form, every language has its own address for search engines, and a shared link shows a preview. Pages also load faster on a second visit. No database changes and no new requirements.
What's new
- A front page that explains Kilo. Below the sign-in form there is now a short introduction: the moving average, the chart, quick entry, importing from The Hacker's Diet Online and Yet Another Diet Tool, sharing your chart, and how Kilo keeps your data private, with the video tutorial. The sign-in box itself got simpler: its "How does this work?" link is gone, and the new text ends with a link to the About page instead.
- Link previews. A link to Kilo shared in a chat or on social media now shows a title, a short description and a picture of the chart.
- Faster pages. Browsers now keep Kilo's style sheet, scripts and icons for up to a year instead of checking each file again on every page. After an update the addresses change, so you never get an old file.
Search engines
- The front page has a real title ("Kilo Tracker — Free weight tracker with a moving average") and, with the About page, a description for search results.
- Each language has its own address (
/?lang=nl,/about?lang=de, ...), withhreflangand canonical links, so search engines can find all 15 languages instead of only English. /sitemap.xmllists those addresses, androbots.txtpoints to it.- The sign-up, code, remove-data and error pages ask not to be indexed. Public charts stay out of search engines, as before.
- Picking a language in the menu after arriving on a
?lang=address now switches the language as expected.
Translations
- Swedish: a follow-up from @loneicewolf (#14): "den" instead of "dem", "Videoguide" for the video tutorial, and "min data" on the remaining buttons.
- The 11 new texts are machine-translated in all 14 languages; corrections from native speakers are welcome (see TRANSLATING.md).
Self-hosting
- The sitemap,
robots.txtand the link previews need full addresses. Behind a reverse proxy, keep passing theHostandX-Forwarded-Protoheaders (as in the README's examples): gunicorn trustsX-Forwarded-Protofrom a proxy on the same machine, so the addresses start withhttps://. - CI now tests on Python 3.14.
Upgrading
No migrations and no new requirements. After git pull:
pybabel compile -d translations(new texts in every language);- restart the app.
Afterwards, the About page shows v1.4.0.
Full changelog: v1.3.1...v1.4.0
Kilo Tracker 1.3.1
Swedish has been reviewed by a native speaker, and every page now sends three more security headers. No database changes, no new strings, no new requirements.
Translations
- Swedish reviewed by @loneicewolf (#19). Thank you!
That makes seven reviewed languages: Dutch, German, Italian, Finnish, Indonesian, Spanish and Swedish. French, Brazilian Portuguese, Polish, Romanian, Hungarian, Danish and Norwegian Bokmål still welcome a review: see TRANSLATING.md and the open issues.
Security
Every response, shared public charts included, now also sends:
X-Content-Type-Options: nosniff: the browser treats a file as the type the server says it is and never guesses, so a text file can never run as a script.Referrer-Policy: same-origin: sites Kilo links to (the video tutorial, GitHub) no longer learn which Kilo page you came from. Kilo's own pages still get the address, which it needs to send you back to the right page after an expired form.Permissions-Policy: camera, microphone, location, payment, USB and the browser's ad-interest topics are switched off. Kilo uses none of them, and a site that embeds a public chart cannot ask for them through it either.
Upgrading
No migrations and no new requirements. After git pull:
pybabel compile -d translations(the Swedish catalog changed);- restart the app.
Afterwards, the About page shows v1.3.1.
Full changelog: v1.3.0...v1.3.1
Kilo Tracker 1.3.0
Kilo can now be installed on your phone, and your email address no longer travels readable in the sign-in cookie. Plus two accessibility fixes. No database changes, no new strings; one new requirement.
Changes
- Install Kilo on your phone. Kilo now has a web app manifest and app icons. On Android, Chrome offers "Install app" / "Add to Home screen"; on an iPhone use Share → "Add to Home Screen". Kilo then opens from its own icon, in its own window without the address bar. The browser bar takes the colour of the header and follows dark mode. Shared public charts are not offered as an app.
- Your address is encrypted in the sign-in cookie. Kilo stores only a hash of your email address, but the pages need the address itself (the header, printing, the export's file name, the code for removing your data). It lived readable in the signed sign-in cookie; it is now encrypted there, so someone who sees the cookie cannot read it. The "We sent a code to …" notices no longer pass through the cookie either. Nothing changes in what you see, and nobody is signed out.
- Readable notices. The green and red notices (such as "Signed out." and error messages) now have text dark enough to read in both themes: 5.2:1 and 5.6:1. They were 4.25:1 in the light theme and about 2:1 in dark mode, while WCAG asks for at least 4.5:1.
- Range buttons for voice control. A screen reader now says the visible label first, then its meaning ("3M, 3 months"), so saying "click 3M" works with voice control (WCAG 2.5.3). Hovering a range button shows "3 months" as a tooltip.
- A favicon at
/favicon.ico. Browsers, bookmarks and feed readers that ask for it get the Kilo icon instead of an error.
Self-hosting
- New requirement:
cryptography, for the encrypted address. The key is derived fromSECRET_KEY; there is no new setting. - The example logrotate rule (
deploy/logrotate/kilo-gunicorn) now covers only/var/log/gunicorn/kilo*.log, so it leaves other apps' logs in that folder alone.
Development
- The accessibility checks now include axe-core's experimental label-in-name rule, which caught the range buttons.
- A browser test asks Chromium itself whether Kilo is installable.
Upgrading
No migrations and no new strings. After git pull:
pip install -U -r requirements.txt(installscryptography);- restart the app.
Afterwards, the About page shows v1.3.0.
Full changelog: v1.2.3...v1.3.0
Kilo Tracker 1.2.3
An accessibility release: Kilo now works much better with a screen reader and the keyboard, and the buttons are readable in dark mode. No database changes.
Changes
- The chart in words. A screen reader now reads the chart as "Weight chart" with a description of what it shows, for example: "1 week: from 80.1 kg on October 20, 2026 to 80.2 kg on October 27, 2026. Lowest 80.0 kg, highest 80.2 kg, average 80.1 kg." It follows the range buttons and every save. On a public chart with the weights hidden it only says which way the line goes, so no number is given away.
- A daily log that says which day is which. Each day's weight field and note button are named after their date, with the month spelled out so it is read as a word ("Weight on October 24, 2026"), also for the older days loaded while scrolling. The chart description and the Undo notice spell the month out too.
- Range buttons a screen reader understands. The selected range is announced as selected, and the letters are read as words ("3M" is "3 months", in each language).
- Real dialogs. "Log today's weight?", "Unusual value" and "Session expired" are now proper dialogs: they are announced with their title, the keyboard stays inside while one is open, and focus goes back where it was when it closes. Escape works as before.
- Skip links. The first Tab on every page offers "Skip to main content"; on the dashboard "Skip to the daily log", past the chart and the numbers.
- Less motion on request. When your system asks for reduced motion, Kilo drops its fades and smooth scrolling.
- A quicker emoji panel for the keyboard. It is one Tab stop instead of about 60; the arrow keys, Home and End move inside it, and Escape closes just the panel.
- Readable buttons in dark mode. The green and red buttons now have dark text in dark mode. White on the dark theme's green and red was too faint (2.3:1 and 2.5:1); it is now about 7:1, well above the 4.5:1 that WCAG asks.
- A visible keyboard focus on the stat boxes.
Translations
There are 13 new strings (the chart description, the day labels, the spoken range names and the skip links). They are machine-translated in all 14 languages and marked for review; reviews are welcome, see TRANSLATING.md.
Development
- Automatic accessibility checks. The browser tests now run axe-core on every page, and on the dashboard with its dialogs, note editor and menus open, in the light and the dark theme. Its one finding, a missing level-one heading, is fixed: the header logo is now the page's heading. This adds
axe-playwright-pythontorequirements-e2e.txt(browser tests only).
Upgrading
No migrations and no new requirements. After git pull:
pybabel compile -d translations(new strings);- restart the app.
Afterwards, the About page shows v1.2.3.
Full changelog: v1.2.2...v1.2.3
Kilo Tracker 1.2.2
A small release: the About page now links to a video tutorial. No database changes.
Changes
- Video tutorial. The About page has a new "Video tutorial" section with a still from the video that links to the 13-minute tutorial on YouTube: signing in, logging your weight, importing your history, the chart, sharing it and taking your data with you. The video is not embedded, so nothing is loaded from YouTube until you click.
Translations
The three new strings are machine-translated in all 14 languages and marked for review, so the reviewed languages show a few entries to check again.
Upgrading
No migrations and no new requirements. After git pull:
pybabel compile -d translations(new strings);- restart the app.
Afterwards, the About page shows v1.2.2.
Full changelog: v1.2.1...v1.2.2
Kilo Tracker 1.2.1
A fresher look, five more translations reviewed by native speakers, and a few small improvements. No database changes.
Changes
- A fresher look. A slightly brighter green, still dark enough for readable white text (WCAG AA contrast), rounded corners and a soft shadow on the boxes, the range buttons on a rounded bar, and a tidier account menu: "Language" and its menu on one line, the dark-mode switch at the right edge.
- The daily log is as wide as the chart on tablets and narrow windows (721–1000 px wide), instead of a narrower column in the middle.
- Every section of the settings and About pages has a back arrow to the dashboard, not only the first one, so a long page on a phone no longer means scrolling all the way up.
- A printed report shows whose weight it is: the account's avatar and address are printed at the top right, opposite the logo.
- The code page matches the sign-in page: the code field takes the width and the Verify button sits next to it at its own size, like the address field and Send code. The "Remove my data" confirmation step uses the same layout.
- The export's file name includes the account's address, e.g.
kilo-tracker-export-you@example.com-2026-10-21.csv, so exports of different accounts are easy to tell apart. Characters that are unsafe in a file name become_. - New contact address on the About page: ramon@11tools.com.
Translations
Reviewed by native speakers. Thank you all!
- German by Laurence de Vries (#6)
- Italian by @mrCabez (#18)
- Indonesian by @liketocoode (#17)
- Spanish by Brechtje de Vries (#4)
- Dutch by the maintainer
That makes six reviewed languages, with Finnish. The others (French, Brazilian Portuguese, Polish, Romanian, Hungarian, Danish, Swedish and Norwegian Bokmål) still welcome a review: see TRANSLATING.md and the open issues.
Development
- The dashboard script moved out of the page into two static files,
dashboard-chart.js(also used by the public chart) anddashboard-log.js(the dashboard only), so browsers can cache it. Their addresses carry the file's modification time, so after a deploy a browser never runs an old script with a new page. - Smaller pieces: the chart statistics moved to
app/overview.py, the per-request session code toapp/sessions.py, and several long functions were split up (the Hacker's Diet parsers, the avatar cache, saving and clearing a day, the import messages, the catalog checks).tests/test_routes.pywas split into test files by subject. Nothing visible changes.
Upgrading
No migrations and no new requirements. After git pull:
pybabel compile -d translations(several translations changed);- restart the app.
Afterwards, the About page shows v1.2.1.
Full changelog: v1.2.0...v1.2.1
Kilo Tracker 1.2.0
The public chart gets a look of its own, a few fixes, a native-speaker review of the Finnish translation, and a much larger test suite.
New
- The public chart keeps its own theme and range. In Settings → Public chart, the "Dark mode" switch and the "Chart range" menu are now saved with the page's other settings. Before, they only rewrote the link. Without
?theme=or?range=in its address, the public page uses these saved settings, so switching your own dark mode no longer changes how your public chart looks. The link and the embed code always include?theme=lightor?theme=dark, plus&range=…when a range is chosen. An address that already has them still takes precedence, so existing embeds keep working. After the upgrade, every existing public chart starts with its owner's current dark mode, so none changes how it looks.
Fixes
- The public chart's link on the settings page now wraps onto the next line, instead of running past the edge of the card.
- Saving a weight, switching dark mode and choosing a chart range no longer give a server error (500) when the request is malformed: a JSON body that isn't an object, or a date or range that isn't text. They now answer "Invalid request.", "Invalid date." or "Invalid range." and change nothing. Only a signed-in user with a valid form token could send such a request.
- A weight sent as a JSON number is now checked the same way as typed text.
true,NaN,Infinityand negative numbers are refused;trueused to be saved as 1 kg. The dashboard always sends text, so this only affects other clients.
Translations
- Finnish was reviewed by a native speaker, @camille-neonilla (#16). Thank you!
- One new message, "Invalid request.", is machine-translated into all 14 languages. In Finnish, that one entry is marked for review again.
Development
- Browser tests. The dashboard and the public chart are now tested in a real Chromium with Playwright, in
tests/e2e/. The tests cover saving a day, the question about an unusual weight, Undo, the note editor, the "today" prompt, the range buttons, dark mode and the session-expired dialog. They fail on any JavaScript error or Content-Security-Policy violation. They are optional (requirements-e2e.txt, thenpytest -m e2e) and run in a CI job of their own. - Coverage in CI.
coverageis now inrequirements-dev.txt. CI reports branch coverage (97 %) and fails below 95 %. - A faster, broader test suite. It runs in about 80 seconds instead of three minutes, because the tests hash sign-in codes cheaply while production keeps scrypt. New tests check that every page except the public ones needs a sign-in, along with the chart calculations, the database query counts and many error paths.
- Less duplicated code. A code-duplication audit and a complexity audit led to shared helpers: the emailed codes in one module (
app/codes.py), shared form templates, and common import and height functions. Nothing visible changes.
Upgrading
Make a backup of the database first. On the first start, two new migrations run automatically:
0002adds the public chart's theme, copied from each user's current dark mode;0003adds its saved range.
Then, after git pull:
pip install -U -r requirements.txt(the requirements haven't changed since 1.1.4);pybabel compile -d translations(there is a new message);- restart the app.
Afterwards, the About page shows v1.2.0, and SELECT * FROM alembic_version gives 0003.
Full changelog: v1.1.4...v1.2.0
Kilo Tracker 1.1.4
A maintenance release: database migrations, automated checks and dependency updates. Nothing changes for visitors.
Self-hosting
- Database migrations with Alembic. The schema is now managed by Alembic (through Flask-Migrate), with the migrations in
migrations/versions/. The app applies the ones your database hasn't had yet at every start, under a lock so two processes never migrate at once, so updating needs no extra step. The first migration brings any existing database, however old, to the current schema without touching its data; on an up-to-date database it only adds Alembic'salembic_versiontable. Future changes such as renames and type changes are now possible on SQLite. See "Database migrations" in the README for how to write one. - Newer minimum versions. Flask 3.1.3, Flask-SQLAlchemy 3.1.1, Flask-WTF 1.3.0, email-validator 2.3.0 and dnspython 2.9.0 are now the minimums, plus the new Flask-Migrate 4.1.0.
Development
- CI on GitHub Actions: every push and pull request runs the tests on Python 3.12 and 3.14, and ruff.
- Ruff settings in the repository (
ruff.toml), with the deliberate exceptions listed and explained; the code passes them. - Dependabot proposes newer Python packages and GitHub Actions once a month, in one grouped pull request each, and CI checks every proposal.
Upgrading
Make a backup first (the first start adds the alembic_version table). Then, after git pull: pip install -U -r requirements.txt (installs Flask-Migrate and Alembic), pybabel compile -d translations, and restart the app.
Full changelog: v1.1.3...v1.1.4
Kilo Tracker 1.1.3
A language menu, an Undo for removed weights, and more control over the public chart.
New
- Language menu. Pick your language in the header (signed out) or at the top of the account menu (signed in). The menu lists your browser's languages first, then English, then the rest alphabetically, each in its own name. Your choice is remembered for a year in this browser; "Browser language" goes back to automatic.
- Undo after removing a weight. Clearing a weight in the daily log deletes it right away; now a notice "Weight of … removed. Undo" stays for 8 seconds and brings back the weight and its note. The note icon of the row now also shows when the note is gone.
- Public chart without your weight. Switch off Show my weight to share only the shape of your line: no kilograms, no BMI, no stat boxes. The server rescales the weights to 0–100 and leaves out your height and BMI, so the kilograms aren't even in the page source. The stat boxes can only be switched on while the weight is shown.
- A fixed range in the embed code. Add
?range=3m(or1w,1y,all, …) to your public chart's address to show just that period, without range buttons. The new Chart range menu in the settings puts it in the link and the<iframe>code for you. - Light or dark embed. A Dark mode switch above the chart range puts
?theme=lightor?theme=darkin the link and the embed code, so your chart matches the site it sits on and keeps that look even if you change your own theme later.
Also
- A tidier Settings page. Every button now sits at the right of its section, the public chart's Save comes last, and Sign out on other devices is amber: green for routine actions, amber for this one, red for removing your data.
- The README now says it plainly: Kilo is metric only, and will stay that way.
- All new texts are translated into the 15 languages.
Upgrading
After git pull: pip install -U -r requirements.txt, pybabel compile -d translations (new strings), then restart the app. A new user column (public_show_weight) is added automatically at startup. Existing public charts keep showing the weight.
Full changelog: v1.1.2...v1.1.3