Task 4.2 Put components together as a design based on the "Salmon" reputation bridge distribution framework, highlighting the missing and underspecified pieces.
- We need some anti-sybil signup step, which in the original paper was requiring an established (more than n months old) Facebook account. What is a workable option for us, engineering-wise and social-community-wise?
- How dangerous is the social graph? How much to remember? Where to store it?
- False positives, where a bridge gets blocked but not because it got assigned to a bad user.
- False positives, where a bridge goes down but we call it blocked.
- How to adapt to multiple countries? Or regions really.
- Do we need to batch the reassignment events? Otherwise the people from the old bridge all get the new bridge.
- Predicting better adversary strategies.
Edited by Roger Dingledine