Hi. let me first say that fossil is a great tool witch is fun to use, and it really helps me with my workflow.

While playing with fossil on my eee i could not understand why my wiki edits did now show.

I was able to create new wikipages, but not able to edit old ones.

After a short while i finally noticed that the clock on my system was completly wrong because my eee had been off so long that BIOS clock was reset to year 2002(!)

I wonder if unsynced clocks might create similar or other issues for normal use, and if this problem could be solved in any way.

If the local fossil server creates artifacts with timestamp in the past, it could be useful with a warning. 

It could be other way of dealing with this, and there is also a posibility to reject this ticket and expect people to have good clocks and ntpservices on their computers. - if so, maby some lines about this in the documentations.

Thank for a great tool.

Kjell. 

Norway.

localtime on server not syncronized. "strange" behaviour in fossil