Question for API consumers about server-side filtering

[glacials]

Hi everyone! With GitHub Actions's ability to schedule cron jobs, it looks like we can finally have an API that contains the exact sets in Standard without having to go off-platform and with no filtering required.

The problem is, timezones. Currently when you consume the What's in Standard? API, you are (or should be!) filtering the sets array down to Standard sets by comparing enter / exit dates to your local time.

But I don't know your local time, so an auto-updating API will have to either assume some semi-arbitrary timezone, or let you supply your timezone as an input. Since I'm still (again?) committed to staying on GitHub Pages, that'll mean something like:

whatsinstandard.com/api/vx/UTC−1200/standard.json
whatsinstandard.com/api/vx/UTC−1100/standard.json
whatsinstandard.com/api/vx/UTC−1000/standard.json
whatsinstandard.com/api/vx/UTC−0930/standard.json
whatsinstandard.com/api/vx/UTC−0900/standard.json
whatsinstandard.com/api/vx/UTC−0800/standard.json
whatsinstandard.com/api/vx/UTC−0700/standard.json
whatsinstandard.com/api/vx/UTC−0600/standard.json
whatsinstandard.com/api/vx/UTC−0500/standard.json
whatsinstandard.com/api/vx/UTC−0400/standard.json
whatsinstandard.com/api/vx/UTC−0330/standard.json
whatsinstandard.com/api/vx/UTC−0300/standard.json
whatsinstandard.com/api/vx/UTC−0200/standard.json
whatsinstandard.com/api/vx/UTC−0100/standard.json
whatsinstandard.com/api/vx/UTC/standard.json
whatsinstandard.com/api/vx/UTC+0100/standard.json
whatsinstandard.com/api/vx/UTC+0200/standard.json
whatsinstandard.com/api/vx/UTC+0300/standard.json
whatsinstandard.com/api/vx/UTC+0330/standard.json
whatsinstandard.com/api/vx/UTC+0400/standard.json
whatsinstandard.com/api/vx/UTC+0430/standard.json
whatsinstandard.com/api/vx/UTC+0500/standard.json
whatsinstandard.com/api/vx/UTC+0530/standard.json
whatsinstandard.com/api/vx/UTC+0545/standard.json
whatsinstandard.com/api/vx/UTC+0600/standard.json
whatsinstandard.com/api/vx/UTC+0630/standard.json
whatsinstandard.com/api/vx/UTC+0700/standard.json
whatsinstandard.com/api/vx/UTC+0800/standard.json
whatsinstandard.com/api/vx/UTC+0845/standard.json
whatsinstandard.com/api/vx/UTC+0900/standard.json
whatsinstandard.com/api/vx/UTC+0930/standard.json
whatsinstandard.com/api/vx/UTC+1000/standard.json
whatsinstandard.com/api/vx/UTC+1030/standard.json
whatsinstandard.com/api/vx/UTC+1100/standard.json
whatsinstandard.com/api/vx/UTC+1200/standard.json
whatsinstandard.com/api/vx/UTC+1245/standard.json
whatsinstandard.com/api/vx/UTC+1300/standard.json
whatsinstandard.com/api/vx/UTC+1400/standard.json

From a technical and human-effort standpoint that's actually not a problem at all since the API is already generated at build-time, so I'd just generate it 38 times. But it adds some confusion to consuming the API, including some pitfalls like having to account for daylight saving time.

So I'm curious, if you consume the API does this matter to you? Do you prefer to have things in the right timezone? Are you okay with a little off, like a few hours? How about a lot off, like 26 hours?