LinkCue

How the three-program system works
Back to Help

System Flow

LinkCue Manager ─────┐ │ Twitch Chat ─────────┼────► LinkCue Bot │ ├── Canonical Queue │ ├────► LinkCue Player │ └────► Public Queue
LinkCue Manager

The management console used to add, reorder, remove, and organize videos in the stream queue.

LinkCue Bot

The central authority. It owns the canonical queue, receives chat submissions, synchronizes clients, serves the API, and powers the public webpages.

LinkCue Player

The streamer's playback application. It receives queue state from the Bot while the streamer retains control over playback.

Public Queue

A read-only view of the Bot's current canonical queue. It can observe queue state but cannot control it.

Twitch Chat

Viewers can submit supported video links and use queue commands. Chat sends requests to the Bot, not directly to the Player.

Control Network Security

LinkCue uses a two-stage trust model for remote control. The streamer-defined Control Network Password establishes trust when a new client is paired. After successful pairing, the Bot issues a unique client credential for normal operation.

Streamer creates Control Password | v Player / Manager pairing request | v Bot validates control password | v Bot issues client credential | v Authenticated control communication
Control Password

A streamer-defined secret used during pairing. It authorizes new LinkCue clients but is not used for every command.

Client Credentials

Each paired Player or Manager receives its own identity after authorization.

Security Boundary

A downloaded copy of LinkCue cannot control a stream unless it is authorized through the streamer's pairing process.

Everybody talks through the Bot. The Bot owns the truth.