-# Take the current and previous day's logs. If I look once a day (DreamHost time),
-# this should catch everything with some overlap. TODO: Avoid the overlap?
-# Requires sth more sophisticated to track what I've already seen.
+# Take the previous day's logs. If I look once a day (DreamHost time), this
+# should catch everything with no overlap. I previously included the current
+# day's logs, but I now think the difficulty of maintaining an accurate sense of
+# usage in the presence of overlap is a greater evil than up to a day of extra
+# latency. I might find a better solution in the future.