10,952 karma · joined July 7, 2010
(fc8bc5bfd9dd7b50671510a083330d1180894c5e) (0c25c202625ab9aceb0d795d938c852db6251faa) (6cd80fa7687113be3f2db8968957ad618e7d0407)
It works just fine, there simply isn't an icon for it. Use the Google Voice extension. This is noted all up and down this thread. The actual process of GV calls being handed off to Talk/Hangouts is the same it's been for years. A tiny icon went away until they flesh out the rest of GV into Hangouts (I have very bold predictions about why they took away the call button temporarily, but I'm keeping that to myself for now)
2. but they haven't done it yet.
Look, I'm willing to take back everything I said, but quite frankly, Google Voice hasn't improved since I started using it 4 years ago and I'm not holding my breath.
"Super star agile developers"? That's the best FUD you can put in my mouth? By the way, you might look up the "superstar" developers behind Wayland: Ctrl+F "The developers": http://en.wikipedia.org/wiki/Wayland_(display_server_protoco... ..... Huh, that's sure interesting.
Nowhere did I imply that Wayland was better than X simply because it was newer. That's the exact kind of FUD I'm talking about from the X.org crowd that fears Mir and Wayland because they don't understand: the current technologies, the future technologies, the evolution of Wayland, the DEVELOPERS behind Wayland AND the HUGE list of flaws in X.
Stop spreading uninformed FUD, do not put words in my mouth and don't accuse me of being a hipster.
With WebRTC, a proper signaling protocol (they're probably using Jingle anyway, give the RTC history and the fact that RTC relies and builds on Jingle), and a relay server, there's not much to need to do to interoperate if they wanted to enable it.
This whole notion that they "can't" make it interoperable or that it will "slow them down", is complete and utter shit. Slow them down on what? All I've seen so far is more merging of GoogleTalk+GooglePlus and a rebranding effort. Basically no new feature, no integration with Google Voice, no seamless integration with SMS.
Reminds of a project posted to HN a while back that had taken someone a month. I replicated it in the evening using all open source, open protocol components instead of being stubborn and falling prey to NIH syndrome.
1. Use the Google Voice extension. Enter number. Press 'dial'. Your Hangout is now ringing, huzzah
I mean, if what you're saying is true, they just broke all Google Voice incoming calls for all users (hint, they didn't).
Works perfectly, no idea why "the dialer went away" means "incoming calls no longer work", but hey, it's Google and it's FUD, should I bother trying to be surprised?
Don't get me wrong, Google fucked their one big chance to integrate Voice, Video, SMS and IM. With Hangouts, I should be able to "Call Someone" and have it negotiate video if we both have and want video, or it should use the next available medium. If both users use Hangouts, then send a Hangout IM. And if not, finally fall back to Google Voice/VoIp/SMS.
The users shouldn't have to ask themselves, "wait, does Bobby have Hangouts?" ever. That is literally the number one issue with G+!
If only that were true, I'd have spent even less time this week on meta-HN-drama.
And I reject or seriously, seriously, seriously lament that "discourse has moved to twitter". That sounds like the opener to George Orwell's 2084 or something.
Of course, Skype's bot won't implement WebRTC.
They'll implement the proprietary blend that they told no one they were working on until everyone else was making serious progress with the implementation that everyone else collaborated on...
http://html5labs.interoperabilitybridges.com/prototypes/cu-r... [hm, they've actually put some money where their proposal is, I'll have to check into this more]
One is a feature designed to allow them to check URLs, fetch thumbnails, etc. The other is a very pivotal core decision in how Skype works.
Skype has always been primarily node-to-node. Doing p2p connections like that required signaling/directory services. In the past, users' computers were used for that functionality. After their purchase, Microsoft transitioned those signaling/directory services to the cloud.
At worst, this gives Microsoft the ability to see who is calling who, I'll grant that. Worst case scenario, you can't negotiate via STUN and UDP hole punching or UPnP port forwarding, then you will get stuck with TURN and that will route through Microsoft's servers.
So, unless someone has proof of a connection that should have established peer-to-peer and instead the call itself was routed through MS's servers TURN style.... then can we ALL please stop repeating this obnoxious rumor about MS eavesdropping on all Skype calls. Or worse yet tying it to some URL lookup service?
(Honestly, if you'd just asked, I would have been assumed this would have been the case anyway)
http://www.youtube.com/watch?v=_FjuPn7MXMs
Take that and extrapolate. Doesn't seem that "crazy" really. Compiz and KWin both already have window animations you're describing. There was even a Wii-head-tracking plugin for compiz that would give your desktop a third perspective dimension. (Moving your head would reveal the edges/bits of the other windows underneath higher ones).
It'd be a neat demo, but it sounds like a nightmare for daily usability, etc.
Then you take that transaction to an offline computer or source and sign it, take it back to the online computer and transmit it to the network. /roughly, see the other link for better information