Change History

No worries. I don't know where the thread is myself, and it might only have been visible to script developers.

As I mentioned, I doubt that a challenge like this can be published with today's guidelines, but I might be wrong. But if it's not allowed, there is no point in "setting the standard", otherwise I do agree with you.

The best solution in my personal opinion would be something like this:
For every found cache by the user, figure out the last find date prior to his/hers. Return all logs (inclusive) between that date and the users found date. Example for user A:

(date, username, logtype)
2016-10-06 B found
[b]2016-10-05 C found
2016-10-05 A found
2016-10-05 D note
2016-10-04 D DNF
2016-10-03 E found
2016-10-03 F found[/b]
2016-10-02 G found
Would return the bolded ones.

EDIT: We would however need to look into how fast we can make this, and the memory consumption. Imagine a user with 50000 finds. It could easily become half a million rows returned.

No worries. I don't know where the thread is myself, and it might only have been visible to script developers.

As I mentioned, I doubt that a challenge like this can be published with today's guidelines, but I might be wrong. But if it's not allowed, there is no point in "setting the standard", otherwise I do agree with you.

The best solution in my personal opinion would be something like this:
For every found cache by the user, figure out the last find date prior to his/hers. Return all logs (inclusive) between that date and the users found date. Example for user A:

(date, username, logtype)
2016-10-06 B found
[b]2016-10-05 C found
2016-10-05 A found
2016-10-05 D note
2016-10-04 D DNF
2016-10-03 E found
2016-10-03 F found[/b]
2016-10-02 G found
Would return the bolded ones.