docs(511): correct the stale "external logo URL can't drive the bug" claim + document the new limits #522

Closed
timothy wants to merge 1 commits from docs/511-external-logo-limits into main
1 Commits
Author SHA1 Message Date
timothy f014d31531 docs(511): correct the stale "external logo URL can't drive the bug" claim
Build ErsatzTV Image / CI image pin matches docker/ci (pull_request) Successful in 36s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 37s
Build ErsatzTV Image / Docs update reminder (pull_request) Successful in 44s
Build ErsatzTV Image / decisions.md append-only (pull_request) Successful in 42s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 1m23s
Build ErsatzTV Image / Functional E2E (curl contracts) (pull_request) Successful in 16m39s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 19m50s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 20m30s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Has been skipped
Found by sweeping the subject (external logo URL) while closing out #511,
not by reading the diff — docs/channels.md and the channel editor both
still documented the PRE-#502 behavior as a current limitation.

#502 fixed exactly this: an external-URL logo now passes through to the
graphics engine instead of being File.Exists-checked into oblivion. The
SPA help text was the user-visible half — it told operators to "upload an
image instead" for something that works today. No test pinned the string,
and the toggle was never actually disabled for external URLs, so this is
copy-only. The preview is still suppressed for external URLs, which
remains correct, so the new text says why.

Also documents #511's limits where an operator would look for them: the
10s deadline, 10 MiB wire cap, 3 redirects, 50 MP / 600 frame decode
budget and 200 MP retention budget, plus the practical effects (a
full-1080p animated overlay is limited to ~96 frames; an 8K still is
fine) and the fact that busting a limit disables the bug, never the
stream.

refs #511 #502
2026-07-21 02:01:43 +02:00