#28: WebRTC Identity Provider Selection
Discussions
Comment by @annevk May 6, 2014 (See Github)
The other new primitive here is the <iframe>
not visible from the page. You cannot do that yourself in that way.
Comment by @mnot Sep 30, 2014 (See Github)
Discussed at London F2F; @dherman and @domenic to take lead. Need a few weeks to digest / discuss.
Comment by @domenic Jan 7, 2015 (See Github)
Opened https://github.com/w3c/webrtc-pc/issues/172 to get the ball rolling.
Comment by @mnot Jan 8, 2015 (See Github)
Discussed in NYC; issue has been raised.
OpenedMay 6, 2014
Via @annevk:
http://dev.w3.org/2011/webrtc/editor/webrtc.html#identity-provider-selection
Mozilla intent to implement
The API design doesn't make sense to me, and perhaps we could help with that, but I think that's a lesser concern next to the idea of an entirely new identity primitive. This is worth us all understanding and making sure it fits well with the rest of the platform.
I need to do a lot of reading to really get this. The Mozilla intent to implement gives a nice one-paragraph overview, but the entire WebRTC world is pretty far outside my area of expertise. Any help would be welcome.