Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

tltv

Federation protocol for 24/7 TV channels

Details

External ID
48067612
Source
HN
Company
—
Product
tltv
Website domain
timelooptv.org
Launched
May 8, 2026
Cohort
—
Upvotes
6
Upvotes percentile
0.3053311793214863
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

I spent six years trying to build a tv channel server. rewrote it eight times. flask, fastapi, ffmpeg, gstreamer, named pipes. every version got more complicated and none of them worked right.turns out I was building the wrong thing. the thing I actually wanted was a protocol.so tltv is that. a channel is an ed25519 key pair. you sign your metadata with it. you serve hls video from wherever you want. your public key becomes a tltv:// address that anyone can tune into.relay nodes can re-serve your stream but they can't modify it. they verify signatures on everything. you can move servers and keep your channel because the key is the identity, not the hostname. nodes find each other through peer exchange. no central registry.the cli is probably the fastest way to see what I mean: curl -fsSL timelooptv.org/install | sh tltv keygen tltv server test --name "my channel" -k TV*.key that's a fully compliant origin server. pure go, generates smpte bars with audio, no ffmpeg. one binary, ~20mb of ram. there's also a full gstreamer-based server (cathode), a web viewer (phosphor), and bridge/relay servers in the cli. everything mit licensed.live demo at https://demo.timelooptv.orghttps://github.com/tltv-org

Enrichment

Theme
file transfer and sharing tools
Vertical
Media & entertainment
Function
—
Audience
B2B
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
federation protocol for tv channels
Manually corrected
False

Could you build this?

No Designing and deploying a decentralized federation protocol with cryptographic identity and resilient continuous video streaming requires deep distributed systems and media streaming engineering.

What it would actually take: The architecture requires an Ed25519-based cryptographic identity protocol, custom P2P or federated discovery/relay node routing, and a low-latency GStreamer/FFmpeg pipeline trans手游 (transmuxing) continuous linear streams into HLS/DASH. Achieving deterministic, non-drifting 24/7 video streaming across untrusted peers demands specialized distributed consensus and multimedia systems engineering.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one — 73 launches clear the similarity bar, closest 8 shown.

Attention rank: #62 of 74 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 172 days after the earliest competitor.

Other launches for this product