Talk:Location fuzzing

ohiVFLNZ

hWSHou http://ezfazd.com/ hfhOJstA [url=http://dklrhx.com/]hfhOJstA[/url]

Accuracy levels
The browser geolocation API returns an accuracy radius along with coordinates, which may be quite large -- 22km for my case for an IP-based geo lookup in Firefox 3.5. If we did our own fuzzing, this would also introduce an accuracy range.

Our current name lookups have problems with this in that you may get a very accurate name for a location that's several km away from you, which is additionally confusing to users. (Over-accuracy to the "right" place is scary, over-accuracy to the "wrong" place is confusing and may mislead readers.) I'd rather have it say "San Francisco" than have it point directly to "Opera Plaza, San Francisco" when I'm somewhere between 0 to 22km away from Opera Plaza!

FireEagle uses an explicit notion of location hierarchy to return useful name info for non-exact locations.

Negativity
One big thing I want to avoid is over-focus on the negativity. Geolocation is a useful feature for our users. It is not nuclear waste material. There's only so much we have to do to protect people from themselves. --Evan 16:36, 24 December 2009 (UTC)


 * Indeed... making the experience clearer will not only help with negative reactions, it'll also help more people to notice and make use of the location feature! --brion 01:46, 25 December 2009 (UTC)

Pref discussion notes

 * checkbox below location in profile settings
 * 'Share my current location when posting notices'
 * control saving of geotag info from *whatever* source
 * default to on -- maintain current default behavior
 * stash prefs into its own table: user_location_prefs [can then be extended as necessary]

Future other improvements:
 * clean up accuracy levels on names lookups -- only use PPL and above?
 * maybe a way to strip geo tags from existing notices (cf twitter's button to do this globally)
 * not-too-invasive indicator of what's going to be posted at post time and allow one-time opt-out (per pre-post section above]