I have encountered some bugs related to time zone, when using cheap surveillance cameras, for which the time zone/ Daylight Saving Time doesn't always work prop

I have encountered some bugs related to time zone, when using cheap surveillance cameras, for which the time zone/ Daylight Saving Time doesn't always work properly. The displayed time inside the video feed may be off by one hour / also different than the time the notification email. I have encountered some bugs related to time zone with docker in which the displayed time in the displayed console log output is different from the local time, which is kind of confusing when reporting issues on github. But if your code isn't done properly and have filters based on local time you need remember to pass the correct time zone configuration when shipping with docker. When reading blog posts / social media / messaging apps you need to be aware of the "responded at xxxx time" usually is local relative to the poster, which may cause confusing anachronism, when trying to know if the message is before or after an event. (If you get the time via an API, it usually is UTC, but when you are scrapping you need to be careful). Also with DST you always need to check that your alarm clocks have the correct date so they change correctly. Semi-related, on a dual booting linux/windows, my windows machine after reboot is usually still in the past at the time when it was last shut off, which prevents logging into Fusion360 (without signaling why the server refuse the connection), until my windows get it's time at the right time by synchronizing with the ntp time server.