News for hackers. Stuff that matters.
Re:Chrome Privacy by mikewest on Saturday September 24, 2011 @05:42PM (#3034404)
The main dev on the WebRequest API sits right behind me, and is making steady progress. It's the first synchronous extension API that interacts with the network stack, and it's a nontrivial effort to get it running. I can assure you, however, that making life hard for privacy extensions is the exact opposite of what we're being paid to do.

Look at the progress on privacy-related APIs over the last year: WebRequest is coming along nicely, WebNavigation and ContentSettings are feature complete and in the final stages of polish, and Proxy went out to stable in Chrome 13. Privacy and Clear just landed in experimental, and we're iterating on them rapidly.

(Details on the state of each are available at http://code.google.com/chrome/extensions/trunk/experimental....)

Re:Chrome Privacy by qjz on Saturday September 24, 2011 @08:42PM (#3034710)
Is it possible to restrict requests to the host in the URL I'm visiting? XSS, DNT, etc. become much less of an issue when you can block all external resources requested by a page.
Re:Chrome Privacy by mikewest on Saturday September 24, 2011 @08:51PM (#3034723)
That will be possible with the WebRequest API, yes: http://code.google.com/chrome/extensions/trunk/experimental.... For example, you'd be able to intercept and block network requests from a particular tab that didn't hit the same domain.

The API in experimental now, so download a dev release of Chrome/Chromium, enable experimental APIs via `about:flags`, and start filing bug reports. :)

Re:Chrome Privacy by mike-cardwell on Sunday September 25, 2011 @07:12AM (#3035592)
FWIW, this is already possible with Firefox by using the RequestPolicy addon.
Re:Chrome Privacy by notbitter on Saturday September 24, 2011 @10:29PM (#3034884)
Glad to hear it. Chrome is great in every other way.