RESCENE ARCHIVE
In serviceOfficial content scattered across platforms, gathered into one timeline
Web service + admin console + mobile app · 2026 — Present
Overview
An archive service that collects official content spread across YouTube, TikTok, Instagram, and X into one chronological place. It offers a timeline, per-member pages, a schedule calendar, search, and user-built collections.
The product principles are enforced in code. Nothing is rehosted — links and oEmbed come first so storage stays minimal. Unverified rumour content is never surfaced. Browsing needs no account, and authentication is requested only when personalization requires it. Consent is granular, there are no dark patterns, and signup under age 14 is blocked.
Three surfaces — the public web, an admin back office on its own domain, and a mobile app — run from a single monorepo, in seven languages.
Engineering highlights
Document Picture-in-Picture player
To work around YouTube error 153, I built a small same-origin route that loads inside the PiP window instead of about:blank. Playback state is handed across, so closing the window resumes where you left off.
Designing name collisions out
SQL resources are isolated in a dedicated schema, and globally flat namespaces — scheduled jobs, storage buckets — carry mandatory prefixes. The rules are written down, so adding a resource needs no judgement call.
Production security headers
A production-only CSP that does not break dev HMR, HSTS preload, an allowlist for embed domains, form-action narrowed to the three OAuth providers, and a Permissions-Policy that disables camera, microphone, and geolocation.
Tooling built for operators
Not a CRUD table but a governance layer: an approval queue, a registry of ingest sources, an audit log, and an access log.
One token architecture, two platform themes
The Aurora palette ships from one package as CSS custom properties for web and typed constants for mobile, with mobile keeping its own light-glass variant.