fc-updates

As a part of the project to publish user location to hubs, we will be migrating existing user location data to match the criteria that new location data must satisfy and publishing it to hubs. New location data is restricted to ~city level granularity and sublocalities (e.g. Brooklyn, NY) will not be presented as options. If your location is set to e.g. Brooklyn, NY we will make an attempt to translate it to the encompassing city (e.g. New York, NY).

Warpcast is now pushing (public) location data to Hubs since FIP: Location in profiles went live. 

A small change we had to make is adjust the "rounding" of locations displayed on the profile. Previously we allowed city-level (e..g New York) and sub-city level (e.g. Brooklyn). 

Going forward Warpcast will standardize on city-level. So if you previously selected Brooklyn it will now reflect as new york (sorry)

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

The reason for this change is: 

1. We had to standardize on the translation to and from lat long. Since the only data we get from other apps is lat-long, we don't know if you choose Brooklyn or New York there, since it matches both. 

2. Picking the wider location is better for helping match users that are "within driving distance" and this makes location more useful overall.