Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13271

Closed (moved)
Open
Opened Sep 27, 2014 by Matt Pagan@mttp

Can we reverse the order on Tor Browsers' network connection questions

In Tor Browser 4.0, the number of questions we ask users who choose "Configure" is reduced from 3 to 2. Cool! Can we ask the bridge question first (seems to be more commonly used), and the local proxy question second (seems to be less commonly used)? A lot of users still get tripped up by "Do you need to use a proxy". My guess is that some users think "Of course I need a proxy. That's why I'm using Tor." I think if the proxy question and the bridge question were asked in reverse order, they would get a better feel for the types of questions we're asking in this section, and fewer users would try to select a proxy when they don't need to.

It may also help reduce the number of users who mistakenly try to configure a proxy when they don't use one if the word "proxy" were replaced with "local proxy" in the strings. It seems like this modification would only be inaccurate in cases where the user pulled an open proxy IP off a google search, in which case they should probably be using a bridge instead anyway.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13271