Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

collect very coarse client location in usage DB #7

Open
warner opened this issue Apr 4, 2018 · 0 comments
Open

collect very coarse client location in usage DB #7

warner opened this issue Apr 4, 2018 · 0 comments

Comments

@warner
Copy link
Collaborator

warner commented Apr 4, 2018

We don't record IP addresses in the mailbox server (except for error cases, for which I haven't found an easy way to filter them from the exception messages), but I'd kind of like to know roughly how many users we have coming from different countries. At some point I'll probably move the mailbox server from it's current location (a Linode box, probably in texas somewhere), and it'd be good to choose a hosting provider that minimizes mediam round-trip latency to clients.

I don't think we could measure this directly: clients don't include any timestamps in their server messages, and their clocks could be horribly skewed anyways, and there aren't any server messages that clients react to right away (they respond to the other client's PAKE message with an encrypted VERSION message, but they also run the entire PAKE calculation inbetween, which takes a while and would bias the results pretty badly). And besides I don't want that level of detail.

So I'm thinking of feeding the client's IP address into one of those offline geolocation tables (looks like the MaxMind DB might work), and storing the country code in the Usage record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant