Hello Codeforces,
My Cheater Database has just surpassed 2000 caught users! I write this blog to mark this momentous occasion — and would like to thank everyone who has sent reports, whether or not they were accepted. I would also like to thank my amazing admin team, who have also contributed to the development of the site and accepting reports.
Finally, I would like to thank whichever kind soul in Mumbai, India (according to Vercel) decided to DDoS the site the other day, your service to the community is greatly appreciated.!
Now, a few important points that I should reiterate, to ensure both the site and the Codeforces community stay as positive as possible:
- Please STOP polluting "recent actions" with blogs about cheaters. It's not really a good experience for anyone, whether new users or veterans, to open up Codeforces and see a billion new blogs about some random new GPT cheater. It also won't speed up the process of them getting banned from the site. It's just irritating, so don't do it.
- I am not a Codeforces admin, nor is cry or any other contest writer. Therefore, asking us to ban people is useless, because we simply do not have the power to do this. What we are already doing is reporting high-rated cheaters to the admins directly, and this issue is slowly getting dealt with, so please be patient.
- When writing reports, please send specific submission links. As admins, it wastes our time when users just send us links to the user's profile.
- Please refrain from writing racist comments/blogs about cheaters. Cheating is bad, full stop. No need to weaponise the cheating issue on this site to justify your racist prejudices, there is simply no way doing this can possibly be good for anyone involved.
Also, a number of users have complained that not all cheaters are showing up as cheaters on the Chrome extension. This has been fixed, and it is due to an extremely stupid bug that I let through on an old version of the extension. Please update to the latest version of the extension, and this will no longer be an issue.
Finally, if anyone wants to fix the Firefox version of the extension, please go ahead and do so, then make a PR, because I don't have a clue how Firefox extensions work.
