<?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, 06 Nov 2025 11:01:16 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.5</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>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" fetchpriority="high" 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="(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" 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="(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" 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="(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>
		<item>
		<title>Measuring the response latency of OpenAIs WebRTC-based Realtime API</title>
		<link>https://webrtchacks.com/measuring-the-response-latency-of-openais-webrtc-based-real-time-api/</link>
					<comments>https://webrtchacks.com/measuring-the-response-latency-of-openais-webrtc-based-real-time-api/#respond</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Tue, 01 Apr 2025 11:00:04 +0000</pubDate>
				<category><![CDATA[Guide]]></category>
		<category><![CDATA[Reverse-Engineering]]></category>
		<category><![CDATA[Blackbox Exploration]]></category>
		<category><![CDATA[openai]]></category>
		<category><![CDATA[realtime api with webrtc]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4460</guid>

					<description><![CDATA[<img width="729" height="800" src="https://webrtchacks.com/wp-content/uploads/2025/03/openai-response-latency-post-image-square-729x800.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/03/openai-response-latency-post-image-square-729x800.jpg 729w, https://webrtchacks.com/wp-content/uploads/2025/03/openai-response-latency-post-image-square-768x843.jpg 768w, https://webrtchacks.com/wp-content/uploads/2025/03/openai-response-latency-post-image-square.jpg 1024w" sizes="auto, (max-width: 729px) 100vw, 729px" /><p>As Chad mentioned in his post last week, we have been diving into what OpenAI is doing with WebRTC. Over the last months, we actually did a full teardown and compared OpenAI&#8217;s Realtime API to what powers chatgpt.com. What intrigued us most was how to measure response latency. One of the key metrics for any [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/measuring-the-response-latency-of-openais-webrtc-based-real-time-api/">Measuring the response latency of OpenAIs WebRTC-based Realtime API</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/measuring-the-response-latency-of-openais-webrtc-based-real-time-api/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Unofficial Guide to OpenAI’s (Beta) Realtime WebRTC API</title>
		<link>https://webrtchacks.com/the-unofficial-guide-to-openai-realtime-webrtc-api/</link>
					<comments>https://webrtchacks.com/the-unofficial-guide-to-openai-realtime-webrtc-api/#comments</comments>
		
		<dc:creator><![CDATA[Chad Hart]]></dc:creator>
		<pubDate>Tue, 18 Mar 2025 11:45:30 +0000</pubDate>
				<category><![CDATA[Guide]]></category>
		<category><![CDATA[llm]]></category>
		<category><![CDATA[openai]]></category>
		<category><![CDATA[realtime api with webrtc]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4424</guid>

					<description><![CDATA[<img width="500" height="800" src="https://webrtchacks.com/wp-content/uploads/2025/03/word-image-4424-1-500x800.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/03/word-image-4424-1-500x800.png 500w, https://webrtchacks.com/wp-content/uploads/2025/03/word-image-4424-1-768x1229.png 768w, https://webrtchacks.com/wp-content/uploads/2025/03/word-image-4424-1.png 800w" sizes="auto, (max-width: 500px) 100vw, 500px" /><p>EDITOR NOTE: OpenAI release the GA version of the Realtime API with WebRTC. This post covers the Beta version-only. The GA version is fully backward compatible and everything here is still accurate &#8211; just don&#8217;t mix approaches. I will have an gpt-realtime GA version update / version soon! OpenAI using WebRTC in its Realtime API [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/the-unofficial-guide-to-openai-realtime-webrtc-api/">The Unofficial Guide to OpenAI’s (Beta) Realtime WebRTC API</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/the-unofficial-guide-to-openai-realtime-webrtc-api/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>2024 WebRTC in Open Source Review: A Quantitative Analysis</title>
		<link>https://webrtchacks.com/2024-webrtc-in-open-source-review-a-quantitative-analysis/</link>
					<comments>https://webrtchacks.com/2024-webrtc-in-open-source-review-a-quantitative-analysis/#respond</comments>
		
		<dc:creator><![CDATA[Chad Hart]]></dc:creator>
		<pubDate>Tue, 28 Jan 2025 12:30:26 +0000</pubDate>
				<category><![CDATA[Review]]></category>
		<category><![CDATA[AR]]></category>
		<category><![CDATA[BigQuery]]></category>
		<category><![CDATA[github]]></category>
		<category><![CDATA[ML]]></category>
		<category><![CDATA[MoQ]]></category>
		<category><![CDATA[MR]]></category>
		<category><![CDATA[webcodecs]]></category>
		<category><![CDATA[webtransport]]></category>
		<category><![CDATA[WebXR]]></category>
		<category><![CDATA[WHEP]]></category>
		<category><![CDATA[WHIP]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4368</guid>

					<description><![CDATA[<img width="800" height="451" src="https://webrtchacks.com/wp-content/uploads/2025/01/YouTube-livestream-thumbnail-e1738067529645-800x451.gif" 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/01/YouTube-livestream-thumbnail-e1738067529645-800x451.gif 800w, https://webrtchacks.com/wp-content/uploads/2025/01/YouTube-livestream-thumbnail-e1738067529645-768x433.gif 768w, https://webrtchacks.com/wp-content/uploads/2025/01/YouTube-livestream-thumbnail-e1738067529645-1536x866.gif 1536w, https://webrtchacks.com/wp-content/uploads/2025/01/YouTube-livestream-thumbnail-e1738067529645-600x338.gif 600w" sizes="auto, (max-width: 800px) 100vw, 800px" /><p>I have been updating a WebRTC in Open Source dataset derived from GitHub event data for 10 years now. I periodically update this to look for recent trends on WebRTC activity, popular repos, and new API usage. I hosted a live stream of my 2024 review back in December where Tsahi Levent-Levi joined to help [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/2024-webrtc-in-open-source-review-a-quantitative-analysis/">2024 WebRTC in Open Source Review: A Quantitative Analysis</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/2024-webrtc-in-open-source-review-a-quantitative-analysis/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Capture &#038; Replay WebRTC video streams for debugging – video_replay 2025 update</title>
		<link>https://webrtchacks.com/capture-and-replay-streams-with-video-replay/</link>
					<comments>https://webrtchacks.com/capture-and-replay-streams-with-video-replay/#comments</comments>
		
		<dc:creator><![CDATA[Philipp Hancke]]></dc:creator>
		<pubDate>Tue, 21 Jan 2025 12:09:53 +0000</pubDate>
				<category><![CDATA[Guide]]></category>
		<category><![CDATA[debug]]></category>
		<category><![CDATA[video_replay]]></category>
		<category><![CDATA[wireshark]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4352</guid>

					<description><![CDATA[<img width="800" height="450" src="https://webrtchacks.com/wp-content/uploads/2025/01/video_replay-2025-post-image-800x450.webp" 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/01/video_replay-2025-post-image-800x450.webp 800w, https://webrtchacks.com/wp-content/uploads/2025/01/video_replay-2025-post-image-768x432.webp 768w, https://webrtchacks.com/wp-content/uploads/2025/01/video_replay-2025-post-image-600x338.webp 600w, https://webrtchacks.com/wp-content/uploads/2025/01/video_replay-2025-post-image.webp 1280w" sizes="auto, (max-width: 800px) 100vw, 800px" /><p>Debugging WebRTC media issues, especially video, often requires access to the unencrypted RTP payloads. We talked about this back in 2017 already and had a great blog post on using the libWebRTC &#8220;video_replay&#8221; tool. While that post has aged remarkably well, video_replay has improved significantly, in particular since it is now possible to create the [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/capture-and-replay-streams-with-video-replay/">Capture &#038; Replay WebRTC video streams for debugging – video_replay 2025 update</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/capture-and-replay-streams-with-video-replay/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		<enclosure url="https://webrtchacks.com/wp-content/uploads/2025/01/webrtchacks.mp4" length="167" type="video/mp4" />

			</item>
		<item>
		<title>Power-up getStats for Client Monitoring</title>
		<link>https://webrtchacks.com/power-up-getstats-for-client-monitoring/</link>
					<comments>https://webrtchacks.com/power-up-getstats-for-client-monitoring/#comments</comments>
		
		<dc:creator><![CDATA[Balázs Kreith]]></dc:creator>
		<pubDate>Tue, 03 Sep 2024 09:45:16 +0000</pubDate>
				<category><![CDATA[Guide]]></category>
		<category><![CDATA[getStats]]></category>
		<category><![CDATA[observeRTC]]></category>
		<category><![CDATA[qualityLimitationReason]]></category>
		<category><![CDATA[RTT]]></category>
		<guid isPermaLink="false">https://webrtchacks.com/?p=4309</guid>

					<description><![CDATA[<img width="800" height="800" src="https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="A person wearing a garment Description automatically generated" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1.jpg 800w, https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1-300x300.webp 300w, https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1-768x768.webp 768w, https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1-80x80.webp 80w, https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1-600x600.webp 600w, https://webrtchacks.com/wp-content/uploads/2024/08/power-up-getStats-1-150x150.webp 150w" sizes="auto, (max-width: 800px) 100vw, 800px" /><p>WebRTC’s peer connection includes a getStats method that provides a variety of low-level statistics. Basic apps don’t really need to worry about these stats but many more advanced WebRTC apps use getStats for passive monitoring and even to make active changes. Extracting meaning from the getStats data is not all that straightforward. Luckily return author [&#8230;]</p>
<p>The post <a href="https://webrtchacks.com/power-up-getstats-for-client-monitoring/">Power-up getStats for Client Monitoring</a> appeared first on <a href="https://webrtchacks.com">webrtcHacks</a>.</p>
]]></description>
		
					<wfw:commentRss>https://webrtchacks.com/power-up-getstats-for-client-monitoring/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
