Mediawan
A study of media-server architecture: a single Node process serving an SPA, session auth, an admin panel, cached AniList metadata, source resolution, per-device delivery decisions (direct play vs. remux vs. transcode), and a thin media proxy — with a companion Samsung Tizen TV app. Published for educational purposes; ships no content, indexes or credentials.
* Educational / research project. No content is hosted or distributed; every source is opt-in.
focus
Delivery engineering: probing what the requesting device can actually decode, copying streams whenever possible, and treating an unnecessary lossy transcode as a regression. Independent backends fail over instead of failing the request.
milestones
01
Capability probing + per-track remux/transcode sessions with ffmpeg; direct play preferred
02
Tiered source ranking with a quality floor; provider chain that moves on when one is down or rate-limited
03
Security layer: headers, rate limiting, SSRF guards, signed media tokens; SQLite via node:sqlite
04
Browser UI and a separate TV-optimised UI packaged as a Tizen app
05
node:test suites, Docker Compose deployment path, diagnostic scripts