amber-backend/pb_hooks
Claude 73a86d3e23 Show which provider's bytes were slow
Added beside the upstream panel and for the same reason: the owner reported
anime stuttering and it took an evening of measurement to establish that the
television was fine and TorBox's CDN had dipped to 5.5 Mbps. That is a question
a dashboard should answer in a glance.

Median rather than mean, because one fast session should not hide ten slow ones,
and the share of watched time spent waiting alongside it, because that is the
number that matches what the viewer actually felt.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-07 22:26:28 +02:00
..
client_logs.pb.js Add client_logs collection for background device diagnostics (feedback 2 §4) 2026-07-23 11:49:04 +02:00
device_auth.pb.js fix(device-auth): inline helpers into each hook handler (JSVM scope) 2026-07-19 19:48:03 +02:00
device_page.pb.js device approve page: manual code-entry for the QR-less path (#55) 2026-07-20 11:06:51 +02:00
onboarding.pb.js The code has to choose the template, not the clock 2026-08-12 21:35:46 +02:00
profile_pin.pb.js Add /api/amber/set-pin: hidden pinHash rejects client writes (#13/#14) 2026-07-21 21:29:02 +02:00
status.pb.js Show which provider's bytes were slow 2026-09-07 22:26:28 +02:00
update.pb.js Stop choosing an update variant, and drop the 18+ controls 2026-08-30 04:09:10 +02:00
web.pb.js Shadow the stale pb_public pages the deploy leaves behind 2026-08-07 02:13:31 +02:00
whoami.pb.js Stop choosing an update variant, and drop the 18+ controls 2026-08-30 04:09:10 +02:00