marcovezzale This has been discussed earlier, and is a bit of a logical paradox. This photo was seemingly taken in Venezuela at 11:06 (15:06:10 - 0400). Considering Thailand is +11 hours ahead of Venezuela, that would correctly make the time 10:06 PM in Thailand, so it's not specifically "wrong".
The debate would perhaps be, should the date simply display as is, with no regards to where the image is being viewed from? That would seem somewhat logical, although that would mean images could look like they were taken in the future, or several hours ago, even if they were taken just a minute ago, all depending on where the visitor is browsing from. In that regard, the date would simply display as "2023-09-29 15:06:10", regardless of where the viewer is. This of course might make sense for photos with EXIF, but it doesn't make sense for normal file dates that were created on server, where the visitor would want to the data of the file relative to their own time.
Then of course, there are other complications with EXIF dates. It's not clearly defined if EXIF dates are GMT or local, and only new devices have the property
OffsetTimeOriginal. Google Photos even uses the GPS coordinates to add an offset to the DateTimeOriginal, based on timezone of the GPS coordinates (I see there are many complaints about this).
In either case, it's not specifically wrong, but there might be room for changes. I had a long discussion with someone about this here: