W3C home > Mailing lists > Public > public-tracking@w3.org > November 2012

RE: Agenda for 07 November 2012 call - V01

From: Fred Andrews <fredandw@live.com>
Date: Mon, 5 Nov 2012 22:34:47 +0000
Message-ID: <BLU002-W2252C602301C7834C6BAD3EAA640@phx.gbl>
To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>

> 4. 
        Discussion of new general approach to exceptions sketched in

 >    Core changes:
 >        - Main responsibility of Exception UI is with the sites
 >        - Sites 'store' exceptions via API in browser
 >        - Browser may validate exceptions with their users to
        ensure they are OK with it
 >    Question:
 >       - Feedback?
 >       - OK to pursue this approach from now on?

What a great advancement!  Exceptions now become opt-out.  When a user visits a website their
UA is filled with exceptions that the user is expected to opt out of.

Users should not have to deal with a load of marketing crap from each an every website wanting
them to add exceptions.  The user agent is their known friend, and lets not twist it otherwise.  A UA
will likely want an interface with user trusted third party curated ratings of websites, and will want
to give users other options such as 'don't even touch this website' or 'this website works fine without
this tracker, don't believe their marketing crap' etc and they are not going to get this from the website
itself, now are they?

Here's an idea, make it opt-in.  When these APIs are called the exceptions are added to a pending list
for the user to review and opt-in - a small icon on the UI, that can be well ignored.


Received on Monday, 5 November 2012 22:35:14 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:00 UTC