[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5273 [Firefox Patch Issues]: Update TBB design doc for 2.3.x-alpha



#5273: Update TBB design doc for 2.3.x-alpha
----------------------------------+-----------------------------------------
 Reporter:  mikeperry             |          Owner:  mikeperry                    
     Type:  defect                |         Status:  new                          
 Priority:  major                 |      Milestone:  TorBrowserBundle 2.3.x-stable
Component:  Firefox Patch Issues  |        Version:                               
 Keywords:  MikePerry201207       |         Parent:                               
   Points:                        |   Actualpoints:                               
----------------------------------+-----------------------------------------

Comment(by gk):

 Replying to [comment:19 mikeperry]:
 > Replying to [comment:18 gk]:
 > > Choice is good but do users really want to have per site choices
 regarding ad-trackers and DNT? What makes you believe so? And why does
 that not already exist as an add-on and all anti-tracker add-ons are
 working globally (at least all I can currently come up with)? If there is
 even a tiny demand for a specific wish there usually seems to exist an
 add-on for it on AMO.
 >
 > Yeah, that's exactly the scenario I want to avoid. We should add
 warnings/text in the addon store UI that tells the user that addons can
 harm privacy and anonymity... Since Adblock Plus is the most popular addon
 in the world, supporting some form of user choice per-site might be a
 decent compromise? It might prevent the userbase from fragmenting itself
 globally.. It's a tricky tradeoff, though.

 Okay, I've been thinking about that idea for a while now. I guess a user
 choice per-site might indeed be a decent compromise. But only if there is
 really a substantial chance to get the user deploying a global adblocker
 etc. to use the per-site model (but that's just a matter of proper
 "incentives", right?). I don't know what means would be appropriate to
 reach that goal yet. A warning/text in the add-on UI seems not bad to me
 as a starting point. I would be happy to have some code that is binding
 the adblock/ghostery or whatever global logic to the URL bar domain by
 default as well if the per-site checkbox is checked and ignoring it
 otherwise. And, of course, it would be nice to have some usability study
 evaluating this approach.
 > At any rate, the key thing I want to communicate with the context menu
 is that all of the global privacy options that alter browser behavior need
 to be in a per-site menu (if they exist at all), rather than global
 choices.
 Yes, that's a reasonable fallback if users want to alter the default
 behavior. Agreed.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5273#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs