Developer-onlyClip-AheadOfficial source

SlopTV

A self-hosted experiment turning YouTube chat into generated clips and a continuously replayed broadcast.

Access and release status are source-checked descriptions, not a live uptime check. A reachable website does not establish that video playback or interaction currently works.

No rights-cleared product preview yet. See the official page for its latest interface.

Published by Video Runtime · Source check 2026-09-05 · Evidence method · Suggest a correction

EDITORIAL VIEW

Editor's Verdict

Useful as a broadcast-pipeline reference, not proof that fresh video is generated as fast as it plays.

The author separates clip production from playback and reuses the clip pool to fill airtime.

How It Works

  • Chat prompts pass through a language model and local GPU workers; a separate process streams the completed clip pool.

What We Like

  • Generation and playback can restart separately, limiting disruption from a failed worker.

Current Limitations

  • The documented setup uses two RTX 5090 GPUs. No explicit repository licence was found in the inspected root; public visibility alone does not grant open-source rights.
  • We did not verify the linked YouTube broadcast's current uptime or reproduce the hardware results.

Pricing & Access

  • Budget for GPUs, electricity and any language-model service. Check code and model permissions before reuse.

Verification Summary

  • Official public sources reviewed on 2026-09-05. This is not a hands-on test or uptime guarantee; no paid generation was performed.
Technical notes & official performance

Official Performance Data

  • No comparable end-to-end performance measurement was verified for this listing.

Technical Notes

  • The implementation uses ComfyUI, a shared file pool and RTMP delivery. Author-reported generation throughput is not a site benchmark.

Sources

  1. Author repository and architecture ↗github · accessed 2026-09-05

Access, stage & mechanism

These are separate source-checked facts, not a live uptime monitor. Unverified fields are left open; transport and persistent sessions do not establish how frames are generated.

Release stage
Not verified
Access mode
Not verified
Source availability
Not verified
Transport
Not verified
Interaction
Not verified
Session mode
Not verified
Generation mechanism
Not verified
Continuity method
Not verified
Licence status
Not verified
Tasks
Not classified

Read how official-source and hands-on records stay separate in our Methodology.