Highlights
Listening history from before the upgrade
v1.16.0 started recording listening sessions, so Activity began on the day you upgraded. On its first start, v1.17.0 fills in the time before that:
- From the apps' own history. The players have kept a record of each stretch of listening since June 2026, with real start and end times. Those become sessions, and appear in the day-by-day charts, the calendar and the time-of-day heatmap. The device and app weren't recorded, so the Sessions list shows them as Listening history.
- Estimated, for anything older (or books played offline): worked out from where each book was left. Estimates count in the totals and the top books, authors, narrators and listeners, but never in the day-by-day charts. Activity and Year in listening say how much of a period is estimated.
- Choose how long sessions keep their detail: Settings > General > Listening history, from 30 to 3650 days (400 by default,
AUDIOSILO_SESSION_DAYS). After that a session is added into daily totals per person and book, which Activity keeps.
Notifications
- Server > Events lists every event of the last 90 days, newest first, with a filter by kind. The bell gains a See all link to it.
- "Someone signed in" is announced once per browser. Signing in to the admin console again from the same browser no longer fires a new sign-in notification each time; a sign-in from any other browser still does, yours included. If you sign a browser out from People > Devices, change someone's password or disable their account, that person's browsers are forgotten and their next sign-in is announced again.
A faster console
- Console files are gzipped and revalidated: the main bundle drops from 660 KB to 208 KB, and pages you've loaded before come back as "not modified".
- Fix: opening the console in a new browser could hit "too many requests" errors and, now and then, a page that failed to load. A first visit loads around 40 files at once, more than the per-address limit allowed. Static files no longer count toward it; the API still does.
Before you upgrade
- Back up your data directory. This release adds two database migrations (0020 and 0021), which run automatically on first start. 0021 fills in the listening history above, once; on a large library it can add a few seconds to that first start.
- One "new sign-in" per browser after upgrading. Browsers aren't known yet, so the first sign-in from each one after the upgrade is announced once.
- Changing your own password forgets your browsers too, so your next sign-in is announced once.
Other changes
- Fix: a library whose root folder is a symlink (a NAS mount linked into place) indexed no books. It is indexed now.
- Fix: Check now during the daily update check answered with the old result. It now waits for that check.
- Fix: a settings change could save a config.yaml that only worked while an
AUDIOSILO_*variable stayed set. Such a change is refused, naming the variable. - Backups: the scheduler no longer lists the backups folder every minute, which matters when
backups.diris on a NAS. - Fewer database writes: a device's "last seen" is written at most once a minute (unless its address or app changes), so it can lag by up to a minute.
- Notifications: a refused destination field is explained in the console's language.
- People: a person's Devices tab counts their devices only, as their card does, and lists their API keys separately.
The player API is unchanged, and every server-side change is additive, so existing iOS, Android and web players keep working.
Admin guides:
- Activity: https://docs.audiosilo.app/users/admin/activity
- Notifications: https://docs.audiosilo.app/users/admin/notifications
- Server: https://docs.audiosilo.app/users/admin/server
- People and devices: https://docs.audiosilo.app/users/admin/users-and-invites
Native builds embed the web player; ffmpeg/ffprobe are found locally or
auto-downloaded on first use. Prefer Docker for advanced / multi-user
setups: ghcr.io/kodestar/audiosilo-server.