Live data from Hacker News

Hello Firefox, this is Chrome calling

blog.chromium.org

121–130 of 183 posts

Re: Hello Firefox, this is Chrome calling

#121
post #78
post #32

Earlier quoted context omitted.

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

$(document).keypress won't pick up keystrokes from across tabs or windows. So unless the popup is the active window, you should be safe from something like this.

Hmm, we are not talking about web page js here, we are talking about Chrome API js here. It's far more powerful.

Re: Hello Firefox, this is Chrome calling

#122
post #12

I feel like DataChannels are the best part of the WebRTC standard (or would be, if they were usable): a true p2p connection allowing transfer of arbitrary data without plugins or anything. This gives multiplayer games, file transfers, realtime chat and collaborative editors (let your imagination run wild...) and the only thing a server is required for is establishing the connection (and saving state). This functional…

This is what really excites me. I want to build a P2P DHT in the browser, basically see if I can implement something like Freenet entirely in JS.

http://webp2p.org/

Re: Hello Firefox, this is Chrome calling

#123
post #107

Earlier quoted context omitted.

That's what I meant - most probably some server support will be required. I hope ejabberd and others will address this. Until that WebRTC won't be useful for building web based XMPP/Jingle clients. Regarding codecs - most XMPP/Jingle clients support VP8 and Opus is catching up too. It's not like there are many of them around anyway. Farstream supports both if corresponding gstreamer components are present.

IIRC, ejabberd is agnostic about the XMPP messages going through, you should be able to use strophe.js to craft the proper Jingle packets from the browser's offer/answer session description. Given codec and SRTP compatibility with clients, eg GTalk (which I don't know about), you should be good to go.

But ejabberd still had to enable support for BOSH or WebSockets first. Without it Strophe was of no use. So I assumed that similar thing has to happen with in this case in order to be able to route the Jingle stream from the browser over WebRTC. If the server modifications won't be needed at all - then of course it'll simplify things. Also, clients don't always use SRTP - there can be other methods like ZRTP for example.

Re: Hello Firefox, this is Chrome calling

#124
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…

Skype has to be killed just because it's a closed non interoperable network. WebRTC can be misused as well if closed non interoperable networks built on it will pop up around like mushrooms. If WebRTC will be used to plug into federated XMPP/Jingle networks - then it'll be good.

Re: Hello Firefox, this is Chrome calling

#125
post #123

Earlier quoted context omitted.

IIRC, ejabberd is agnostic about the XMPP messages going through, you should be able to use strophe.js to craft the proper Jingle packets from the browser's offer/answer session description. Given codec and SRTP compatibility with clients, eg GTalk (which I don't know about), you should be good to go.

But ejabberd still had to enable support for BOSH or WebSockets first. Without it Strophe was of no use. So I assumed that similar thing has to happen with in this case in order to be able to route the Jingle stream from the browser over WebRTC. If the server modifications won't be needed at all - then of course it'll simplify things. Also, clients don't always use SRTP - there can be other methods like ZRTP for exam…

ejabberd already supports BOSH. The rest is up to the client since it's P2P.

Re: Hello Firefox, this is Chrome calling

#126
post #6

Well, it's encrypted, so that seems like a reasonable alternative to the potential of being spied upon when using Skype.

So is Skype. Unless there's evidence that Google couldn't be compelled to comply with US law and honor a legally binding order to intercept a Chrome video call?

Re: Hello Firefox, this is Chrome calling

#127
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…

Another really important thing Skype can do is terminate calls on regular landlines. That lets Skype plug the gap from old to new, as its network grows.

Google has the infrastructure to make it happen via WebRTC, but it would need to be integrated with accounts and payment.

Re: Hello Firefox, this is Chrome calling

#128
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?

Last I checked everyone was trying to create something better. Google, Apple, Facebook, Tencent, carriers, and many startups.

Re: Hello Firefox, this is Chrome calling

#129
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…

Have you tried Google Hangouts? I've had some success with that lately over Skype.

Meetings.io was our go-to service for a while, it was just so insanely better than Google hangouts and skype. It showed so much promise, until sadly they were acquired and now it sucks.

Re: Hello Firefox, this is Chrome calling

#130
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…

There will be a day when humans get over grunting and waving their arms to get what they want, but grunting into a computer and waving your arms isn't moving toward that evolutionary step.

Voice communication over the Internet and, well, everything else needs to stop and symbolic communication needs to flourish.

Today data plans are an add on to voice plans. Tomorrow it will flip.

Post reply on HN