Slashdot Mirror
Google Chrome To Have Real-Time Communications
kai_hiwatari writes "Last month, Google released an open-source project called WebRTC which aims to enables Real-Time Communications capabilities in the web browsers through simple JavaScript APIs. Now, they have taken the first step towards having WebRTC built into Chrome. With WebRTC, developers will be able to build voice and video applications using nothing more than HTML and JavaScript. This is a powerful technology which can challenge services like Skype."
If this is done through javascript then is it possible to start running these services automatically without user oversight? Could lead to some interesting spyware opportunities.
Looking up WebRTC's license right now, says it's open source. Can't wait for the other browsers to pick up on this. I just hope it warns users before allowing access to the camera and mic.
"When information is power, privacy is freedom" - Jah-Wren Ryel
I wonder if there's anything from a technical point of view that would prevent this from working on mobile devices, such as iPads and Android phones and tablets? If they're looking for wide adoption, I'll bet that getting it running on everyone's mobile or tablet would make it a killer app.
I know Google has this whole web-based vision where everything is accessed through the browser, but I'd rather see this as a stand-alone app. I like my web browser to browse the web, my softphone to make calls, my email client to check my email, and my word processor to process my words. Heck, Windows 8 will be written in HTML/Javascript, and Gnome Shell is written in Javascript, so I don't expect to have to wait too long for a native app. I just can't wait for the cloud bubble to burst so we can go back to having traditional software again.
Funny may not give karma, but +5 Informative never made anyone snort coffee out their nose.
"We noticed that your face was turned away during our advertisement. Let us play that again for you..."
With WebRTC, developers will be able to build voice and video applications using nothing more than HTML and JavaScript. This is a powerful technology which can ...
... implement some truly awesome spy technology. Implemented both by site owners and site hackers.
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
I'd rather not have video compression implemented in slow Javascript (even if it is getting faster). I also imagine that you can't access web cam peripherals from Javascript without some kind of browser extension, though I don't know.
Without Wesley Data doesn't get turned on
That put a horrible picture in my head and I threw up a little in my mouth.
Google won't add basic features like proxy settings that aren't shared with the operating system, and a master password for your saved passwords, but they keep packing these kinds of features in.
I really don't understand why they're making the kinds of decisions they're making. It seems so random, like they stuff in whatever shiny they like, and then come up with weak justifications for skipping the rest.
Javascript doesn't have Peer to Peer communication. Normally you're not allowed to make JS connections to anything but the server the JS came from. And even then, you can only make HTTP connections. And you certainly can't listen for incoming connections from peers. And then there's the lack of access to audio and video inputs.... So, there are many reasons why WebRTC is required.
Yeah - I'm really interested to see if WebRTC combined with the Mozilla "Verified Email" incubator project gets us away from the server owns my identity world of today.. https://wiki.mozilla.org/Identity
Seems like then all you need the servers for are to issue short-lived identity certificates and host public keys to verify the certs. Then we could do some interesting browser to browser tech without having servers to authenticate every step.. Some interesting P2P tools could emerge. Hmm.