WordPress.com gets it consistently wrong, Twitter has it right: posting time stamps
Posted by jpluimers on 2022/11/15
UTC and time zones are both hard, especially with respect to scheduling.
The easiest would be to schedule things and store the time zone offsets together with the timestamp, just as ISO 8601 has UTC-relative time zone designators, or alternatively store the region in addition to the timestamp (which can be more user friendly).
When a scheduling system uses local time for schedules, you can expect these will adhere to your local time when the schedule becomes in effect.
So I schedule my posts for 06:00, 12:00 and 18:00 local time during weekdays.
Look what happens:
- [Archive.is] Jeroen Wiert Pluimers on Twitter: “Pro-tip for @wordpressdotcom : fix the scheduler so when you schedule in your local time zone, there is no shift during daylight saving time changes. I schedule all my posts to appear at 06:00 12:00 and 18:00 in my local time. 1/… “
- [Archive.is] Jeroen Wiert Pluimers on Twitter: “That works fine during winter time, which is ~5 out of 12 months, for example https://t.co/banrMebk2A 2/… “
- [Archive.is] Jeroen Wiert Pluimers on Twitter: “However 7 out of 12 months, they get posted at 07:00 13:00 and 19:00 local time, for example 3/3… “
Via [Archive.is] Colin Nederkoorn on Twitter: “Pro tip: Don’t schedule recurring meetings in UTC if you live in a place with daylight savings.… “ (which I do not agree with, see my post UTC and ISO 8601, or GTFO).
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a Reply