englishm

5 ms·

1.
by englishm 2mo ago
TL;DR: - API for self-service MoQ relay provisioning. - simple scope-granularity rw/ro auth (plans for more advanced auth as standards mature). - globally deployed draft-16 support (draft-18 work already underway). - SUBSCRIBE_NAMESPAC
2.
An API for MoQ: provision your own isolated relays(blog.cloudflare.com)
8 points by englishm 2mo ago|1 comments
3.
An Exercise in Agentic Coding: AV1 Encoder from Scratch in Rust(caricio.com)
1 points by englishm 7mo ago|0 comments
4.
by englishm 1y ago
Yes, you certainly could use MoQ to send multiple streams (WebRTC simulcast style). There are implementations of traditional receiver-side adaptive bitrate switching with MoQ already today (mostly switching between tracks at group boundarie
5.
by englishm 1y ago
Yes, Safari's WebTransport implementation is still a work in progress.
6.
by englishm 1y ago
Safari is still working to add full support for WebTransport.
7.
by englishm 1y ago
Good question! I can't speak concretely to our plans for optimizations at that level of the stack at this stage, but it's true that speaking broadly QUIC does currently lag behind some of the performance optimizations that TCP has
8.
by englishm 1y ago
I plan to cover more of the internal implementation details at a future date, possibly at a conference this fall.. But I can at least say that we use anycast to route to a network-proximal colo.
9.
by englishm 1y ago
Looks like it might be a happy eyeballs issue? I'll pass it along to folks who would know more about what that might be, thanks.
10.
by englishm 1y ago
Thank you dang!
11.
by englishm 1y ago
Synchronized playback is usually primarily a player responsibility, not something you should (solely) rely on your transport to provide. We have had some talk about extensions to allow for synchronizing multiple tracks by group boundaries a
12.
by englishm 1y ago
QUIC is already quite widely used! We see close to 10% of HTTP requests using HTTP/3: https://radar.cloudflare.com/adoption-and-usage As for the NAT problem, that's mainly an issue for peer-to-peer scenarios. If y
13.
by englishm 1y ago
So... MoQ represents a bit of a moving away from the all-in-one "black box" of web APIs like WebRTC. From the browser perspective, the main thing that matters is the WebTransport API. Using MoQT in conjunction with that WebTranspo
14.
by englishm 1y ago
Yes, exactly! I mention that in the post. Streaming formats are where a lot of interesting decisions can be made about how best to optimize QoE for different use cases. MoQT is designed have enough levers to pull to enable a lot of clever t
15.
by englishm 1y ago
(OP of the Cloudflare blog & submission here) I think kixelated is saying enough stuff beyond our post that he deserves the credit for and this shouldn't be treated as a dupe. (emailed to say as much also)
16.
by englishm 1y ago
I e-mailed to ask they swap it back - I like your post, too! Also, putting it out here, we're building on a _lot_ of kixelated's work with what we've deployed, so he really deserves a lot of credit.
17.
by englishm 1y ago
You might be interested in looking at this RTC example for ideas about how to make bi-directional data flows for arbitrary groups of participants (or players) work through a relay. https://hang.live/ It uses a feature we ha
18.
by englishm 1y ago
It could! We've mainly been focused on using it for audio and video for live streaming and RTC use cases, but the MoQT layer is very intentionally decoupled from the media details so the fan out infrastructure could actually be used fo
19.
by englishm 1y ago
Firefox also has WebTransport support and Safari has a work-in-progress implementation behind a developer mode feature-flag. Safari used to not work at all, but I know they've been putting more effort into it lately, so hopefully we&#x
20.
by englishm 1y ago
Hi! Cloudflare MoQ dev here, happy to answer questions! Thanks for the award, kixelated. xD
21.
Media over QUIC (MoQ): Refactoring the Internet's real-time media stack(blog.cloudflare.com)
72 points by englishm 1y ago|5 comments
22.
by englishm 3y ago
The main thing we're waiting on is WebTransport in Safari. Apple has committed to adding it, and there's already been some work on it in WebKit, but we don't know when it will make its way into a Safari release yet.
23.
by englishm 3y ago
https://2023.demuxed.com/ has the day-long uncut videos available behind a $20 "VoD-only" post-event "ticket" paywall. Eventually https://www.youtube.com/@Demuxed will have the edited Vo
24.
The Problem with Latency Part 2: Could a New Protocol Be Part of the Solution?(blog.webex.com)
1 points by englishm 3y ago|0 comments
25.
by englishm 3y ago
I very much disagree with the characterization of WebRTC being "designed to be overcomplicated and garbage on purpose" but I do think your point about needing to not open the door to DDoS botnet capabilities is something worth hig
26.
by englishm 3y ago
> I hope P2P stays around in browsers. I do, too. There was a W3C draft [1] ~pthatcherg was working on for P2P support for QUIC in the browser that could have maybe become a path to WebRTC using QUIC as a transport, but I think it may ha
27.
by englishm 3y ago
Here are a couple resources which may be helpful: - https://www.mux.com/video-glossary - https://howvideo.works/ Also, if you do want to take the time to read a longer and denser article, but come away with
28.
by englishm 3y ago
The current moq-pub implementation only requires valid fMP4 (a la CMAF) to be provided over stdin. I haven't tested, but I imagine you can do the same with gstreamer. Separately, I've been working on a wrapper library for moq-rs t
29.
by englishm 3y ago
I don't know the timeline, but Apple has committed [1] to adding WebTransport support to WebKit. [1]: https://github.com/WebKit/standards-positions/issues/18#issu...
30.
by englishm 3y ago
That sounds like it was an interesting project! Jean-Baptiste Kempf also presented something at Demuxed last week using FEC and QUIC datagrams to get similarly low latency delivery over WebTransport into a browser. There's also a draft

More ›