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

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
--------------------------------------------+------------------------------
 Reporter:  mcs                             |          Owner:  brade
     Type:  defect                          |         Status:  needs_review
 Priority:  Very High                       |      Milestone:
Component:  Applications/Tor Launcher       |        Version:
 Severity:  Normal                          |     Resolution:
 Keywords:  TorBrowserTeam201802R, ux-team  |  Actual Points:
Parent ID:  #24689                          |         Points:
 Reviewer:                                  |        Sponsor:  Sponsor4
--------------------------------------------+------------------------------

Comment (by antonela):

 Thanks @mcs for the explainer.
 So, in that case, my recommendation is to use a select

 https://trac.torproject.org/projects/tor/attachment/ticket/23136/BridgeDB%20-%20select.png
 https://trac.torproject.org/projects/tor/attachment/ticket/23136/BridgeDB%20-%20select%20-%20active.png

 I made mockups for both versions so we can see how it looks/ feels without
 development effort.

 https://trac.torproject.org/projects/tor/attachment/ticket/23136/BridgeDB%20-%20radio.png

 I'd like to suggest showing a limited qty of previous connections. Also,
 since the main action here was Request a New Bridge, I'd recommend to have
 it in the first place.

 We should check the impact of this iteration on all user flows, eg.
 Connection Error with obfs4 and back to request a new bridge.

 About the captcha, will it show after the user selects which kind of
 bridge he wants?

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