<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
(not yet a bug, becauase I am not sure where this fits!)<br>
<br>
<b>Should we store true geo (country level) somewhere in Firefox?</b><br>
<br>
1. We are starting to deploy services (and services integrations)
both by locale and by geographic entity. For example, Feature X is
GEO-US only, but supports many languages.<br>
<br>
Currently, at least these services generate and use user geo Country
Codes.<br>
<br>
- <a class="moz-txt-link-freetext" href="about:newtab">about:newtab</a><br>
- <a class="moz-txt-link-freetext" href="about:home">about:home</a><br>
- (Heartbeat First Impressions)<br>
- (others)<br>
<br>
2. They all calculate the code the same way (using
mozilla/GeoDude). <br>
3. They cache the data at different intervals.<br>
<br>
Issues:<br>
- the caching is different times / schedules. User 'country' can be
inconsistent between services inside Firefox.<br>
- Our server gets hit more often than it should, as O(Users *
Services), rather than O(Users). <br>
<br>
Some expected complaints (and answers):<br>
1. storing GEO potentially exposes user info. Claim / Ans: Right
now sites are doing this by IP already.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>