Opened 11 months ago

Last modified 2 months ago

#31875 new task

BridgeDB should consider a user's location

Reported by: phw Owned by:
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Normal Keywords: s30-o23a4
Cc: phw, cohosh Actual Points:
Parent ID: #31280 Points: 10
Reviewer: Sponsor: Sponsor30-must

Description knows the user's physical location and should consider it when returning bridges. For example, if somebody in country X asks for an obfsN bridge but BridgeDB knows that only obfsN+1 works in X (e.g., by consulting the result of #28531), it should return obfsN+1.

Ideally, we would do this for all of BridgeDB's distribution mechanisms. We could also do it for email – if the user emailed bridges+CC@…. As I understand it, we cannot do it for moat because BridgeDB doesn't get to see the user's IP address in this case.

Child Tickets

Change History (2)

comment:1 Changed 11 months ago by teor

I wonder if you can get the user's IP address in an X-Forwarded-For header using moat?

I also wonder what happens when your GeoIP databases are out of sync (with each other, or with the real world political control of networks). For example, what happens when IP addresses move between countries?

comment:2 Changed 2 months ago by cohosh

Cc: cohosh added

cohosh cc'ing myself on sponsor 30 work

Note: See TracTickets for help on using tickets.