W3C Developers · @w3cdevs
699 followers · 137 posts · Server w3c.social

Wanna get an overview of current @w3c work? Watch this 🎬 from @plehegar about , , and much more!
youtu.be/rNFpgT8ZRqQ?si=H74Z5E

This talk is among the 20 presentations recorded during the "Web Technology Forum" event, organized by the W3C China team.
English and Chinese captions are avail.!: youtube.com/watch?v=3VxD4_4NTB

Read more about this successful event: w3.org/blog/2023/infinite-inte

#webnn #machinelearning #security #webrtc #privateadvertising #webassembly #webgpu #webtransport #webcodecs #dids #wcag

Last updated 1 year ago

W3C Developers · @w3cdevs
644 followers · 123 posts · Server w3c.social

Watch Chad Hart's itw of @tidoust talking about and explaining the game of processing dominoes , , , etc.
youtube.com/watch?t=933&v=lyOS

#streams #webcodecs #webtransport #webrtc

Last updated 1 year ago

W3C Developers · @w3cdevs
594 followers · 95 posts · Server w3c.social

9 June at 11am ET: webrtcH4cKS organizes a live panel discussion on , and the future of w/ @tidoust (@w3c), Bernard Aboba (Microsoft) and Jordi Cenzano (Meta).
Get a cal invite here: webrtchacks.com/livestream/

This follows a series of 2 articles by @tidoust and @dontcallmeDOM: webrtchacks.com/real-time-vide

#webtransport #webcodecs #webrtc

Last updated 1 year ago

W3C Developers · @w3cdevs
485 followers · 62 posts · Server w3c.social

🆕 You've enjoyed reading the creation of a multi-step video processing pipeline? This second article by @tidoust explores the actual processing of video frames! webrtchacks.com/video-frame-pr

Technologies involved are .

Give feedback and contribute to an experimental code for creating video processing pipelines using these web technologies: github.com/tidoust/media-tests Thanks!

#javascript #webassembly #webgpu #webcodecs #webgl #webtransport #webnn

Last updated 2 years ago

tiesselune :tiesseluneShiny: · @tiesselune
346 followers · 1022 posts · Server g33ks.coffee

Wow, I'm discovering , an experimental Web API that is being implemented in chromium browsers, which is basically (please bare with me for a minute), UDP websockets over HTTP/3.

What it means : UDP is an alternative to TCP (as in TCP/IP) that has no transport control, which means that "datagrams" are sent (messages) with no garantee of really arriving at destination nor in the right order. Usually they do, but in opposition to TCP, it won't be detected and fixed at the protocol level. It means lighter and faster communication at the expanse of reliability. Today, UDP is used for online game synchronisation, voice and video chat, etc. Contexts where "missing a frame" is not a problem.

And recently, it's used for HTTP/3. You might be using it right now on most Google websites without even knowing it. Reliability is not provided by the protocol, but by the browser directly, which has a lot of interesting applications.

Anyway. WebTransport means that the browsers are exposing this as a Javascript API, which gives you a faster alternative to Websockets, with both reliable (with browser/server checks for integrity and order) and unreliable (data comes in any order, packets get dropped) modes.

Which is very good news for games, online video, etc.

That's it that's the toot.

#webtransport

Last updated 2 years ago