StreamPulse

Live studio with connection diagnostics and a rehearsal poll; displayed votes are explicitly labelled as simulated.

Inspiration

Live participation loses value when an overlay silently stops updating. StreamPulse combines audience polls with connection visibility, drawing on our networking, telecommunications and software background.

What it does

Creators launch a question with 2–4 answers. Twitch viewers type !vote 1 through !vote 4, and an OBS browser overlay updates live. Each viewer gets one changeable vote. The studio shows Twitch connection state, connected app clients and browser-to-server round-trip time.

How we built it

Built with OpenAI Codex, Node.js, ws, Twitch IRC-over-WebSocket and browser HTML/CSS/JavaScript. Codex helped implement the poll model, server, reconnection handling, interface and automated tests.

Challenges and what we learned

We separated application RTT from Twitch video latency and used explicit connection states rather than implying a video-quality measurement. Vote deduplication, vote changes, bounded reconnect backoff and private creator controls are core parts of the design.

Validation and next steps

Automated tests cover poll correctness, input validation, HTTP authorization, live WebSocket state broadcasts and heartbeat round trips. Real Twitch chat votes, vote changes and closed-poll rejection were verified on asiyaali08. We broadcast the browser overlay live at 720p through FFmpeg and captured actual Twitch playback for the demo. The demo includes a source walkthrough explaining how Codex was used; direct Codex-app recording was unavailable. Poll data is in memory and resets on restart.