Live data from Hacker News

Hello Firefox, this is Chrome calling

blog.chromium.org

91–100 of 183 posts

Re: Hello Firefox, this is Chrome calling

#91
post #63

Earlier quoted context omitted.

Encrypting data certainly increases the barrier to entry for spying.

No it doesn't, it means if somebody doesn't really want to spy on you they just will not waste their time....

Isn't that the definition of a raised barrier? Even if it isn't very high.

Re: Hello Firefox, this is Chrome calling

#92
post #85

Earlier quoted context omitted.

Not saying Skype is perfect (it isn't), but WebRTC by itself doesn't come close to being a Skype substitute. While stability for particular client-side bits (media, transport, etc) will now now fall on the browser vendor, you're still going to depend on another service for all the niceties (media and signaling relay, contacts, presence, history, etc), and they could screw it up just as badly as Skype, or worse. Skype…

You're correct that you'll depend on another service for all the niceties, but I for one am super excited about decoupling all of those services from the connection itself. Hopefully it'll lead to a lot more competition and innovation in the space.

At the very least I hope it forces IM apps like Skype and Facetime to support WebRTC (that is possible for native apps, too, right?) so that in the future we get interoperability between them.

Wouldn't it be nice if WebRTC pushed video-calling into becoming like e-mail, and you could take to anyone, regardless of what "video-calling app/service" they are using?

Re: Hello Firefox, this is Chrome calling

#93
post #66

Yes, please, please, please kill Skype. Kill it mercilessly. Using it has been the worst experience I've ever had with an application. I've been in a long distance relationship for a few years now and Skype has sadly been our main mode of video communication. The app crashes when I search chat history, can take upwards of 90+% of my CPU, literally forcing me to shut down every other application I have running. The fo…

I use Sococo's Teamspace, which I help write as my job. We're cognizant of cpu usage especially on laptops and pads. We're ok now, and our next release will use substantially less CPU. Our codecs are WebRTC-derived, and its pretty stingy with memory and cpu so that's cool.

Confused; is it inappropriate to suggest other startup's products here? WebRTC etc are good technology, that's why we picked them up. All the issues mentioned by the poster are important to all of us in this space. Sococo is responsive, constantly doing customer experience surveys and trying to address quality.

Do you imagine Sococo is some giant corporation? Its a startup like so many here. I was the 3rd person in the company, the 1st Software Engineer, so I'm pretty proud of the progress we've made in the last couple of years. There are a lot of big players in our market, and we've done a good job of beating them technically even though we're small.

Re: Hello Firefox, this is Chrome calling

#94
post #30
post #20

Earlier quoted context omitted.

Unfortunately, if this page is accurate, DataChannels don't really work yet: http://www.webrtc.org/chrome#TOC-Data-Channels- A shame, because I have a use in mind for them. :)

It works on some alpha release of both Firefox and Chrome. There are already some file transfer apps if you're curious, although I haven't tested myself: https://github.com/lindstroem/FileTransfer and https://github.com/peer5/sharefest . Also, the folks from easyrtc ( https://github.com/priologic/easyrtc ) have already started working on adding DataChannels to their library.

I tried this less than a week ago on Linux platform and was unsuccessful. I am also waiting on this feature, want to do some cool stuff :-)

Re: Hello Firefox, this is Chrome calling

#95
post #88

Earlier quoted context omitted.

You fail to get my point, why do you think that that the US has has little issue with allowing encryption to be used these days? How strong is your 'locked' box? It's only a bunch of 1s and 0s.

Unless the NSA/FBI/whatever is decades ahead in mathematical research from what is common in academia, or has computers that are many orders of magnitude faster than what we have today, well encrypted data is basically random data to anyone who lacks the keys. That's a pretty tough locked box.

And who packages that box?

Re: Hello Firefox, this is Chrome calling

#96

Earlier quoted context omitted.

The one key element of a Skype Killer, which isn't present in WebRTC, is a prescribed infrastructure to support these communications. Skype is made up of users who actually are, usually, unaware that they are also routing calls for other users. Even more precarious (and absent from WebRTC) are the skype SuperNodes, which no one is going to redo for WebRTC. The things which we love about skype, most notably the direct…

It would seem to greatly lower the cost of building a Skype-killer, though, and that's a pretty big deal.

Sort of. Now you don't need to build client software, but that was never the real prowess or power of Skype, it was always the infrastructure.

Think of it this way. Skype has 2 things that WebRTC doesn't: Signaling and a Directory. Without those two components, you just have a phone without a phone number :/.

Lower barrier, yes. Easy? No, there are still significant costs.

Re: Hello Firefox, this is Chrome calling

#97
post #66

Yes, please, please, please kill Skype. Kill it mercilessly. Using it has been the worst experience I've ever had with an application. I've been in a long distance relationship for a few years now and Skype has sadly been our main mode of video communication. The app crashes when I search chat history, can take upwards of 90+% of my CPU, literally forcing me to shut down every other application I have running. The fo…

By your own admission, Skype is the best video communication platform that exists but is far from perfect. It's hard to disagree. Why isn't someone creating something better?

Re: Hello Firefox, this is Chrome calling

#98

Earlier quoted context omitted.

Yeah, but what does it matter then? I can stand outside the bank safe all day and stare at it but unless I know the code I'm still just looking at a locked box. Strong encryption is the same way, feel free to stare at my VPN stream all day, it won't help you.

You fail to get my point, why do you think that that the US has has little issue with allowing encryption to be used these days? How strong is your 'locked' box? It's only a bunch of 1s and 0s.

Maybe because they realize that treating encryption as munitions is totally unenforceable and strong encryption is basically public knowledge at this point? I know everyone has a cousin in the NSA that knows someone who knows someone who knows how to break Triple DES in 3 minutes, but there's no evidence that is actually real. Even if the NSA or whoever is years ahead of the public in math research (they aren't, BTW, these people would make far more money in the private sector) there's still no evidence to the smartest mathematicians and cryptographers that this is the case. The biggest threats to encryption is parallel computing, weak security, and possibly quantum computing in the future, not a backdoor.

Re: Hello Firefox, this is Chrome calling

#99
post #48
post #32

Earlier quoted context omitted.

This is possible with current technology: $(document).keypress(sendKeypressInfo)

Won't the Same Origin Policy limit the exposure via ajax?

The Same Origin Policy can be overridden by the site accepting the connection (http://www.w3.org/TR/cors/), so assuming that site is hosted by the attacker it wouldn't be helpful. If the site used (and the browser supported) a Content Security Policy (http://www.w3.org/TR/CSP/) you could restrict such outgoing connections.

Re: Hello Firefox, this is Chrome calling

#100
post #16

Looks neat. One thing I wonder about tech' like this, is that it is encrypted from you to the service, but there is no assurance of privacy. Someone who runs a service like this can easy drop in on your calls and ease-drop. Which is a legitimate concern if someone wanted to use this either in a corporate environment or for very private calling (e.g. husband and wife, doctor and patient, etc). No current video tech' r…

My understanding is that it's possible to not have a 'service' and instead form connections from one person directly to another. That decentralization would be a privacy boon.

Unfortunately, no: both browsers need to exchange volatile information to establish the connection. It includes information like how to traverse NATs to get to the other browser. You need some more centralized service to exchange that information and bootstrap the process.
Post reply on HN