This would allow us to compute most of needed data from the server. We could use x-vercel-ip-timezone from Vercel by default with the option to override from the client if desired. Some links about this: [https://twitter.com/leeerob/status/1551273570713698304/photo/1](https://twitter.com/leeerob/status/1551273570713698304/photo/1) [https://github.com/vercel/examples/blob/main/edge-functions/geolocation-country-block/middleware.ts](https://github.com/vercel/examples/blob/main/edge-functions/geolocation-country-block/middleware.ts) [https://vercel.com/docs/concepts/edge-network/headers#x-vercel-ip-timezone](https://vercel.com/docs/concepts/edge-network/headers#x-vercel-ip-timezone) <sub>From [SyncLinear.com](https://synclinear.com) | [CAL-901](https://linear.app/calcom/issue/CAL-901/rfc-consider-adding-timezone-to-request-headers)</sub>
This would allow us to compute most of needed data from the server.
We could use x-vercel-ip-timezone from Vercel by default with the option to override from the client if desired.
Some links about this:
https://twitter.com/leeerob/status/1551273570713698304/photo/1
https://github.com/vercel/examples/blob/main/edge-functions/geolocation-country-block/middleware.ts
https://vercel.com/docs/concepts/edge-network/headers#x-vercel-ip-timezone
From SyncLinear.com | CAL-901