Home

Playback Statistics

A Jellyfin plugin that records what was played on a server and keeps it private to the person it is about.

The server writes one row per finished play into a SQLite file of its own: which account played which item, when it started and stopped, how much was watched, whether it reached the end, the client and the device it played on, and whether the server had to transcode and why. Nothing is sent anywhere. No network address, no user agent and no library file path is kept.

A signed-in person reads their own figures, their own year and their own consent, and deletes their own history. An administrator reads the server-wide reports, which name nobody. The one exception is the server's year in review, where an account is named only if that account itself recorded its agreement to be named. No route hands one account another account's rows, and an administrator is refused there like anybody else.

Status

In-Development, the first rung of the maturity ladder (In-Development, Alpha, Beta, Release Candidate, Full Release).

One release exists, 0.1.0.0 on the Jellyfin 10.11 line. The Jellyfin 12.0 line has published nothing. What that release does and what is wrong with it is in CHANGELOG.md, and Support matrix and releases says which server each line runs on.

No statistics page is drawn in the dashboard yet. The views are built, and they are not declared to the server until the plugin serves their code itself. Pages says what is coming and when.

Pages here

• Installation - the address, the catalogue, the restart, upgrading, uninstalling and what removal deletes.
• Pages - every view, what it shows, its three states, and where it is found.
• Configuration - the eight settings, the two retention windows, and which deletion is terminal.
• What is stored and who can read it - the tables, the readers, and the absences.
• Privacy, consent and deletion - the wording, what agreeing changes, and how a person deletes their history.
• Transcode reasons - why the reason counts exceed the plays.
• Support matrix and releases - the two server lines, the floors, the version streams, and how to verify a release asset.
• Troubleshooting - the log lines, the settings-page sentences, and what a refused save looks like.
• Release process - for whoever cuts a release.

Where a page here summarises a document in the repository, the document is linked from it and is the one the test suite reads. If the two disagree, the repository wins.