kixelated

6 ms·

31.
by kixelated 1y ago
Horizontal black lines? Dunno what that could be about, we render to a <canvas> element which is resized to match the source video and then resized again to match the window with CSS.
32.
by kixelated 1y ago
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 any
33.
by kixelated 1y ago
That is all sorts of miserable. I had an initial prototype that emulated UDP over SCTP, running QUIC (without encryption) on top. The problem is that SCTP becomes the bottleneck, plus it's super complicated. I immediately jumped ship t
34.
by kixelated 1y ago
Each track is further segmented into streams. So you can prioritize new > old, in addition to audio > video.
35.
by kixelated 1y ago
Thank you so much dang.
36.
by kixelated 1y ago
Chrome and Firefox support WebTransport. Safari has announced intent to support it and they already use QUIC under the hood for HTTP/3. Cloud services are pretty TCP/HTTP centric which can be annoying. Any provider that gives you
37.
by kixelated 1y ago
Hi I originally wrote WARP and used something similar at Twitch. It supports CMAF segments, so the media encoding is backwards compatible with HLS/DASH and can share a cache, which is a big deal for a gradual production rollout.
38.
by kixelated 1y ago
Yeah I will soon, but I could also use the time to fix up some more stuff.
39.
by kixelated 1y ago
QUIC/WebTransport gives you the ability to drop media, either via stream or datagrams, so you can get the same sort of response to congestion as WebRTC. However, one flaw with MoQ right now is that Google's GCC congestion controll
40.
by kixelated 1y ago
I linked the URL to their relay but otherwise all of the libraries, demos, rants, jokes are my own. I can remove the link to their post if that would help, or I could get Cloudflare's blessing. It's just a bit frustrating.
41.
by kixelated 1y ago
Hey folks, it seems like an admin merged my post with the Cloudflare post :(. Here's the original (and much funnier) post: https://moq.dev/blog/first-cdn/ And for context, Cloudflare is using a fork of my ope
42.
by kixelated 1y ago
Hey dang, I don't think my blog is a repost. It links the Cloudflare announcement but the content is completely different (and actually funny). Is there any way you could restore it?
43.
by kixelated 1y ago
Firefox should work, I just don't test it often. Lemme fix.
44.
The First Media over QUIC App: Hang.live(moq.dev)
2 points by kixelated 1y ago|1 comments
45.
by kixelated 1y ago
Hey HN, I've spent the last few years working on an open source WebRTC replacement using new web technologies. It's being standardized by the IETF, but progress is slow, so I finally decided to get serious and go full-time making
46.
The first Media over QUIC CDN: Cloudflare(moq.dev)
292 points by kixelated 1y ago|121 comments
47.
TLS and QUIC: A Masochist's Guide(quic.video)
2 points by kixelated 1y ago|0 comments
48.
by kixelated 1y ago
Absolutely. Logs should be bursty, because they're most useful when debugging rare issues. If you have identical log lines, then that should have been a metric instead. Metrics should be sampled based on frequency, because they dedupli
49.
Application First – Media over QUIC(quic.video)
2 points by kixelated 1y ago|0 comments
50.
Your Job Now: Be the Outlier(quic.video)
3 points by kixelated 1y ago|0 comments
51.
by kixelated 2y ago
I tried using SCTP before QUIC. Unfortunately, while the API looks like you can mix reliable/unreliable messages, in reality the transport doesn't support it because of how FORWARD-TSN works. There were some other pretty fundament
52.
Never* Use Datagrams(quic.video)
3 points by kixelated 3y ago|0 comments
53.
QUIC's (Hidden) Superpowers(quic.video)
1 points by kixelated 3y ago|0 comments
54.
by kixelated 3y ago
Fun fact, at one point it was better (and cheaper) to serve Telstra viewers out of LA instead of our Sydney datacenter because of the mess that is Australia internet infrastructure.
55.
by kixelated 3y ago
AT&T customers will complain if AT&T throttles a RTMP stream, as it will cause indefinitely buffering. AT&T customers are less likely to complain if AT&T throttles a HLS broadcast, as the quality will just be lower.
56.
by kixelated 3y ago
I am bad at web design.
57.
by kixelated 3y ago
QUIC supports self-signed certs if LetsEncrypt is too corporate for you. WebTransport lets you specify the certificate fingerprint (sha256) much like WebRTC, although it does enforce that the certificate is valid for <14 days so it will
58.
by kixelated 3y ago
I'm glad you liked it. > A client can theoretically detect a bandwidth fall (or even guess it) while loading a segment, abort its request (which may close the TCP socket, event that then may be processed server-side, or not), and di
59.
by kixelated 3y ago
QUIC is a major functionality improvement, while IPv6 is a capacity improvement. You can do some extremely cool things with QUIC that definitely deserves a post of its own.
60.
by kixelated 3y ago
ABR is absolutely required for distribution. MoQ also supports ABR, but additionally gives you the ability to also drop the tail of a GoP if a rendition switch is too slow, or no lower rendition exists. As for maintaining existing standards

More ›