jozamudi d60524815f hls.js: put retry budget where 1.5.x actually reads it ...

maxNumRetry was set at the top of the load policy, which hls.js 1.5.x
ignores — it reads the budget from the errorRetry/timeoutRetry
sub-objects. Net effect before: a fragment-load *timeout* (a CDN that
starts sending then stalls) got only the default 1 retry before fatal
fragLoadTimeOut.

Now (verified resolved in-browser):
  maxTimeToFirstByteMs 15s   first byte
  maxLoadTimeMs        30s   total load (finite -> stalls time out)
  timeoutRetry.maxNumRetry 6  was 1
  errorRetry.maxNumRetry   8  our proxy's 502 path

2026-08-31 01:22:22 +00:00

..

app.js

hls.js: put retry budget where 1.5.x actually reads it

2026-08-31 01:22:22 +00:00

hls.min.js

fix playback: vendor hls.js locally, surface stream/API errors visibly

2026-08-19 15:13:51 +00:00

index.html

UI/UX polish: a11y, player controls, undo, stats ranges

2026-08-30 20:53:55 +00:00

login.html

ui: loading states, player failure overlay + retry, toasts, back nav, full history page with delete

2026-08-19 18:20:42 +00:00

style.css

Intro skip: MAL timings via keyless Jikan + player button

2026-08-30 21:01:24 +00:00