News for hackers. Stuff that matters.
Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by nikcub on Monday May 21, 2012 @08:57AM (#4002601)
I wrote a Chrome extension to do what you describe, it breaks almost the entire web. I am experimenting with a generic rule set with a view of forking Chrome with a better default privacy and security policy.

I totally agree that users shouldn't need to know the details, but there are some things, like third-party cookies, that needs to be explained and simplified. A bit like not clicking on an exe email attachment.

I think the equivalent could be that users white-list websites, or 'install' them, if they trust them, which allows those sites to execute third-party cookies. Everything else would be 'incognito' by default.

But I am not entirely sure what would work, hence my experimentation at the moment. I know that the answer definitely isn't DNT.

Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by Revisor on Monday May 21, 2012 @04:03PM (#4004647)
How does it break the web and what has the most breaking impact in your experience?
Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by mike-cardwell on Tuesday May 22, 2012 @05:02AM (#4006972)
I can't imagine a way that #1, #2 or #4 would be able to "break the web". Worse case scenario is they add a tiny amount of overhead. #3 might cause a tiny minority of websites to stop working, but they'd get fixed quickly if #3 was implemented.