[tor-bugs] #5485 [BridgeDB]: Think about ways to give out non-blocked bridges without making it too easy to enumerate all bridges

[Tor Bug Tracker & Wiki]

#5485: Think about ways to give out non-blocked bridges without making it too easy
to enumerate all bridges
----------------------+-----------------------------------------------------
 Reporter:  karsten   |          Owner:  aagbsn  
     Type:  task      |         Status:  assigned
 Priority:  normal    |      Milestone:          
Component:  BridgeDB  |        Version:          
 Keywords:            |         Parent:          
   Points:            |   Actualpoints:          
----------------------+-----------------------------------------------------

Comment(by sysrqb):

 (This is actually unlikely related to #6396)

 How are blocked bridges currently being determined? I know they're listed
 in a file that BridgeDB parses.

 I think from a usability point of view, b) and c) aren't mutually
 exclusive. I'm not clear about how the "fixed set of five bridges" would
 be decided. Is it per /24? Per email address? I think b1 is a reasonable
 fall-back, if we can't find any that are unblocked.

 In order of end-user expectation (I'm assuming here):
 1) Three usable bridges
 2) Three possibly reachable bridges, but note the ones that may be blocked
 3) Inform the user there are no available bridges for their use
 4) Three likely blocked bridges

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