Linked by Kroc Camen on Sat 29th May 2010 20:41 UTC
Permalink for comment 427239
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-12-02
The W3C Device APIs provides a way for HTML and JavaScript to access hardware such as web cameras and microphones. The web has already exposed GeoLocation and this takes things a step further, allowing for new kinds of innovative web-based apps that have so far been restrained to Flash and native apps for a lack of any other way of doing it. Not having to download and install anything, nor worry about platform compatibility, will ensure that moving this sort of functionality to the web is a good idea.
This part of the article is where I disagree with you fully. Why on earth would you want to allow HTML to control hardware? That will lead to nothing but trouble in the long run, as has already been shown through history. Why give another tool to the masses to invade privacy?