From d4fb6aa83ca5398e7059a8a0f82bdbbdec72ad7a Mon Sep 17 00:00:00 2001 From: kixelated Date: Mon, 30 Oct 2023 11:15:59 +0900 Subject: [PATCH] Update replacing-webrtc --- web/src/pages/blog/replacing-webrtc.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/web/src/pages/blog/replacing-webrtc.mdx b/web/src/pages/blog/replacing-webrtc.mdx index da91f8d..b5294e2 100644 --- a/web/src/pages/blog/replacing-webrtc.mdx +++ b/web/src/pages/blog/replacing-webrtc.mdx @@ -252,7 +252,7 @@ This is a gross oversimplification of a topic with an immense amount of research | ECN | Get told by the router to back off. | None\* | [L4S](https://datatracker.ietf.org/doc/rfc9330/) | There's no single "best" congestion control algorithm; it depends on your use-case, network, and target latency. -But this is one area where WebRTC has a huge advantage thanks to [transport-wide-cc](https://webrtc.googlesource.com/src/+/refs/heads/main/docs/native-code/rtp-hdrext/transport-wide-cc-02/README.md). +But this is one area where WebRTC has an advantage thanks to [transport-wide-cc](https://webrtc.googlesource.com/src/+/refs/heads/main/docs/native-code/rtp-hdrext/transport-wide-cc-02/README.md). ### Reducing Bitrate