Sat, Jan 5
Fri, Jan 4
Thu, Jan 3
Tue, Jan 1
Partially implemented in the related commit.
Tue, Dec 25
For now it will report to admins only.
This was the original behavior but iirc somebody requested this to be changed early on. I'll wait for consensus but if nobody else comments here I'll just implement this
Alright, this seems to have been caused by the server being overloaded at the time the vote happened. The user clicked the vote button multiple times and the server took a couple seconds to process the request, leading to double votes. This can be fixed by "locking" voting from a certain user to a post/comment for a couple seconds (via redis) after the voting endpoint is called. Or maybe outright rate-limiting.
Investigating this right now. It doesn't seem to be the double-voting issues we've had early on with @pembo210's broken mouse
Sep 25 2018
Sep 4 2018
Aug 22 2018
Jul 5 2018
And who would it report to? Mods? Admins?
Jul 4 2018
Typo on the commit description.
Jul 2 2018
The difference between level 0 (founder) and 1 (sr. admin) would be nil, maybe level 0 can have access to edit some deeper site configurations that are still in the database (like defaults, and invite mode). Level 1 could have all the admin privileges.