Opened 7 years ago

Closed 5 years ago

#7524 closed task (invalid)

Design a system for applying an allocator strategy

Reported by: aagbsn Owned by:
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: #7520 Points:
Reviewer: Sponsor:

Description

The social distributor should support a configurable allocator strategy that will assign bridges to an account by implementing a policy that may take into consideration datapoints such as:

  1. age of the account
  2. history of bridges allocated to this account
  3. filtering of bridges assigned to this account
  4. frequency of requests for bridges

For example, an allocator strategy might be as simple as "give no more bridges to a user whose bridge was blocked"
Alternately, "give fewer bridges to accounts correlated with more blocking events than 1 standard deviation above the average"

A good idea might be to evaluate multiple simple strategies simultaneously and see which strategies are more effective.

Child Tickets

Change History (1)

comment:1 Changed 5 years ago by isis

Resolution: invalid
Status: newclosed

This is not really part of the design of the rBridge paper, and not blocking the accounts of users who should be blocked according to rBridge (i.e. they locked themselves out of the system by too many of their bridges getting blocked) would completely invalidate the design of social distributor, as well as invalidate the bridge censorship results shown in the graphs in that paper.

Note: See TracTickets for help on using tickets.