Talk:WebRTC

"It is licensed under the 3-clause BSD license" - what is licensed? The standard does not need a license. A particular implementation might be licensed but it is not clear which implementation this sentence might be referring to.
 * It looks like the page was edited by people who were confusing the specification with the "webrtc" package. I toned that down a bit, I hope. --Gmaxwell (talk) 22:09, 25 July 2012 (UTC)

Support Section
What does "PC" mean in this context? Is this Windows? Or IBM-PC compatible machine and various OSs? — Preceding unsigned comment added by 78.45.92.136 (talk) 15:54, 30 October 2013 (UTC)

Opera support
'Opera: WebRTC implement the laboratory version of Opera in January 2012. The stable version now fully supports the standard.'

Is this correct? As far as I'm aware, Opera 12 supports getUserMedia, but not PeerConnection. — Preceding unsigned comment added by Samdutton (talk • contribs) 16:44, 16 July 2012 (UTC)

Answering my own question :). Correct -- and since v15, Opera doesn't support getUserMedia. However, Opera is now based on Chromium, and is expected to provide full WebRTC support in future. Sam Dutton (talk) 15:16, 6 September 2013 (UTC)

Scope of WebRTC?
Does anyone know the scope of the WebRTC project? What features does the project do, and what features are out of its scope? Things that i'm wondering about in particular:
 * what kind of communication will be supported? Text chat between two users, multi-user chat, voice telephony, video telephony, smell-o-vision?
 * what about software for a central server which handles lots of users? User management, rosters/address book, billing?
 * what about infrastructure? Will the project set up a server which is used by all users? Or is this up to the users? Or is the whole thing just between two users anyway, with no central server (kind of like a walkie-talkie)?
 * chat client features (away message, finding other users, user blocking, chat logs, video filters)? — Preceding unsigned comment added by 82.83.209.8 (talk) 16:41, 31 August 2013 (UTC)

Video codec
It's very strange that the current spec lists feature requirements for a video codec but not what codec must be supported. All current implementations seem to support VP8 (correct?), but I guess the MPEGLA has blocked its standardization. How can WebRTC be an interoperable standard without mandatory support for a specific video codec? If two clients don't support a common codec what happens? --88.73.51.230 (talk) 11:52, 1 October 2013 (UTC)

WebRTC in action
I sugest providing links to running implementations like appear.in and comtalk.co — Preceding unsigned comment added by 2.129.83.238 (talk) 04:34, 11 February 2015 (UTC)

Nobody seems to object. By the way, appear.in had to change its name to whereby.com as a result of some trademark dispute, and comtalk.co seems to have disappeared. On the other hand there are some newer companies making WebRTC available, like talky.io. It would be useful to have an up-to-date list. Longitude2 (talk) 10:31, 31 March 2020 (UTC)

Local IP vulnerability known long before citation given
The article currently says:


 * In January 2015, TorrentFreak reported that browsers supporting WebRTC suffer from a serious security flaw that compromises the security of VPN-tunnels, by allowing the true IP address of the user to be read.

This implies that the vulnerability wasn't known, or not widely so, before that. But there's a bug filed against Firefox a year earlier, which discusses the fact that it was already well-known at the time:


 * I've see this discussed publicly on twitter and elsewhere, and there are public demos so I don't think we need to keep this hidden. (e.g. http://net.ipcalf.com/)

It would be good if someone could find a decent citation from 2014 or earlier to replace the current text. - IMSoP (talk) 19:14, 25 July 2015 (UTC)

Standardisation
The article currently suggests that WebRTC is already standardised, but I found no evidence to that end. In fact, the W3C still explicitly labels it a working draft and webrtc.org says that the APIs are still in development and subject to change. This should be incorporated into the article.–Totie (talk) 23:00, 7 September 2016 (UTC)
 * I've made a minor change to the introduction to reflect that this is still a work in progress. 137.222.34.156 (talk) 14:21, 12 October 2016 (UTC)

Ublock apparently has a new spnosor (Wikipedia)
" (however the uBlock Origin add-on can fix this problem).[30]" When did Wikipedia become a sponsor and advertising medium for Ublock? How can I advertise my software here on Wikipedia??? — Preceding unsigned comment added by 2606:A000:FD41:7D00:A5D8:D104:C30C:9376 (talk) 23:23, 4 February 2017 (UTC)
 * What is the problem? I'm not aware of any other browser fix for this problem, so I don't see any favouritism here. ··gracefool &#128172; 22:36, 7 February 2017 (UTC)

WebRTC Protocol vs Google implementation
I believe this page incorrectly associates WebRTC the protocol with a Google's implementation. This would be similar if the page for HTTP contained only details for Internet Information Services but excluded Apache HTTPD and nginx.

I would love to help update this page to actually reflect what WebRTC is, both the W3C APIs and the IETF RFCs. This page should also document all the implementations that exist aiortc, Pion WebRTC, GStreamer etc.. There are also WebRTC focused servers like Janus and Jitsi. These do have a dedicated article, but it would be great to help readers understand it all more

I have a conflict of interest I contribute to Pion WebRTC so I am heavily interested in pushing away from a WebRTC monoculture. I would love to share everything I have learned from writing a WebRTC implementation! I think this page could be really great for people learning WebRTC, there isn't a great resource out there for how everything works currently. Lots of documentation of browser APIs, but not the actual protocols Sean-Der93 (talk) 06:05, 19 September 2019 (UTC) Sean DuBois (Sean-Der)

Brendan Eich
"Brendan Eich called it a "new front in the long war for an open and unencumbered web"." Who cares what Brendan Eich says and does this really belong in the main description? Jone951 (talk) 21:49, 22 November 2019 (UTC)

Remove OpenWebRTC from article?
OpenWebRTC seems to have been abandoned around 2016. Since then only a handful of commits, and last commit in 2018. Maltimore (talk) 09:29, 10 April 2020 (UTC)


 * Done Maltimore (talk) 08:54, 15 April 2020 (UTC)

WebRTC demo: client and host in game play
Here is some external content (of mine) that a developer might find useful. I'm proposing a new bullet under the external links section. This live demo (a game) has a WebRTC signaling process facilitated by a Heroku app using socket.io.

Video to get a sense for connecting the client to the host: [Https://www.triquence.org/videos?network-connection https://www.triquence.org/videos?network-connection]

Host page with the Puck Popper game loaded: [Https://www.triquence.org/?7b https://www.triquence.org/?7b]

Client page: [Https://www.triquence.org/client?m https://www.triquence.org/client?m]

A page with discussion on the use of socket.io and WebRTC: [Https://www.triquence.org/multiplayer https://www.triquence.org/multiplayer]

Jmiller333 (talk) 20:14, 2 February 2024 (UTC)


 * Thanks, but per WP:EL we shouldn't link any of this. Wikipedia is not a link directory or a how-to site. MrOllie (talk) 20:15, 2 February 2024 (UTC)