<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>webrtcHacks</title>
	<atom:link href="https://webrtchacks.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://webrtchacks.com/</link>
	<description>guides and information for WebRTC developers</description>
	<lastBuildDate>Thu, 08 Oct 2026 10:42:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.11</generator>

<image>
	<url>https://webrtchacks.com/wp-content/uploads/2022/04/webrtcHacks-icon-80x80.jpg</url>
	<title>webrtcHacks</title>
	<link>https://webrtchacks.com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Voice agents get confused by echo too</title>
		<link>https://webrtchacks.com/voice-agents-get-confused-by-echo-too/</link>
					<comments>https://webrtchacks.com/voice-agents-get-confused-by-echo-too/#respond</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Thu, 08 Oct 2026 11:50:00 +0000</pubDate>
				<category><![CDATA[Reverse-Engineering]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[AEC]]></category>
		<category><![CDATA[AEC3]]></category>
		<category><![CDATA[Blackbox Exploration]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[echo]]></category>
		<category><![CDATA[Edge]]></category>
		<category><![CDATA[getUserMedia]]></category>
		<category><![CDATA[libwebrtc]]></category>
		<category><![CDATA[machine learning]]></category>
		<category><![CDATA[VAD]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4977</guid>

					<description><![CDATA[<img width="800" height="447" src="https://webrtchacks.com/wp-content/uploads/2026/10/chrome-aec3-robot-monkey-800x447.webp" class="webfeedsFeaturedVisual wp-post-image" alt="A robot monkey talks into a tin-can telephone while holding the listening can to its own ear; a baby monkey covers its mouth beside it." style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" fetchpriority="high" srcset="https://webrtchacks.com/wp-content/uploads/2026/10/chrome-aec3-robot-monkey-800x447.webp 800w, https://webrtchacks.com/wp-content/uploads/2026/10/chrome-aec3-robot-monkey-768x429.webp 768w, https://webrtchacks.com/wp-content/uploads/2026/10/chrome-aec3-robot-monkey.webp 1376w" sizes="(max-width: 800px) 100vw, 800px" /><p>Philipp Hancke tests why voice agents sometimes answer their own greetings. In his setup, echo reached transcription in 21% of Edge sessions and 4% of Chrome sessions. AEC dumps show how echo cancellation, gain control, and VAD thresholds interact.</p>
<p>The post <a href="https://webrtchacks.com/voice-agents-get-confused-by-echo-too/">Voice agents get confused by echo too</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/voice-agents-get-confused-by-echo-too/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Google Chrome downloads a new neural AEC while you are not looking</title>
		<link>https://webrtchacks.com/chrome-neural-echo-cancellation/</link>
					<comments>https://webrtchacks.com/chrome-neural-echo-cancellation/#respond</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Tue, 06 Oct 2026 13:08:05 +0000</pubDate>
				<category><![CDATA[Reverse-Engineering]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[AEC]]></category>
		<category><![CDATA[AEC3]]></category>
		<category><![CDATA[Blackbox Exploration]]></category>
		<category><![CDATA[Chrome]]></category>
		<category><![CDATA[echo]]></category>
		<category><![CDATA[getUserMedia]]></category>
		<category><![CDATA[libwebrtc]]></category>
		<category><![CDATA[machine learning]]></category>
		<category><![CDATA[TensorFlow]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4918</guid>

					<description><![CDATA[<img width="800" height="450" src="https://webrtchacks.com/wp-content/uploads/2026/09/chrome-aec3-monkeys-1672x941-1-800x450.webp" class="webfeedsFeaturedVisual wp-post-image" alt="Three baby monkeys: one covers its eyes, one covers its ears, and one has its mouth open." style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" srcset="https://webrtchacks.com/wp-content/uploads/2026/09/chrome-aec3-monkeys-1672x941-1-800x450.webp 800w, https://webrtchacks.com/wp-content/uploads/2026/09/chrome-aec3-monkeys-1672x941-1-768x432.webp 768w, https://webrtchacks.com/wp-content/uploads/2026/09/chrome-aec3-monkeys-1672x941-1-1536x864.webp 1536w, https://webrtchacks.com/wp-content/uploads/2026/09/chrome-aec3-monkeys-1672x941-1-600x338.webp 600w, https://webrtchacks.com/wp-content/uploads/2026/09/chrome-aec3-monkeys-1672x941-1.webp 1672w" sizes="(max-width: 800px) 100vw, 800px" /><p>Chrome quietly delivers a neural model that changes part of its echo-cancellation pipeline. Philipp Hancke reverse engineers the model and compares echo suppression and speech recognition against AEC3.</p>
<p>The post <a href="https://webrtchacks.com/chrome-neural-echo-cancellation/">Google Chrome downloads a new neural AEC while you are not looking</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/chrome-neural-echo-cancellation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Comparing WebRTC video codecs with a proper dataset</title>
		<link>https://webrtchacks.com/comparing-webrtc-video-codecs-with-a-proper-dataset/</link>
					<comments>https://webrtchacks.com/comparing-webrtc-video-codecs-with-a-proper-dataset/#respond</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Thu, 27 Aug 2026 11:39:17 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[av1]]></category>
		<category><![CDATA[codecs]]></category>
		<category><![CDATA[h.264]]></category>
		<category><![CDATA[libwebrtc]]></category>
		<category><![CDATA[simulcast]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[vp8]]></category>
		<category><![CDATA[VP9]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4863</guid>

					<description><![CDATA[<img width="800" height="450" src="https://webrtchacks.com/wp-content/uploads/2026/08/codex-post-4863-codec-race-20260827-800x450.webp" class="webfeedsFeaturedVisual wp-post-image" alt="Horse race with VP8, H.264, VP9, and AV1 replacing the race numbers on the horses" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" srcset="https://webrtchacks.com/wp-content/uploads/2026/08/codex-post-4863-codec-race-20260827-800x450.webp 800w, https://webrtchacks.com/wp-content/uploads/2026/08/codex-post-4863-codec-race-20260827-768x432.webp 768w, https://webrtchacks.com/wp-content/uploads/2026/08/codex-post-4863-codec-race-20260827-600x338.webp 600w, https://webrtchacks.com/wp-content/uploads/2026/08/codex-post-4863-codec-race-20260827.webp 1332w" sizes="(max-width: 800px) 100vw, 800px" /><p>Stumbling over Microsoft&#8217;s Video Conferencing Dataset (VCD) I asked Claude to take on a video codec engineer&#8217;s favorite hot take: compare video codecs. It did a fairly good writeup using the tooling provided by libWebRTC. One of the most surprising results was that background blur makes H.264 a lot more effective. Other than that, the [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/comparing-webrtc-video-codecs-with-a-proper-dataset/">Comparing WebRTC video codecs with a proper dataset</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/comparing-webrtc-video-codecs-with-a-proper-dataset/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Vector Vibing to speed up Opus encode by 20%</title>
		<link>https://webrtchacks.com/vector-vibing-to-speed-up-opus-encode-by-20/</link>
					<comments>https://webrtchacks.com/vector-vibing-to-speed-up-opus-encode-by-20/#respond</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Thu, 02 Jul 2026 12:34:00 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4802</guid>

					<description><![CDATA[<img width="512" height="288" src="https://webrtchacks.com/wp-content/uploads/2026/07/opusavx2.png" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" /><p>tl;dr: Opus encoding just got 20% faster on desktop Chromium by turning on AVX2 vectorization in libopus. Vectorization means one instruction doing the same arithmetic on a whole vector of values at once instead of one at a time. Codecs spend their hot loops running identical math across long buffers of samples, exactly where vectorization [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/vector-vibing-to-speed-up-opus-encode-by-20/">Vector Vibing to speed up Opus encode by 20%</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/vector-vibing-to-speed-up-opus-encode-by-20/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Vibe-coding WebRTC</title>
		<link>https://webrtchacks.com/webrtc-vibes/</link>
					<comments>https://webrtchacks.com/webrtc-vibes/#respond</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Tue, 02 Jun 2026 11:08:06 +0000</pubDate>
				<category><![CDATA[Review]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4782</guid>

					<description><![CDATA[<p>Well, that title is clickbait for Hacker News. The honest title would have been &#8220;using AI to tackle long-standing WebRTC issues.&#8221; Posts on webrtcHacks are rare these days, and in German we would say there are Unkenrufe that WebRTC is dead. It is not. It is the infrastructure for meetings, game streaming, and voice AI, [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/webrtc-vibes/">Vibe-coding WebRTC</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/webrtc-vibes/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>WebRTC vs. MoQ by Use Case</title>
		<link>https://webrtchacks.com/webrtc-vs-moq-by-use-case/</link>
					<comments>https://webrtchacks.com/webrtc-vs-moq-by-use-case/#comments</comments>
		
		<dc:creator><![CDATA[Chad Hart]]></dc:creator>
		<pubDate>Tue, 04 Nov 2025 12:05:35 +0000</pubDate>
				<category><![CDATA[Standards]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[FCM-RT]]></category>
		<category><![CDATA[HLS]]></category>
		<category><![CDATA[live streaming]]></category>
		<category><![CDATA[LL-HLS]]></category>
		<category><![CDATA[MoQ]]></category>
		<category><![CDATA[quic]]></category>
		<category><![CDATA[relay]]></category>
		<category><![CDATA[WHIP]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4716</guid>

					<description><![CDATA[<img width="800" height="800" src="https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-800x800.jpeg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-800x800.jpeg 800w, https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-300x300.jpeg 300w, https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-768x768.jpeg 768w, https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-80x80.jpeg 80w, https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-600x600.jpeg 600w, https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2-150x150.jpeg 150w, https://webrtchacks.com/wp-content/uploads/2025/11/word-image-4716-1-2.jpeg 1024w" sizes="auto, (max-width: 800px) 100vw, 800px" /><p>This might be my first editorial style post here. Fippo’s Is everyone switching to MoQ from WebRTC? started some threads on MoQ vs. WebRTC. I started to respond, but my responses quickly became too long so I decided to go even deeper with a post here. Fippo’s post shows hard data that Media over QUIC [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/webrtc-vs-moq-by-use-case/">WebRTC vs. MoQ by Use Case</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/webrtc-vs-moq-by-use-case/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
		<item>
		<title>Is everyone switching to MoQ from WebRTC?</title>
		<link>https://webrtchacks.com/is-everyone-switching-to-moq/</link>
					<comments>https://webrtchacks.com/is-everyone-switching-to-moq/#comments</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Tue, 07 Oct 2025 11:50:35 +0000</pubDate>
				<category><![CDATA[Standards]]></category>
		<category><![CDATA[chromestatus]]></category>
		<category><![CDATA[cloudflare]]></category>
		<category><![CDATA[MoQ]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4667</guid>

					<description><![CDATA[<img width="666" height="375" src="https://webrtchacks.com/wp-content/uploads/2025/10/angry-webrtc-developers-complaining-about-moq.webp" class="webfeedsFeaturedVisual wp-post-image" alt="Angry WebRTC developers complain about MoQ" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://webrtchacks.com/wp-content/uploads/2025/10/angry-webrtc-developers-complaining-about-moq.webp 666w, https://webrtchacks.com/wp-content/uploads/2025/10/angry-webrtc-developers-complaining-about-moq-600x338.webp 600w" sizes="auto, (max-width: 666px) 100vw, 666px" /><p>It is time for another edition of &#8220;Is everyone switching to…&#8220;. Cloudflare recently published a blog post about Media over Quic (MoQ) which made a number of statements about WebRTC that require some &#8220;clarification&#8221;. Let us start with that and look at MoQ and WebTransport after that. An odd understanding of WebRTC The blog post [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/is-everyone-switching-to-moq/">Is everyone switching to MoQ from WebRTC?</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/is-everyone-switching-to-moq/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>How OpenAI does WebRTC in the new gpt-realtime</title>
		<link>https://webrtchacks.com/how-openai-does-webrtc-in-the-new-gpt-realtime/</link>
					<comments>https://webrtchacks.com/how-openai-does-webrtc-in-the-new-gpt-realtime/#respond</comments>
		
		<dc:creator><![CDATA[Chad Hart]]></dc:creator>
		<pubDate>Tue, 23 Sep 2025 11:15:15 +0000</pubDate>
				<category><![CDATA[Reverse-Engineering]]></category>
		<category><![CDATA[Blackbox Exploration]]></category>
		<category><![CDATA[chatgpt]]></category>
		<category><![CDATA[openai]]></category>
		<category><![CDATA[realtime api with webrtc]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4634</guid>

					<description><![CDATA[<img width="767" height="800" src="https://webrtchacks.com/wp-content/uploads/2025/09/word-image-4634-1-1-767x800.jpeg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://webrtchacks.com/wp-content/uploads/2025/09/word-image-4634-1-1-767x800.jpeg 767w, https://webrtchacks.com/wp-content/uploads/2025/09/word-image-4634-1-1-768x801.jpeg 768w, https://webrtchacks.com/wp-content/uploads/2025/09/word-image-4634-1-1.jpeg 800w" sizes="auto, (max-width: 767px) 100vw, 767px" /><p>Earlier this month, OpenAI released the GA version of its realtime API. This includes many capabilities that the Beta didn’t have, including video support. I started out doing an update to the The Unofficial Guide to OpenAI’s Realtime WebRTC API I made for the Beta release last November. I discovered there were enough WebRTC updates [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/how-openai-does-webrtc-in-the-new-gpt-realtime/">How OpenAI does WebRTC in the new gpt-realtime</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/how-openai-does-webrtc-in-the-new-gpt-realtime/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How WebRTC’s NetEQ Jitter Buffer Provides Smooth Audio</title>
		<link>https://webrtchacks.com/how-webrtcs-neteq-jitter-buffer-provides-smooth-audio/</link>
					<comments>https://webrtchacks.com/how-webrtcs-neteq-jitter-buffer-provides-smooth-audio/#comments</comments>
		
		<dc:creator><![CDATA[Fengdeng Lyu]]></dc:creator>
		<pubDate>Tue, 03 Jun 2025 11:00:53 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[chromium]]></category>
		<category><![CDATA[jitter]]></category>
		<category><![CDATA[jitter buffer]]></category>
		<category><![CDATA[libwebrtc]]></category>
		<category><![CDATA[neteq]]></category>
		<category><![CDATA[ptime]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4560</guid>

					<description><![CDATA[<img width="800" height="800" src="https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1.png" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1.png 800w, https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1-300x300.png 300w, https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1-768x768.png 768w, https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1-80x80.png 80w, https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1-600x600.png 600w, https://webrtchacks.com/wp-content/uploads/2025/06/word-image-4560-1-150x150.png 150w" sizes="auto, (max-width: 800px) 100vw, 800px" /><p>Audio jitter buffers are required 101 introductory material for understanding VoIP. libWebRTC’s audio jitter buffer implementation &#8211; the one in Chromium &#8211; is known as NetEQ. NetEQ is anything but basic. This is good from a user perspective since real-life networks conditions are often challenging. However, this means NetEQ’s esoteric code is complex and difficult [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/how-webrtcs-neteq-jitter-buffer-provides-smooth-audio/">How WebRTC’s NetEQ Jitter Buffer Provides Smooth Audio</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/how-webrtcs-neteq-jitter-buffer-provides-smooth-audio/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>OpenAI &#038; WebRTC Q&#038;A with Sean DuBois</title>
		<link>https://webrtchacks.com/openai-webrtc-qa-with-sean-dubois/</link>
					<comments>https://webrtchacks.com/openai-webrtc-qa-with-sean-dubois/#respond</comments>
		
		<dc:creator><![CDATA[Chad Hart]]></dc:creator>
		<pubDate>Tue, 22 Apr 2025 10:23:54 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[MoQ]]></category>
		<category><![CDATA[openai]]></category>
		<category><![CDATA[pion]]></category>
		<category><![CDATA[Q&A]]></category>
		<category><![CDATA[quic]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4518</guid>

					<description><![CDATA[<img width="800" height="535" src="https://webrtchacks.com/wp-content/uploads/2025/04/openai-qa-post-image.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://webrtchacks.com/wp-content/uploads/2025/04/openai-qa-post-image.jpg 800w, https://webrtchacks.com/wp-content/uploads/2025/04/openai-qa-post-image-768x514.jpg 768w, https://webrtchacks.com/wp-content/uploads/2025/04/openai-qa-post-image-600x400.jpg 600w" sizes="auto, (max-width: 800px) 100vw, 800px" /><p>OpenAI is utilizing WebRTC for its Realtime API! Even better, webrtcHacks friend and Pion founder Sean DuBois helped to develop it and agreed to a Q&#38;A about the implementation. It is not often a massive WebRTC use case like this emerges so rapidly. In addition, Sean was extremely transparent about his work at OpenAI. In [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/openai-webrtc-qa-with-sean-dubois/">OpenAI &#038; WebRTC Q&#038;A with Sean DuBois</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/openai-webrtc-qa-with-sean-dubois/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
