- From: Nicholas Doty <npdoty@w3.org>
- Date: Wed, 1 Feb 2012 18:18:20 -0800
- To: Shane Wiley <wileys@yahoo-inc.com>
- Cc: Tracking Protection Working Group WG <public-tracking@w3.org>
On Feb 1, 2012, at 6:03 PM, Shane Wiley wrote: > If you feel this can be managed via the site-specific exceptions call, then I believe we're covered. It would still be useful for us to understand your use case. Depending on the design of the JavaScript API, it should be easy to check for the capability to request a site-specific exception. But I currently wouldn't expect user agents to expose that if the Do Not Track itself weren't turned on. > This was assigned to me at Brussels as I saw the site-specific exception value but there were many on the email list that were arguing for having DNT:<null> too. Hopefully someone else will speak up if they want to keep this option (but I hear you loud and clear on traffic bloat). Yes, if there are many (or any) others on the email list who have a use case here, please speak up! Thanks, Nick
Received on Thursday, 2 February 2012 02:18:29 UTC