Content
@
0 reply
0 recast
0 reaction
Varun Srinivasan
@v
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)
6 replies
5 recasts
42 reactions
Varun Srinivasan
@v
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.
0 reply
0 recast
9 reactions
Satoshi Tomatomoto
@tomato.eth
I still wish we could have more custom control over location. Some people might want to give their city, while others only want to specify a coarser location like state, country, or even continent.
1 reply
0 recast
3 reactions
dusan.framedl.eth
@ds8
this broke frames.js, cc @df, @stephancill, @dwr.eth getting `Unrecognized enum value USER_DATA_TYPE_LOCATION for enum UserDataType` for anyone that has set/updated their location
0 reply
0 recast
4 reactions
eirrann | he/him🎩🔵
@eirrann.eth
This is in reference to whether someone sets a location in the profile? FC isn't collecting user location data itself in any way, correct?
1 reply
0 recast
1 reaction
meta-david🎩 | Building Scoop3
@metadavid
Does that mean Foursquare-type functionality can’t be built on Warpcast?
0 reply
0 recast
0 reaction
--Dir3--
@dir3
How does standardizing location data to city-level affect user privacy?
1 reply
0 recast
1 reaction