[tor-bugs] #5484 [BridgeDB]: Make BridgeDB give out non-blocked bridges

[Tor Bug Tracker & Wiki]

#5484: Make BridgeDB give out non-blocked bridges
----------------------+-----------------------------------------------------
 Reporter:  karsten   |          Owner:                          
     Type:  project   |         Status:  new                     
 Priority:  normal    |      Milestone:  Sponsor F: July 15, 2012
Component:  BridgeDB  |        Version:                          
 Keywords:            |         Parent:                          
   Points:            |   Actualpoints:                          
----------------------+-----------------------------------------------------
 From [wiki:org/sponsors/SponsorF/Year2]: "17. bridgedb: learn to take in a
 list of bridges blocked in a set of countries, and learn what country a
 user is asking for bridges in, and leave the blocked bridges out of the
 answer we provide.  We'll want this building block once we have bridge
 reachability testing working."

 From talking to Aaron in December:

  1. The current BridgeDB code contains a function to accept a list of
 blocked bridges by country to give out non-blocked bridges to users
 (#1837).  This code needs testing.  Also, there is a bug with how BridgeDB
 learns which country a user is interested in getting un-blocked bridges
 for, which currently conflicts with the language selection.

  2. There are at least three approaches for giving out non-blocked bridges
 to users: a) exclude blocked bridges from results, b) replace blocked
 bridges with non-blocked once, or c) include blocked bridges in results
 and write "maybe blocked" next to them.  We're currently doing a), but we
 should do c) to improve usability.  There are variants of b), e.g., b1)
 Christian suggests to give out exactly one non-blocked bridge if otherwise
 we’d give out zero bridges and b2) Roger suggests to give out the first
 three non-blocked bridges in a fixed set of five bridges.  One part of
 this deliverable should be to discuss these alternatives and agree on one
 of them that shall be implemented.

 Can we agree on some schedule when these substeps and the overall
 deliverable are expected to be done?

 Optimistically assigning to the July milestone.

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