Advertisers get hands stuck inside HTML5 database cookie jar

There are so many ways to coerce a GUID out of a browser: single pixel images, cache headers[1], etc. It's not feasible to implement disclosure control[2] retroactively in web standards.<p>1. <a href="http://sourcefrog.net/projects/meantime/" rel="nofollow">http://sourcefrog.net/projects/meantime/</a> 2. <a href="http://groups.csail.mit.edu/mac/classes/6.805/articles/privacy/sweeney-thesis-draft.pdf" rel="nofollow">http://groups.csail.mit.edu/mac/classes/6.805/articles/priva...</a>

One thing that truly irks me about mobile browsers is that there is no way (as far as I can tell) to trick them out with add-ons and Greasemonkey scripts to make them behave as you prefer.<p>As a user I should be able to white- or black-list who can create databases on my mobile device, but so far this kind of control is not possible with the default browsers.