[PrivacyBadger] Automatically settings all domains to red

Olga Musayev olga.musayev at gmail.com
Thu Jul 3 08:59:13 PDT 2014


I'm developing the Chrome version, unfortunately, so Yan's offer doesn't
help my specific case (though I definitely think this is worth building
regardless). I read through the implementation notes and things make a lot
more sense now.

It looks like what I need to do override the action returned by the
activeMatchers object to always return "block" if the user selected the
heightened overall privacy level. This is in webrequest in checkRequest, or
else directly in onBeforeSendHeaders, and the same in popup.js.

I'll try this out and see if it works. If there are any reasons why this
would not work, I would appreciate hearing them! Thanks for the help.


On Wed, Jul 2, 2014 at 11:28 PM, Yan Zhu <yan at eff.org> wrote:

> If you're doing this for Firefox, I would happily accept a pull request
> that changes all the domains in the list for a website to some color.
>
> On 07/02/2014 11:42 AM, Olga Musayev wrote:
> > Thanks, Peter. My point however is to create gradations of privacy, with
> > different levels for different websites. On some, privacy badger would
> > run as is, while on others, there would be a modified version that
> >  blocks all third party content. This would be determined partly by the
> > user and partly by a server-side mechanism for figuring out which
> > websites are "sensitive."
> >
> > So what is needed is to selectively set all user red settings on some
> > websites, while restoring PB default controls for others, with a control
> > interface that determines the level of privacy.
> >
> >
> > On Wed, Jul 2, 2014 at 8:03 PM, Peter Eckersley <pde at eff.org
> > <mailto:pde at eff.org>> wrote:
> >
> >     One meta point: if your objective is blocking or controlling all
> third
> >     party content without depending on Privacy Badger's heuristic
> >     algorithms, you might have a better time starting with HTTP
> Switchboard
> >     (for Chrome) or RequestPolicy (for Firefox), since those extensions
> >     implement something closer to "everything red" by default.
> >
> >     On Wed, Jul 02, 2014 at 06:42:11PM +0200, Olga Musayev wrote:
> >     > I'm modifying Privacy Badger for a different project, and one of
> the
> >     > features I need is an option for the user to set all domains to
> >     red with
> >     > one click. I'm going through the code, but I'm having a hard time
> >     following
> >     > where exactly the full blocking action is taking place (popup.js
> >     348:360
> >     > has special case for cookieblock and noaction, but not for block).
> >     >
> >     > Any hint for what functions I need to use? Where does the userred
> >     > subscription get executed?
> >
> >     > _______________________________________________
> >     > PrivacyBadger mailing list
> >     > PrivacyBadger at eff.org <mailto:PrivacyBadger at eff.org>
> >     > https://lists.eff.org/mailman/listinfo/privacybadger
> >
> >
> >     --
> >     Peter Eckersley                            pde at eff.org
> >     <mailto:pde at eff.org>
> >     Technology Projects Director      Tel  +1 415 436 9333 x131
> >     <tel:%2B1%20415%20436%209333%20x131>
> >     Electronic Frontier Foundation    Fax  +1 415 436 9993
> >     <tel:%2B1%20415%20436%209993>
> >
> >
> >
> >
> > _______________________________________________
> > PrivacyBadger mailing list
> > PrivacyBadger at eff.org
> > https://lists.eff.org/mailman/listinfo/privacybadger
> >
>
>
> --
> Yan Zhu  <yan at eff.org>, <yan at torproject.org>
> Staff Technologist
> Electronic Frontier Foundation                  https://www.eff.org
> 815 Eddy Street, San Francisco, CA  94109       +1 415 436 9333 x134
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/privacybadger/attachments/20140703/9658bc91/attachment.html>


More information about the PrivacyBadger mailing list