<div dir="ltr">That sounds great, lets move that to a separate toolkit module if we can.<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 3, 2015 at 10:04 PM, Felipe G <span dir="ltr"><<a href="mailto:felipc@gmail.com" target="_blank">felipc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>We already store this info locally!, stored by the search service. It stores it at the pref
browser.search.countryCode, and I guess all these consumers could use it. It has some logic to expire the info and
re-retrieve that would need to be revised to see if it fits well with the other
consumers.<br><br></div><div>One thing to pay attention is to not let features disappear for users who have received them and then travel abroad and get their geo updated.<br></div><div><br>About the privacy concern, you are talking about storing it locally on users' machines, right? If so that does not cause any concerns IMO. What leaks users' info is of course sending that information to servers. (but that's a separate conversation)<br><br></div><div>Cheers,<br></div>Felipe<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Aug 3, 2015 at 3:18 PM, Gregg Lind <span dir="ltr"><<a href="mailto:glind@mozilla.com" target="_blank">glind@mozilla.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div 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>about:newtab</a><br>
- <a>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>
</div>
<br></div></div><span class="">_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
<br></span></blockquote></div><br></div>
<br>_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
<br></blockquote></div><br></div></div></div>