Treat backwards-going timestamp as a day change. Not perfect if the clocks change...

[ypp-sc-tools.db-test.git] / yoweb-scrape.txt

diff --git a/yoweb-scrape.txt b/yoweb-scrape.txt
index b0ac2bbe383f52c2f6e0400da566ccecab1e8a60..84368c5d42eada95571c482e0c649e651a3648a9 100644 (file)
--- a/yoweb-scrape.txt
+++ b/yoweb-scrape.txt
@@ -55,7 +55,8 @@ Other things to mention:
    it's not very customisable.
 
  * It spends a while reading the whole of your chat log which can be
-   very long.  Perhaps it should be 
+   very long.  Perhaps it should be smarter (eg, bisect the log
+   to find `nearly now').
 
  * It could have lots more features in general.
 
@@ -72,6 +73,14 @@ Other things to mention:
  * I haven't decided on a final copyright licence.  You may treat this
    version as GPLv3.
 
+ * The program will become confused when the clocks change,
+   particularly when they go backwards.  This is due to the chat log
+   containing timestamps in local time without a timezone.  If this
+   bothers you, make everything be in UTC.  If it does get confused,
+   you can fix it by logging off and logging on again (perhaps waiting
+   until after the duplicated hour has passed) as that writes a new
+   date record to the log and starts a new series of timestamps.
+
 Ian.