I was looking at my change log, and I had an agreement and a comment on one observation. iSpot had the chronological order reversed from the order I thought I’d made them in. I assumed a memory lapse, but perhaps it was further evidence of inaccurate timestamps in iSpot.
JoP is not only bright,
She travels faster than light.
Went out one day
In a relative way,
Returned on the previous night.
Handy if you’ve missed the flowering of a rare plant, I suppose…
Joking apart, it shows that the gremlin hunt still has some way to go. Even if iSpot is taking times from other sources, they should surely be linked to automatically-synched systems - so should only be out by exact hours if the source is in another time-zone?
Even with sunset at Kirkwall being half-an-hour earlier than here, I would have expected there still would have been traces of twilight left. On the other hand, down here, if it wasn’t for car headlights killing my night vision, I can just about see at night from the light pollution, and that won’t be same in rural Orkney.
A possibly related thing I’ve noticed is that the changes tracker sometimes shows things as new that happened shortly before, rather than after, the last visit to the changes tracker. That could be another symptom of incorrect timestamps.