I am happy to show a screenshot of the email chain between myself and our lawyers back in July.
Do your emails specifically detail the changes the Guardian discusses, and an October 13-ish timeline for publishing them? Maybe you were planning on changing the ToS since July, but that doesn't mean anything in relation to the content, nature, or timing of the change you just released.
we use a legacy maxmind geoip database so we can put the whisper in a general location. that is so inaccurate as to be laughable... The % of all Whispers which are tagged as somewhere in the middle of Kansas because we don't really know where they are (but we know they are in the US) is very high.
We want to know where a user is in a general sense for things like tracking timezone so when we send pushes we know not to send pushes at 3 in the morning. you'd be surprised how often device timezone may not always match with physical location.
So, "Chill everyone, we get 'USA' and just plot it randomly." then "Our location algorithm is accurate enough that we override the user's timezone selection, despite 'USA' spanning 6-9 timezones and multiple Daylight Savings permutations."
Comments
Do your emails specifically detail the changes the Guardian discusses, and an October 13-ish timeline for publishing them? Maybe you were planning on changing the ToS since July, but that doesn't mean anything in relation to the content, nature, or timing of the change you just released.
So, "Chill everyone, we get 'USA' and just plot it randomly." then "Our location algorithm is accurate enough that we override the user's timezone selection, despite 'USA' spanning 6-9 timezones and multiple Daylight Savings permutations."