For your weekend reading: proposal on adding geolocation to the protocol. If implemented, will enable location-based clients, improved feed targeting, and better analytics

For your weekend reading: proposal on adding geolocation to the protocol. If implemented, will enable location-based clients, improved feed targeting, and better analytics
https://github.com/farcasterxyz/protocol/discussions/165

why not both? add "custom" as a geolocation type and then add `string custom` as a oneof.

i prefer the structured but extensible approach introduced in #1.

i would also highly consider h3 as a location type with it's flexible resolutions. it has served the helium ecosystem very well.

why not both? add "custom" as a geolocation type and then add `string custom` as a oneof.

i prefer the structured but extensible approach introduced in #1.

i would also highly consider h3 as a location type with it's flexible resolutions. it has served the helium ecosystem very well.

https://h3geo.org/