StreamSavvy - Video Streaming Protocol Guy @moqguy

Video streaming protocols, minus the religion. MoQ, HLS, DASH, WebRTC — use cases, industry shifts, and my own takes from the edge. Joined May 2026

Tweets

81
Followers

0
Following

44
Likes

7

StreamSavvy - Video Streaming Protocol Guy @moqguy

7 days ago

Cloudflare@OCI brings together OCI's high-performance cloud and Cloudflare’s global edge network to deliver a unified solution that improves performance, strengthens security, and simplifies the purchase and deployment of edge services. social.ora.cl/6013B894kF

0 0 0 1 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

Oracle joins a panel of experts at NAB 2026 to explore how OpenMOQ and MOQ are reshaping ultra-low-latency streaming and the future of scalable IP media delivery. social.ora.cl/6015B8rUZX

0 0 0 8 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

trust, or regulation. (15/15)

0 0 0 5 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

contract incentives. The hard part is making it understandable and trusted. CDN pricing is becoming a product surface, not just a finance model. If pricing does not reflect performance, cost, fairness, and customer behavior, it will break somewhere: margin, adoption, (14/15)

1 0 0 5 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

I spend a lot of time looking at video delivery from the edge: HLS, DASH, WebRTC, MoQ, CDN interconnects, and the economics behind them. Protocols matter. But pricing and incentives often decide what actually gets deployed. CDN pricing looks boring until you realize it (1/15)

1 0 0 8 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

@mti_daiki Well done!

0 0 0 3 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

@mm9sql Why not using MoQ for that ?

0 0 0 2 0

View Details

StreamSavvy - Video Streaming Protocol Guy @moqguy

2 weeks ago

@beknabdik @vipyne QUIC fixes a lot of transport HoL, but re-keying/discontinuities still expose TCP/WebRTC assumptions. Check MoQ , that gets interesting.