The first Media over QUIC CDN: Cloudflare

Post by seany » Sat, Aug 23, 2025, 4:30 AM UTC

solardev wrote: post #82

barosl wrote: post #49

I tested the demo at https://moq.dev/publish/ and it's buttery as hell. Very impressive. Thanks for the great technology! Watching the Big Buck Bunny demo at https://moq.dev/watch/?name=bbb on my mobile phone leaves a lot of horizontal black lines. (Strangely, it is OK on my PC despite using the same Wi-Fi network.) Is it due to buffer size? Can I increase it client-side, or should it be done server-side? Also, thank…

Is it Chrome only? On Android Firefox it just says no browser support :(

Post by kixelated » Sat, Aug 23, 2025, 4:33 AM UTC

bushbaba wrote: post #87

kixelated wrote: post #48

Earlier quoted context omitted.

EDIT: Sorry I just noticed this was directed to Cloudflare. They're using the same architecture as Cloudflare Realtime, their WebRTC offering. `relay.moq.dev` currently uses GeoDNS to route to the closest edge. I'd like to use anycast like Cloudflare (and QUIC's preferred_address), but cloud offerings for anycast + UDP are limited. The relays nodes currently form a mesh network and gossip origins between themselves.…

Anycast can have serious reliability challenges. It was common at GCP for a small QPS user of anycast to have their Load Balancers nuked in a given pop as it was backed by a single machine. But BGP showed it as still the best route. The major DNS based offerings don't have such issues.

Post by nine_k » Sat, Aug 23, 2025, 6:19 AM UTC

Waterluvian wrote: post #78

kixelated wrote: post #57

Earlier quoted context omitted.

I am bad at CSS.

Managing aspect ratios in conjunction with managing a responsive page layout is one of the darker parts of CSS in my experience. You’re not alone.

Post by DaleCurtis » Sat, Aug 23, 2025, 6:50 AM UTC

kixelated wrote: post #89

chrismorgan wrote: post #86

Earlier quoted context omitted.

What’s that like for performance and power usage? I understand normal videos can generally be entirely hardware-accelerated so that the video doesn’t even touch the CPU, and are passed straight through to the compositor. I’m guessing with this you’re stuck with only accelerating individual frames, and there’ll be more back and forth so that resource usage will probably be a fair bit higher? An interesting and unpleas…

It's all hardware accelerated, assuming the VideoDecoder has hardware support for the codec. VideoFrame is available in WebGL and WebGPU as a texture or gpu-buffer. We're only rendering after a`requestAnimationFrame` callback so decoded frames may get automatically skipped based on the display frame rate. I don't think the performance would be any worse than the tag. The only exception would be browser bugs. It defin…

Post by riedel » Sat, Aug 23, 2025, 7:37 AM UTC

torginus wrote: post #26

englishm wrote: post #3

Hi! Cloudflare MoQ dev here, happy to answer questions! Thanks for the award, kixelated. xD

Hi! I have a few :) How close are we to having QUIC actually usable in browsers (meaning both browsers and infrastructure supports it, and it 'just works') How does QUIC get around the NAT problem? WebRTC requires STUN/TURN to get through full cone NAT, particularly the latter is problematic, since it requires a bunch of infra to run.