HN user
Director of Collaboration @Symphony
WebRTC Expert since 2010, Founder @RTC__news, @WebRTCfest, @WebRTCstats, @Bistri
Surfing, Windsurfing, Diving, Photography, Audiophile
Probably the best WebRTC app made with Electron! Congrats to Feross & DC!
Guys, would you like to present at the next SF WebRTC Meetup on April 28th? http://www.meetup.com/SF-WebRTC/events/229430038/
Posted (again) on RTC.news: http://www.rtc.news/posts/os4JyZWT6iLR2jMua/job-apple-is-sti...
Great! Just added to RTC News too: http://www.rtc.news/posts/zbzwy4zt3CNt5XSRw/bimodal-multicas...
Just posted on RTC.News: http://www.rtc.news/posts/XmdjfGSergLgKMYEK/capira42-web-bas...
Feel free to "Show" on http://rtc.news too
Cool! feel free to post the news on http://rtc.news ;)
Good job! I just shared your work to the RTC community: http://www.rtc.news/posts/aRZANoKJyDaRw4SQo/encrypted-webrtc...
Added to RTC News: http://www.rtc.news/posts/TnaFbZox3qegCg4kB/webrtc-job-at-cr...
Great! Feel free to post it on www.rtc.news
Hi,
The solution really depends on the details of your use case and the acceptable delay it would require. You can go for a P2P mesh topology, or you can just use streaming media servers in the backend ; in that case you will use WebRTC from your web app to the server, then the server route/transcode/optimize the distribution of the stream to the clients.
A few resources: - https://tokbox.com/platform/beta-programs/ - http://www.streamroot.io - https://www.peer5.com - https://webtorrent.io - http://www.dialogic.com/en/landing/webrtc.aspx - https://jitsi.org/Projects/JitsiVideobridgePerformance
Reminds me John Hiesey's demo at SF WebRTC Meetup at Twilio https://www.youtube.com/watch?v=sNi92K0ddEw
Just added to RTC.news: http://www.rtc.news/posts/4Gt7n6dtCf6sPg2cx/show-rtcn-helpin...
Added to RTC News: http://www.rtc.news/posts/xrSeZ5Tp7ssdejPNm/user-screenshare...
Mesh vs Mixer vs Router: https://webrtchacks.com/webrtc-beyond-one-one/
Firefox multistream and renegotiation for Jitsi Videobridge: https://hacks.mozilla.org/category/webrtc/as/complete/
WebRTC has already started its industrial phase, the largest platform powered by WebRTC today is probably Facebook: https://www.linkedin.com/pulse/facebook-silently-released-we...
This what we know about the technology behind Facetime: https://cdn.andyet.com/webrtc-reports/facetime-report.pdf
Apple is already participating to the WebRTC Working Group at W3C: http://www.w3.org/2000/09/dbwg/details?group=47318&public=1
Tip from the Apple team: just ask! Seriously! >> https://forums.developer.apple.com/content?query=webrtc >> https://bugreport.apple.com
A way to contribute getting WebRTC supported by Safari: http://www.webrtcinwebkit.org/blog/2015/3/28/bringing-webrtc...
In the meantime, a few workarounds: http://www.makeuseof.com/tag/heres-make-internet-explorer-sa...
WebRTC on IE & Safari > Today, no other choice than a Plugin. As far as I know, only one enable WebRTC locally, unbundled from any platform: http://Skylink.io/plugin
WebRTC Platform as a Service (a-z): - http://Bistri.com (uses Skylink Plugin) - http://Tokbox.com (plugin for IE) - http://Sightcall.com (driver for IE & Safari) - http://Skylink.io (plugin for IE & Safari) - http://Twilio.com - http://Voximplant.com
Looking for a list of all the WebRTC solutions? https://webrtcindex.com
Introducing https://test.webrtc.org - A tool that helps users help themselves.
Real time communications can be challenging: browsers, network, hardware and operating systems need to successfully perform complex tasks for a call to be successful.
Understanding what goes wrong, often on the far end, is challenging for developers.
test.webrtc.org captures media from the microphone and camera at various resolutions and sends it back to itself through a TURN relay server, all encrypted.
Once the media is back, Javascript code looks for various issues such as black video frames and silent audio as well as testing network capabilities.
If an issue is discovered, users can easily download or upload the report. When the latter is chosen, a unique URL is created, which can be used when filing issues.
We encourage developers to take the code from github and integrate similar functionality in their own UX. This should be part of any "support request" flow. We also encourage developers to contribute!
This project is known as Loop: https://wiki.mozilla.org/Loop/Try_Loop
a free full-stack WebRTC solution, with backend servers, clients, API.
* Mozilla provides the OAuth 2.0 authentication, the signaling server, and the clients
* Tokbox (Telefonica) provides STUN/TURN server http://tokbox.com
* Nexmo provides SMS service / MSISDN gateway http://nexmo.com
Disruptive Analysis has now published the WebRTC Industry Status & Forecasts Report, 2014 Edition. It is the most detailed study on WebRTC, based on primary research and detailed quantitative market modelling. It extends the analysis the original report issued in February 2013 and several interim updates.
The report contains the most detailed & comprehensive forecasts on WebRTC adoption available from any analyst firm:
* WebRTC-capable device numbers, by PC/phone/tablet/M2M & geographic region * Consumer WebRTC users for standalone & embedded voice/video * Business WebRTC users for contact centres, UC and app-embedded communications * Telco WebRTC users for VoIP/VoLTE extension, Telco-OTT services & cable/IPTV * M2M/IoT estimates for WebRTC integration
The research has presented a range of new findings:
By 2019, there will be more than 6bn WebRTC-supporting devices & 2bn+ individual users (around 60% of the total Internet population). Some will be regular users, for example where it is embedded into a primary communication app or service, while others will just use it occasionally – perhaps in a B2C customer service & support context. http://webrtcstats.com/wp-content/uploads/2014/10/WebRTCstat...
Enterprise use of WebRTC is the most widely-commercialised today. But there is more action in new cloud-based offers for collaboration and conferencing, rather than upgrades of the existing installed base of UC/PBX “seats”. There are also new platforms emerging to integrate voice/video into apps and workflows. This means that WebRTC will “dis-unify” aspects of business communications, even while it helps other moves towards UC continue. http://webrtcstats.com/wp-content/uploads/2014/10/WebRTCstat...
By the end of 2015, there will be more mobile devices supporting WebRTC than PCs. This is part-driven by Chrome and Android Webview, but also WebRTC integration into apps using 3rd party frameworks or SDKs.
More than 10 telecom operators have commercial offers involving WebRTC in some way, with many more in development or nearing launch. Although IMS-integration of WebRTC gets most airtime, the majority of deployments are standalone Internet/app/OTT-style or even integrated with TV/cable platforms. Overall, telcos could have up to 500M WebRTC users by end-2019 http://webrtcstats.com/wp-content/uploads/2014/10/WebRTCstat...
The new WebRTC sample repo is at http://github.com/GoogleChrome/webrtc.
View samples from the repo live at http://googlechrome.github.io/webrtc.
Safari might support WebRTC in the coming months. Apple appointed 4 members to the WebRTC Working Group: http://www.w3.org/2000/09/dbwg/details?group=47318&public=1
Since the signaling is not part of the standard, on purpose, you can choose whatever you like (XMPP, SIP...) or create you own solution. On the server side, TURN is implemented to go through the NATs, the firewalls, that helps.
Try a WebRTC Video Conference in one click : http://blog.bistri.com/webrtc-demo
You have ideas with WebRTC, try the Bistri APIs : http://developers.bistri.com