Last modified: 2011-12-14 17:37:27 UTC
When exporting pages from a wiki where the local server clock doesn't work right and you have a data which lays in the future, e.g. year 2020, and you import this in another wiki where the clock works normal, the wiki won't change the timestamp. This is illogical since there can't be any revision made in a future date so in my opinion the timestamp should be set to the current timestamp when importing. The future timestamp is causing some confusions in the page history as well. The revision is always listed on top even if there is a newer revision when the text was updated after the import.
If the date were incorrectly in the past, you'd also end up with incorrect results. But at least when you move the data around, it stays consistently incorrect. :) Automatically rewriting the timestamp to the current time would mean that you have no way to correct the dates later (whereas if you knew how much the clock was off, you could go into the DB and correct them all in a batch). I'm not sure we can really do much better than accepting the given data, perhaps with a warning.
That might be true when you export/import an article around one wikifarm/server but not over server borders. In that case you don't even know where the import comes from not to mention about weird time settings. In this case I would expect not to end up with impossible timestamps. Especially since this is very confusing in the page history and could drive one nuts when he doesn't know about the bug and the timestamp is just a few hours/days ahead and not years.
