Jan-Ivar Bruaroey

@Mozilla. Co-chair of #WebRTC & #WebTransport

[Domenic Denicola @domenic]

Alright, I wrote it. https://t.co/RhrRvYQq0O

[Firefox for Web Developers @FirefoxWebDevs]

It's time for Interop 2026! This is a cross-browser effort where we agree on a set of focus areas to improve compatibility.

Here's how things went in 2025, and what we're taking on for 2026: https://t.co/XKhe7Aq1BD

[Jake Archibald @jaffathecake]

Starting my new role on Monday. Could be anywhere.

[Jan-Ivar Bruaroey @jibrewery]

@ggcaponetto90 Glad you enjoyed it! — If you right-click on a demo and click "Inspect" you'll see they're already iframed. Just don't forget the allow= permission policy:

<iframe src="https://t.co/4UC3JQADPl" allow="speaker-selection">
</iframe>

[Jan-Ivar Bruaroey @jibrewery]

This month I'm tackling Speaker Selection in #WebRTC, another thorny topic.

We'll show how the spec says it should work (and works in #Firefox) even outside of video conferencing, and how to use a fallback to make it work in other browsers.

https://t.co/AWaKgtFHSY

[Jan-Ivar Bruaroey @jibrewery]

Our latest Advancing #WebRTC from #Mozilla covers Chrome's new one-time permissions for camera and microphone feature, and how it benefits users of all browsers! Time to rethink how your website approaches user permissions?

https://t.co/Zx7aOImfwB

[Jan-Ivar Bruaroey @jibrewery]

Mozilla’s CEO discusses testimony in U.S. v. Google search case: "We recognize the importance of improving search competition. However, doing so shouldn’t come at the cost of browser competition." https://t.co/z3jIW6SMQI via @firefox

[Fast Company @FastCompany]

Mozilla’s new message: We’re the only browser not backed by billionaires https://t.co/gIOsErfC4D

[Nils Ohlmeier @nilsohlmeier]

Cloudflare TURN is no longer in Beta and I had the honor of helping to write a blog post about it:
https://t.co/H2vWEd97jt

[Jan-Ivar Bruaroey @jibrewery]

This month's Advancing #WebRTC from #Mozilla dives into the new standard video processing APIs MediaStreamTrackProcessor and VideoTrackGenerator. We cover differences across browsers, and how to polyfill the gap in all browsers, including #Firefox!

https://t.co/iXW2JFmXr5

[Jan-Ivar Bruaroey @jibrewery]

Friday's Advancing #WebRTC blog post was about Debugging with about:webrtc in #Firefox. Useful if you have a bug report to send us.

https://t.co/BH9Y5nPP6L

[Jan-Ivar Bruaroey @jibrewery]

Our latest "Advancing WebRTC" blog post!
It covers the just landed setCodecPreferences API in #Firefox Nightly. This closes an important interop gap for web developers choosing codecs in #WebRTC.

https://t.co/IWryo7YX88

[Figure @Figure_robot]

With OpenAI, Figure 01 can now have full conversations with people

-OpenAI models provide high-level visual and language intelligence
-Figure neural networks deliver fast, low-level, dexterous robot actions

Everything in this video is a neural network:

[Jan-Ivar Bruaroey @jibrewery]

@HCornflower Link added.

[Jan-Ivar Bruaroey @jibrewery]

Mozilla is reviving their "Advancing WebRTC" blog!

We'll post about new #WebRTC-related APIs being standardized in the #W3C, starting with this one on how to end-to-end-encrypt WebRTC calls in all browsers today.
https://t.co/DaA3Te7X7J

[Jan-Ivar Bruaroey @jibrewery]

@HCornflower It already links to https://t.co/dAFsFbQpxd which in turn links to https://t.co/4a3vubAY5h in the OP. Is that sufficient?

[Jan-Ivar Bruaroey @jibrewery]

@HCornflower Thanks for catching I got the year wrong! Updated.

MDN shows Safari shipped the spec in March 2022, Firefox in 2023. Hopefully it didn't surprise anyone that what Mozilla shipped was standards-track (or we would have implemented Plan-B). 😉
https://t.co/efEOFo4xx5

[Jan-Ivar Bruaroey @jibrewery]

Answering that might be a whole other blog post! 😉

Official Mozilla positions on various specs (not just WebRTC) is a process question and is tracked in
https://t.co/WynFXWcHY5

Regarding WebRTC, we have a short-term Firefox roadmap and a separate longer-term view that can be harder to articulate — There's a lot of energy solving different important problems atm in WebRTC, so I think having browsers converge on a cohesive set of principles across various APIs, like limiting realtime exposure to workers, reducing fingerprinting, making sure APIs work together, and maintaining a device model that works across all platforms while centering end-user experience and respects their privacy are all good challenges to solve.

[Jan-Ivar Bruaroey @jibrewery]

Credit goes to Jesup, @krosylight and others on the Mozilla Networking (Necko) team! Firefox Nightly passes 497 of the 557 web platform tests (Chrome passes 413) https://t.co/MkhqeLTvtW

[Gustavo Garcia @anarchyco]

Testing WebTransport with Firefox Nightly and it works perfectly with my Prism server out of the box. Good job Mozilla!