Send your logs to the developer in one click. Reporting a problem with Letterboxd Sync used to mean digging through Jellyfin's log files and pasting the right lines into a GitHub issue. This release adds a "Send logs to developer" button to the Logs tab that does it for you.
What it does
- Click the button and the plugin bundles your recent Letterboxd Sync log lines (the same ones already shown on the Logs tab) and uploads them privately, then hands you a short reference code like
LBX-7Q2F9K. Quote that code when you open a GitHub issue and the developer can pull your exact logs, no more copy-pasting walls of text. - A confirmation step lets you preview exactly what will be sent (the real log lines and a telemetry snapshot, byte-for-byte what gets uploaded) and add a short note describing what went wrong.
Privacy, stated plainly
- Unlike the anonymous weekly telemetry from 1.16.0, logs are not anonymous: they can contain your Letterboxd username or film titles, and the bundle is linked to your install's telemetry ID. The dialog says this before you send, nothing leaves your server until you confirm, and passwords, cookies, and auth tokens are never logged.
- Works whether or not you have anonymous telemetry enabled. Uploaded bundles are stored privately and auto-deleted after 90 days.
Also in this release
- Stronger log access control: the plugin's log endpoint now requires administrator access. Previously any signed-in Jellyfin user could read the Letterboxd Sync logs (which name every linked Letterboxd account and watched film); on shared or family servers this is now admin-only.
- Better diagnostics when you do send logs: full multi-line error traces are captured intact (they were previously fragmented), log text is cleaned of stray terminal control codes, and the bundle always records your Jellyfin version.
Nothing changes unless you choose to use the new button.