That 'almost' is a lot bigger than you're making it out to be.
With a hypothetical "WebRTC video chat" service, in order to chat with "any of my facebook friends", I need to:
- Give all my data on my Facebook friends to the service in question. (Let's assume for the moment that it's a benevolent hypothetical chat service and I don't have to give up a lot)
- Invite one of my friends.
- Hope that my friend accepts the service accessing their information in the same way (A very big hurdle if it's a service they've never heard of)
Or I could just use Skype, that they're already on.
... It's still a wash in my opinion. There's no account required at all for a WebRTC application. I can send you a link on any service and you're a click away from video chatting with me. The Social Auth integration was just an example of how easy it would be to build off of existing user bases.
With a hypothetical "WebRTC video chat" service, in order to chat with "any of my facebook friends", I need to:
- Give all my data on my Facebook friends to the service in question. (Let's assume for the moment that it's a benevolent hypothetical chat service and I don't have to give up a lot) - Invite one of my friends. - Hope that my friend accepts the service accessing their information in the same way (A very big hurdle if it's a service they've never heard of)
Or I could just use Skype, that they're already on.