fc-updates

FIP: Adding location to user data

After more research, we're recommending encoding location as latitude, longitude values rounded to one decimal place. 

We plan to finalize this after the next dev call. If you have feedback, please let us know in comments!

FIP: Adding location to user data

After more research, we're recommending encoding location as latitude, longitude values rounded to one decimal place. 

We plan to finalize this after the next dev call. If you have feedback, please let us know in comments! 

https://github.com/farcasterxyz/protocol/discussions/196

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

h/t to @dynemyte and @gt for spearheading this

building farcaster infra @ /neynar 🪐 | casting @ /rish

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

Senior prompt engineer. Shipped on farcaster: @larrybot, @qdau, @frames, @framesfun, /open-frames, farcasterchannels.com, farcaster.id, @mod, @search, @discove

Software developer, open source enthusiast, privacy advocate.

Clear Wallet Open-source privacy focused wallet: https://clear-wallet.flashsoft.eu/


imo 1dp feels like it’s a huge radius for example, in a city if i was trying to offer some kind of proximity based service 

using 2dp and then being able to ‘fuzzify’ your location by choice at a client level feels like a good compromise - thoughts?

rounded to one decimal works, I had not voted for it earlier because it seemed too specific to put out publicly

cc @vrypan.eth @df @rish @andrei0x309 @grin