[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7520 [BridgeDB]: Design and implement a social distributor for BridgeDB

#7520: Design and implement a social distributor for BridgeDB
-------------------------+--------------------------------------------------
 Reporter:  aagbsn       |          Owner:     
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:     
Component:  BridgeDB     |        Version:     
 Keywords:               |         Parent:     
   Points:               |   Actualpoints:     
-------------------------+--------------------------------------------------
Changes (by aagbsn):

 * cc: ioerror (added)


Comment:

 ioerror pointed out that we may not want to do step 3. Ideally, the
 implementation would be flexible so that upon deployment one can choose
 from various strategies and not provide a blueprint for gaming the
 distributor.

 For example, accounts should not get dropped if a bridge is detected by
 DPI and blocked. Since we may not know how a bridge was blocked, we might
 prefer a strategy whereby users more strongly correlated with blocking
 events are isolated rather than removed.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7520#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs