Skype For Microsoft Edge Will Work From the Browser, No Plug-Ins Required
We mentioned a few months back Microsoft's beta of a browser-based intrerface to Skype. Now, reports Engadget, Skype will be able to work without a plug-in (as was required for the beta). However, it will work -- at least at first -- only with Microsoft's Edge browser. The latest Windows 10 Insider Preview build comes with Object RTC API. That's the element that allows real-time audio and video communication without the need for any installation not just for Skype for Web and Outlook.com, but also for other WebRTC-compatible services. To note, Chrome, Firefox and Safari all support WebRTC standards, but it's unclear if and when Skype will enable a plug-in-less experience for those browsers, as well.
Please don't run executable code inside my document viewer.
kthxbye
I suspect well be getting the always on, talk to your web browser functionality so you dont have to click anything when you want ot make a call. You can just say "skype, call my mom" and and bing, skype will inform microsoft, the nsa, and your mom that you want to talk. And when you dont want ot talk to mom, skype will make sure any naughty keywords you use while sitting at your computer are also promptly forwarded to the NSA as well.
With Windows 10 at ~9% market share of desktop OS's, Edge is currently at ~2%. Incorporating Skype isn't going to help Edge attract many more users, if any, since it still is not compatible with many websites and crashes more than other browsers. I use Edge solely to open my Outlook.com mail since the Mail app in Windows 10 won't do the job. The whole Windows 10 situation is quite fubar, it seems to me.
Unfortunately, Microsoft has completely ruined Skype, and they will probably never be able to recover the users they lost. My grandparents got locked out when Microsoft started requiring a Microsoft ID, so I switched them to gchat. Plugins are easy enough to install and unless Microsoft fixes the ridiculous Microsoft ID requirement, I can't see many people using Skype ever again. Let's face it, Microsoft is just not competive with the new generation of tech companies and the only reason they lasted as long as they did is because they had a near monopoly, maintained by compatibility issues, for decades.
I've multiple Skype accounts since ages. Never been forced to require a Microsoft ID. Stop spouting bullshit.
Short version: Microsoft is going to bake in the security holes so low that it will be exploitable in epic ways.
Just like every time Microsoft decides to embed this stuff at a level nobody else can ... and there will be much pwning.
Lost at C:>. Found at C.
Extinquish? I knew you weren't playing with a full deck of cards, but still...
You are partly correct.
WebRTC has 2 parts: protocols & codecs (RTCWeb WorkingGroup at the IETF) and the browser API (WebRTC at the W3C). Al lot of the people are the same people.
All parts of WebRTC was already being worked on before Microsoft really got involved. And Microsoft wanted a more low level browser API than the other WebRTC browser API that was already being worked on. Microsoft wanted this for things like Skype.
Eventually a new community group (not workgroup) was formed at the W3C to work on a new API called ORTC.
The working group at W3C that works on WebRTC have committed themselves to adopt ORTC. So now WebRTC has 2 APIs, only Microsoft has an implementation of ORTC. Firefox, Chrome/Chromium and Opera have an other. And it looks like WebKit/Safari will get WebRTC support too.
The older API is easier to use, because the newer API is more low level, but there are or will be Javascript libraries which will present you with one API which should work with both.
Having a low level isn't such a strange thing any more in browser/webdevelopment land, because as it turns out you can have Javascript libraries which abstract the stuff most don't need to know. Because a lot of times webdevelopers use those anyway, to abstract the differences between browsers.
It's starting to look like more and more browser APIs will be more low level, so high level APIs can be built on top and changed more easily.
Lots of people/companies who work together at the W3C have now basically made this policy:
https://extensiblewebmanifesto...
New things are always on the horizon