@jacobrossi @domenic @JeremyLaurenson @imlazar Someone should write an ORTC polyfill for WebRTC (a la IDB polyfill on WebSQL)
-
-
Replying to @wycats
@wycats@jacobrossi@domenic@imlazar And so, developers will have to code specifically to detect Edge vs everyone else... as usual.1 reply 0 retweets 1 like -
Replying to @JeremyLaurenson
@JeremyLaurenson@wycats@domenic@imlazar that'd be true if Google wasn't also implementing ORTC... please stop this FUD2 replies 0 retweets 0 likes -
Replying to @jacobrossi
@jacobrossi@JeremyLaurenson@wycats@imlazar where are you getting that claim? Not on chrome status, no intent to implement.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@jacobrossi@JeremyLaurenson@wycats@imlazar why would Google be authoring the spec if they had no intention to implement?1 reply 0 retweets 0 likes -
Replying to @mattpodwysocki
@mattpodwysocki@jacobrossi@JeremyLaurenson@wycats@imlazar Google is big, lots of people do different things, often not coordinated.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@jacobrossi@JeremyLaurenson@wycats@imlazar have you talked to Justin Uberti about it since he's a spec author?2 replies 0 retweets 0 likes -
Replying to @mattpodwysocki
@mattpodwysocki@jacobrossi@JeremyLaurenson@wycats@imlazar no, I'm just acting on public information, like all other authors here.4 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@mattpodwysocki@jacobrossi@JeremyLaurenson@imlazar And W3C is not even responsible for the web protocol (just DOM API)1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@domenic@jacobrossi@JeremyLaurenson@imlazar which is nothing more than a shim layer from WebRTC to ORTC. Correct me if I am wrong2 replies 0 retweets 0 likes
@mattpodwysocki @domenic @jacobrossi @JeremyLaurenson @imlazar That's an implementation strategy.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.