Real streaming platforms protect video the same two ways this model shows:
1. DRM license handshake
client -> license server: device cert + content id
server -> client: encrypted key, valid for TTL seconds
(segments cannot be decrypted without a live token)
2. Signed, time-limited CDN URLs
url = edge/segment?exp=now+TTL&sig=HMAC(path,exp,secret)
edge node checks: now <= exp AND sig matches
-> expired or forged signatures are rejected at the edge
The legit client (white core, left) must hold a valid token before it can pull a segment from any CDN edge node (the ring). When the token's countdown reaches zero, the next request forces a fresh handshake with the license server (center) before streaming resumes — exactly like a real DRM key rotation.
Bot traffic (red sparks) skips the handshake and hammers edge nodes directly at high, bursty rates. The anomaly detector keeps a rolling request-rate window per edge node:
rate(edge) = requests in last 2s / 2
flag as bot if rate(edge) > 3 x rate(legit client)
Flagged sources are quarantined at the edge (node flashes red, request rejected) instead of reaching the client — this is the same rate-based heuristic real CDN bot-management layers (Akamai, CloudFront, Cloudflare) use before falling back to fingerprinting or CAPTCHA challenges. Toggle detection off to see unfiltered bot traffic reach the client unchecked.
Fix vs. the 3D original: the source engine's bot-rate formula scaled the "bot traffic injection %" slider by a stray extra ×2.2 factor, so a "20%" setting actually injected ~36% of total traffic and "50%" injected ~69% (verified numerically). This 2D build drops that factor so bot / (legit + bot) now matches the slider's own label.
The ring view is an orbit stand-in for the 3D scene's camera: drag horizontally to rotate it, drag vertically to tilt the ellipse from top-down to edge-on, and scroll to zoom.