[tor-bugs] #5761 [TorBrowserButton]: Decide if it's safe to pass the Dooble around the Tor Community

[Tor Bug Tracker & Wiki]

#5761: Decide if it's safe to pass the Dooble around the Tor Community
---------------------------------+------------------------------------------
    Reporter:  mike123           |       Owner:  mike123
        Type:  enhancement       |      Status:  closed 
    Priority:  normal            |   Milestone:         
   Component:  TorBrowserButton  |     Version:         
  Resolution:  invalid           |    Keywords:         
      Parent:                    |      Points:         
Actualpoints:                    |  
---------------------------------+------------------------------------------

Comment(by mike123):

 Hi Mike, you specified these needs:

 "Hey Textbrowser,

 I think you misunderstood me wrt to the level of commitment from us.

 Our commitment extends this far:

 1. Once Dooble meets
 https://www.torproject.org/projects/torbrowser/design/#security, we'll
 stop telling people not to use it with Tor. Right now, it does not meet
 even these most basic requirements.

 2. Once Dooble meets
 https://www.torproject.org/projects/torbrowser/design/#privacy to an
 equal or greater degree than our Firefox implementation (click the links
 in that section for details) with the same degree of functionality
 (especially the ability to use Google docs and plan youtube videos
 *without* plugins, and the ability to interpret and apply
 HTTPS-Everywhere rules), we'll consider begin devoting Tor development
 resources to making an official Dooble-based bundle.

 Unfortunately, we have no Tor development resources to devote up until
 that point.
 "

 Just one comment: youtuble plugins can be already disabled and furthermore
 to refer to the https everywhere addon, I would say this is an addon, is
 it shipped with the Torbowser? So be fair from the method to compare
 browsers and not all the enhancements for it.
 We will look at yout two links in greater details, but what exactly do you
 miss from them in dooble?
 We should open up tickets or have a list and plan, when the long way could
 be see some light in the tunnel. As now two developers closed this ticket,
 and not the community has anything said besides rrandom, who give side
 details sponsored by google to destroy innovation, this might be done by
 third party people.

 https://sourceforge.net/projects/torbrowser/

 this domain has been shifted over to your sf.net name. Do you want to use
 it?
 I think it is not a good initiative to use it for the firefox bundle, so I
 let your name as admin there in and ask some others e.g. the russion pre-
 owner of the domain if there are ideas for a vidalia qt plugin. This means
 to change the vidalia mainframe to a webfram and compile it as a tab-
 plugin like it has been done in this app: http://interface.sf.net

 this approach does not even need dooble. Here is a simple qt frame host to
 host the plugin:
 http://interface.svn.sourceforge.net/viewvc/interface/communicator/guichat/trunk
 /plugin-host/

 For the https everywhere functionality there will be a feature request in
 dooble.
 Ok, Dooble versions will evolve and we might look later, though it is not
 dooble, it is the mind of people taking part.
 Besides disabling youtube plugins and https everywhere nothing else has
 been listed, in case the privacy and security links are fullfilled. here
 the referring dooble support tickets (see link above) have been done.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5761#comment:32>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online