extension

All posts tagged extension

webrtcH4cKS: ~ Chrome Screensharing Blues – preparing for getDisplayMedia

Posted by Philipp Hancke on June 14, 2018
Posted in: Technology.
Tagged: , , , .
3 comments
What happens when you screen share on a computer that's already sharing your screen

The Chrome Webstore has decided to stop allowing inline installation for Chrome extensions. This has quite an impact on WebRTC applications since screensharing in Chrome currently requires an extension. Will the getDisplayMedia API come to the rescue?

Screensharing in Chrome

When screensharing was introduced in Chrome 33, it required implementation via an extension as a way to address the security concerns. This was better than the previous experience of putting this capability behind a flag which lead to sites asking their users to change that flag… that got those sites an official yikes. ...

Continue Reading

Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+

webrtcH4cKS: ~ WebRTC Externals – the cross-browser WebRTC debug extension

Posted by Philipp Hancke on July 28, 2017
Posted in: Guide.
Tagged: , , , .
4 comments
Garden Tools

I am a big fan of Chrome’s webrtc-internals tool. It is one of the most useful debugging tools for WebRTC and when it was added to Chrome back in 2012 it made my life a lot easier. I even wrote a lengthy series of blog post together with Tsahi Levent-Levi describing how to use it to debug issues recently.

Firefox has a similar about:webrtc page which shows the local and remote SDP for each page as well as a very useful grid of ICE candidates. But unlike Chrome it does not show the exact order of API calls or nice graphs obtained from the getStats API. I miss both features dearly. Edge and Safari don’t support similar debugging helpers currently either. ...

Continue Reading

Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+

webrtcH4cKS: ~ How to stop a leak – the WebRTC notifier

Posted by Chad Hart on August 4, 2015
Posted in: Guide.
Tagged: , , , , .
11 comments

The “IP Address Leakage” topic has turned into a public relations issue for WebRTC. It is a fact that the WebRTC API’s can be used to share one’s private IP address(es) without any user consent today. Nefarious websites could potentially use this information to fingerprint individuals who do not want to be tracked. Why is this an issue? Can this be stopped? Can I tell when someone is trying to use WebRTC without my knowledge? We try to cover those questions below along with a walkthrough of a Chrome extension that you can install or modify for yourself that provides a notification if WebRTC is being used without your knowledge. ...

Continue Reading

Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+

webrtcH4cKS: ~ How to use WebRTC and Chrome Extensions to Call a Browser When it is Not Open (Konstantin Goncharuk)

Posted by Chad Hart on April 8, 2014
Posted in: Guide.
Tagged: , , , , , .
5 comments

Ring! Sometimes you need an alert to get your attention. Traditional phone systems make this easy – if someone calls you your phone rings. The traditional telephony model assumes the called device is always on an available to ring and this is how it generally works across analog phones, mobiles, VoIP phones, and even desktop calling replacements like Skype. The challenge in the web model is that you can no longer assume the remote device is available to run your program’s ring command. Even if the called party has a browser open, it does not mean they have a tab running your app.  This means you need to find some other means of telling the called party to go to your URL. That can be limiting for a lot of apps. Fortunately there are solutions for this. ...

Continue Reading

Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+