This is a classic programming challenge. Below is a likely scenario of what is happening:
- The date is converted by budgetbakers server as a timestamp "at midnight UTC".
- Any client that is leftwards of UTC (minus something) will see the timestamp localized to its timezone. So midnight UTC -3 is interpreted as 21:00 the day before.
This is not wrong in absolute terms. It's wrong in terms of UX. The good way would be:
- Provide an option to set the default time and timezone for imported dates;
- Default this timezone as the client timezone;
- Allow for parsing of ISO 8601 dates with time and timezone (that would allow tinkers to decide exactly which timestamp they want to provide).
It's probably half a day effort for a standard web developer.
This is a classic programming challenge. Below is a likely scenario of what is happening:
- The date is converted by budgetbakers server as a timestamp "at midnight UTC".
- Any client that is leftwards of UTC (minus something) will see the timestamp localized to its timezone. So midnight UTC -3 is interpreted as 21:00 the day before.
This is not wrong in absolute terms. It's wrong in terms of UX. The good way would be:
- Provide an option to set the default time and timezone for imported dates;
- Default this timezone as the client timezone;
- Allow for parsing of ISO 8601 dates with time and timezone (that would allow tinkers to decide exactly which timestamp they want to provide).
It's probably half a day effort for a standard web developer.