[tbb-bugs] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Dec 8 15:42:03 UTC 2017

#23136: moat integration (fetch bridges for the user)
 Reporter:  mcs                        |          Owner:  brade
     Type:  defect                     |         Status:  new
 Priority:  Very High                  |      Milestone:
Component:  Applications/Tor Launcher  |        Version:
 Severity:  Normal                     |     Resolution:
 Keywords:  TorBrowserTeam201712       |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:  Sponsor4
Changes (by mcs):

 * status:  needs_information => new


 Replying to [comment:21 antonela]:
 > We have been reviewing this flow a little bit more.
 > Here is the user flow approach we end up with:
 > ...
 > Let us know what do you think!

 Unfortunately, Kathy and I did not know that you were planning to do more
 design work. We have already proceeded down a different implementation
 path (using the overlay approach, as we discussed). Since we are already
 well past our engineering deadline for this task, I don't think it makes
 sense to switch right now to the inline flow that you have designed. Also,
 our implementation includes most of what you suggested. Here is some info
 about our flow:
 * When the user clicks the "Request another bridge" radio button, a
 CAPTCHA prompt is shown. This prompt is overlaid on top of the other
 content that is in the settings panel.
 * If the user cancels without completing the CAPTCHA, the prompt is closed
 and a "Request a Bridge…" button is displayed beneath the "Request another
 bridge" radio button.
 * If someone who is interacting with the CAPTCHA prompt enters an
 incorrect response, we keep the same CAPTCHA but display the following in
 red below the CAPTCHA image: "The solution is not correct. Please try
 * After the CAPTCHA is solved and a bridge is obtained, the overlay
 disappears and the bridge info is displayed beneath the "Request another
 bridge" radio button. We also change the button label to "Get a  New

 This is very similar to what you proposed, so I think we are actually in
 agreement on most points. Hopefully we will have a test version available
 soon, although we have a BridgeDB dependency and we are not 100% finished
 with the Tor Launcher code either.

 In the meantime, please let us know if you would like us to make some
 screenshots. I know it is difficult to visualize the interface based on a
 textual description.

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

More information about the tbb-bugs mailing list