A small Utopian update - Moderator comments, repositories and the review date

I normally don't post any updates about Utopian or small changes I've made to the underlying code, and I'm not sure why. So from now on I'll probably start doing that! A couple of things have changed in the last few days, in particular concerning the upvoting of a moderator's comment and some of the code that handles the spreadsheet.

Moderator comments

Moderator comments have to be two days old before they are eligible for an upvote. Also, only one comment was upvoted at a time; more specifically when the oldest contribution in the queue is upvoted. Combining these two things together resulted in a big backlog forming, where some of the oldest comments were nearly six days old. To prevent this we have changed the following behaviour:

• If a comment is older than five days, then it will be upvoted the next time the bot votes.
• If there are multiple comments older than five days, then they will all be upvoted in a batch.

This should mean that our moderators should no longer have to worry about whether or not their comment will be upvoted! If you notice something buggy, like that your comment was unfortunately skipped for example, then please contact me on Discord (Amos#4622) and I'll see what I can do.

Repositories

When checking out the spreadsheet I sometimes noticed that repositories weren't being added properly, despite being linked in the post. To remedy this I've changed the way a repository is found. It now uses a regex to check if a GitHub repository can be found in a post's JSON metadata. If this isn't the case, then it iterates over the body of the post and tries to find the repository there. This should hopefully mean that the repository won't be missed as often as before.

Review date

Before	After

While I was changing the way moderator comments are upvoted I noticed that there were some inconsistencies in the spreadsheet. Sometimes moderators would enter their name and the review date, but then actually score the post days later. This would cause the review date to be incorrect, which could obviously mean that a moderator's comment might not be upvoted in time.

Another "problem" is that we all live in different time zones. For one moderator the date could be the 15th for example, while for another it could already be the 16th. Because of this it sometimes seemed like reviews weren't entered in a chronological order.

The final thing that I noticed was that sometimes dates were accidentally entered incorrectly. Sometimes this nearly resulted in posts not getting upvoted, because only posts that were reviewed less than seven days ago are updated in my database. For example, if someone accidentally enters "2018-08-16" instead of "2018-09-16" as the review date, then the post would not get updated.

So what did I do? Something that probably should've been implemented since the beginning. Moderators now only need to enter their name and the contribution's score. Once this is done, the contribution is moved to another worksheet and the review date is set while this happens. This should result in all review dates being in chronological order, while also making sure that comments are upvoted in a timely manner.