| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | Kevin114514 | 3659 |
| 3 | jiangly | 3640 |
| 4 | turmax | 3450 |
| 5 | tourist | 3408 |
| 6 | strapple | 3360 |
| 7 | Um_nik | 3354 |
| 8 | squareOf105 | 3348 |
| 9 | maroonrk | 3312 |
| 10 | idontwannadothis…e | 3191 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 153 |
| 2 | nik_exists | 151 |
| 3 | maspy | 149 |
| 4 | maroonrk | 148 |
| 5 | AmShZ | 146 |
| 6 | Um_nik | 143 |
| 7 | Errichto | 139 |
| 8 | adamant | 135 |
| 8 | BledDest | 135 |
| 10 | cry | 130 |
|
+41
Thanks for the report. I did my own investigation and confirm that BabyOrange5925, c12ste_vietrongtht26 and QuangThang2012 are cheaters. All of these accounts and their linked accounts have been blocked. |
|
+54
Your account has been restored. In Round 1129 we run checks during the contest for unusually fast solves of hard problems. Your profile looked like a typical case: one rated contest, rating 666, A and then F within 28 minutes while skipping B–E. Most accounts with this pattern in that round were indeed cheating, so you were caught by the same check. We need to act quickly in such cases, otherwise cheaters would flood the contests. After a detailed review of your submission history, your code and your AtCoder results, we found no evidence of cheating, so the ban has been lifted. Sorry for the inconvenience. |
|
+26
I checked this personally. Cheating is confirmed and the block stays. |
|
+23
Hi! There is no filter based on whether you might be able to solve the problems. Contest announcements are filtered only by the division's rating limit. Div. 3 announcements go to users rated below 1600 and to unrated users, and Div. 2 announcements go to users rated below 2100. Rounds open to everyone, such as Div. 1 + Div. 2 and Educational rounds, go to all subscribed users. Your account qualifies for all of them, and your "Contest email notification" setting is on (it's on by default). We checked our mail server (Postfix) logs for your address. There are eight deliveries: September 21, 24 and 25, and October 6, 9, 11, 13 and 15. That is every contest announcement sent since September 20, including Codeforces Round 1125 (Div. 3) and WorldQuant Round 1. Every one of them is logged as status=sent (250 2.0.0 OK) from gmail-smtp-in.l.google.com, so Google's mail server accepted them all. Nothing for you is waiting in our queue now. Logs older than about September 20 have already been rotated, so we can't check the August announcements. Our mailing system keeps per-recipient records only for the two latest campaigns, so for older ones the server logs are the only source. Gmail accepting a message doesn't guarantee it reached your Inbox. Most likely the announcements are in your Promotions or Spam folder. If you find one there, mark it as "Not spam" or move it to Primary so future ones arrive normally. Some other providers, such as Microsoft and Apple, are currently rejecting part of our mail because of a blocklist issue, but that doesn't affect Gmail: it accepted all of your messages. |
|
+4
News straight from the source: https://t.me/durov/548 |
|
+258
Thank you. You can rest assured that the organizers will carefully review your information. |
|
On
harrypang →
Request for Manual Review — Contest 2257 (Round 1117 Div. 2) Submissions Skipped, 3 months ago
+23
Update: CF correctly detected a cheater. The only false positive here was the one your comment invented. |
|
On
harrypang →
Request for Manual Review — Contest 2257 (Round 1117 Div. 2) Submissions Skipped, 3 months ago
+46
Thanks for the reminder. I've blocked both you and your second account t_jakhar_15. |
|
+82
Thank you for reaching out. I can confirm the issue with invocations, and I am already working on fixing it. Sorry for the inconvenience! |
|
+132
This email is a scam/phishing attempt. I do not send such emails, and this message was not sent by me or the Codeforces team. |
|
+1
It was quickly fixed |
|
On
Se7enn →
contest.standings API now restricted to gym/mashup only — anyone know why?, 6 months ago
+109
Hi. This change was made by me, so let me explain what happened. Originally, Recently this endpoint started to be used much more heavily by automated tools/scripts. I also suspect that some of this traffic came from AI/research-related usage. As a result, the whole site could become noticeably slower, because Codeforces had to calculate and return too much data too often. A few weeks ago I reacted by heavily restricting this method. In particular, I removed access to regular public contest standings through this API for ordinary users. This did break tools like Carrot, CF-Predictor, and similar extensions. I understand that it was unpleasant for users who relied on them. Today I made the restriction softer and changed the behavior to a compromise. For gym and mashup contests, For regular contests, ordinary and anonymous users can request standings only for public contests, and only by an anonymous GET request with exactly one query parameter: So for public regular contests, please use:
The response for such requests is cached for a short time, usually around 1–3 minutes. This should be much safer for the site and, I hope, should be enough for tools like Carrot, CF-Predictor, and similar extensions, as long as they only need public standings by contest id. If some tool currently sends an authenticated/signed request or passes extra parameters for regular contests, it will probably need to be adjusted to use the simple anonymous URL above. I don't currently have a technical way to keep the old fully-functional API behavior without risking performance degradation of the whole site. So this is not a full rollback to the old behavior, but an attempt to return the most useful part in a safe form. Sorry for the breakage. I'll watch how this compromise works in practice. |
|
+113
Banned |
|
On
_Mahmoud_Ayman →
Groups Members Page Lacks Pagination and Causes Performance Issues, 7 months ago
+18
|
|
+31
You cheated in at least four contests. Under our policy, we do not grant coach mode to such accounts. |
|
+48
I have unbanned hananabuzenib and Nassar_Al_Barahmeh. Unfortunately, it is very difficult to keep bots under control, and their accounts were mistakenly flagged as bots due to unusual behavior patterns. |
|
+24
You can add it to the Catalog! |
|
+1
|
|
+46
|
|
0
fixed now |
|
+55
One of the servers (called Floyd) just rebooted. It looks like it has some hardware issues :-( This is the first time it has happened. |
|
+184
It makes absolutely no sense to draw any conclusions about cheaters before we process the results and remove them. During the round, we only catch the most obvious and blatant cases (and their number is obviously limited). Let's wait until the cheaters are processed, and only then start making any conclusions. |
|
+31
It's not OK. We've updated the announcement to include:
|
|
On
MikeMirzayanov →
ICPC Baku World Finals Alumni Event: I invite you to a push-up challenge!, 14 months ago
0
See you tomorrow! |
|
+4
It is fixed now. Please, check again. |
|
+94
The issue has been fixed, and animated GIFs are now supported as well. |
|
+104
Animated GIFs are now supported. |
|
+16
I can't reproduce it on Brave. It works exactly as on Chrome for me. |
|
+91
Hi. Please, read the response: https://codeforces.me/blog/entry/141490. |
|
+116
Negative ratings will disappear after we process all cheaters and roll back the ratings. Please just wait a little. |
|
+425
Sorry, I lied a little. I didn’t go to eat cake. My brothers came from far away, and we went to the gym. The three of us in the gym for the first time!
|
|
+15
Here are the statistics on how you used magic this year. Shortly before the magic rollback, I gathered the following numbers. By ranks:
By colors:
|
|
+16
Thanks. We've implemented the "exclude problems created before" option. |
|
+13
Here is the link to the table with the current progress on rewards for daily leaders: https://codeforces.me/r/maraton-1-leadership-awards |
|
+48
I'll take a look on it. |
|
+10
Done. Thanks for the reminder. |
|
+35
|
|
-664
They all used secondary accounts to participate in today's round. Such behavior is unacceptable and violates the rules. I think this could be a good lesson. I spent the entire two hours of the round investigating and analyzing the situation because of these "jokers". |
|
+8
The testing protocol contains |
|
+3
Hi. I've implemented some fix. Please, try again. But it seems the reason is just unusual archive (it contains extra files or something like it). |
|
+8
Add "codeforces" as a contest developer to the contest in Polygon. |
|
+1
UPD: It seems we don't have a large number of issues with this. But thanks to everyone who reported: I've applied one more reconfiguration and hope to see even fewer (or almost none) reports now. |
|
+214
Thank you for the initiative in developing the community! |
|
+82
Thanks for the posting such details. You guys do so interesting things! |
|
+24
Thanks! |
|
+17
Unfortunately, I like Hat (Alias) only in Russian. |
|
+7
|
|
+8
Sounds great! I'll be happy if he joins! |
|
0
I look forward to seeing him on Wednesday! |
|
+97
Challenge accepted! |
|
+95
Planning to hit the gym at the Astana Hilton this evening. Want to join? The first workout is free! |
|
+117
Maybe it is a good idea for my Instagram :-) |
|
+5
Please, try again. |
|
+576
We are also unable to determine whether you are solving the problems on your own or generating all the ideas with a large team. Indeed, in the context of online competitions, we cannot enforce all the rules strictly, but I believe we have always done what is within our power and moved forward by continuing to hold contests. I hope that the Codeforces community remains the same as before – with a significant number of participants who follow the rules and do not constantly look for loopholes to break them. |
|
+50
Thanks, added to the list |
|
+414
Hi! We're making progress on this issue. Don't go too far, and you'll see changes soon. |
|
+43
Right now this rule still works. |
|
+18
Please, try again. Thanks for testing! |
|
+3
Actually, I don't see any contest proposals from you. Probably, you didn't create a contest proposal (just separate problem proposals). I will consider the possibility of strengthening the warnings, but it seems that you are the first to encounter such a misunderstanding. After all, it has been repeatedly mentioned specifically about contest proposals. There are some quotes from the sidebar:
Also in this post, there is:
|
|
+11
Fixed. Please, try again. |
|
-6
I can't find such Ray ID in Cloudflare logs. Are you sure in it? |
|
On
sohailkazi →
"Sorry, you have been blocked" message by CloudFlare, cannot make submissions [FIXED], 2 years ago
+21
Hello. I've reconfigured some settings on the Cloudflare side, but in such cases, please report to me as described here: https://codeforces.me/blog/entry/133113 |
|
0
Thanks. |
|
+16
Please read my update. I completely switched the GCC-14 distribution to another one, and I haven't seen any indication that you've tried it yet. |
|
+6
Please, check |
|
0
Please, check |
|
+17
It is fixed now. Please, try again. |
|
0
Please, check |
|
+49
Some time ago, there was news here that we supported C++23 by installing GCC 14 from the Winlibs project. It turned out that with this method of supporting C++23, some compatibility issues lead to significant performance drops in certain submissions. So, I tried another distribution for GCC 14: the MSYS2 project. It seems that this problem does not occur with it, and now there are no unexpected performance drops. Let's test this C++23 support option together! |
|
0
Restart cmd session to reload environment variables. Also check your PATH variable for another gcc before this. |
|
+25
I fixed the print issue, |
|
+4
Thank you for bringing the issue to my attention. I have implemented a fix. Please check it now. |
|
+340
Hello! Actually, you wrote all these complaints before we conducted our regular cheater search. All cheaters were found using the usual method, and the submissions mentioned in the reports provided only minimal assistance. For example, dozens of cheaters were reported, but we found hundreds. I think it's not worth getting worried until the cheater search procedure is completed. In most cases, your complaints will be addressed simply through the standard process. We are making significant efforts to identify as many cases of plagiarism as possible. We are trying very hard! |
|
+612
That moment when you suddenly want to implement reactions to comments. |
|
+180
For the role of a researcher, I nominate this |
|
+269
We are carefully looking into the situation and will inform you when we make a decision. |
|
+12
Please, send me a link to the exact dat-file you are trying to upload. I'll take a look. |
|
+36
In this round, there were three problems based on my ideas: 1974B - Symmetric Encoding, 1974C - Beautiful Triple Pairs, 1974F - Cutting Game. |
|
+641
Give me some time to figure all this out. |
|
+35
Hi, I've fixed it. The rating will be recalculated once the cheaters have been processed. |
|
+35
Here's the update! I've upgraded Go to version 1.22.2 and PyPy3-64 to version 3.10/7.3.15. Enjoy using them! P.S. After my return from Egypt, you can expect more updates! |
|
+34
Thanks! I'll look into it after WF in Egypt. |
|
+40
I sent you all the details via private message, including the transaction link. In short, at the time of the data upload, a different wallet was specified by you, which you changed later. The TONs were sent to that wallet. |
|
+37
The plan is to begin the migration on Monday morning. |
|
+142
Sorry, but I'm moving the round 10 minutes forward. The training session was very cool and long. I'm running to you from the gym! |
|
+148
TLDR: Very soon, I will migrate the testing servers to Windows Server 2022. I have spent a great deal of effort in recent days to accomplish this. Good news: most of these issues are not reproducible there (more precisely, we do not know how to reproduce them), and it will be possible to update some compilers/interpreters that could no longer be updated for Windows 7. Bad news: modern operating systems have deep protections against speculative vulnerabilities (like Spectre, Meltdown, and others), and therefore, on the whole, any solution will work a bit longer (by my estimates, plus 5-15%). P.S. We will likely switch to LLVM's clang++ instead of g++. It performs better in some tests.
I'm not entirely sure about the current situation. I hope that after migrating to Windows Server 2022, there won't be such methods.
I hope that after my work, it will not be possible to exploit the operating system/compiler bugs so explicitly. Therefore, when preparing problems, one should not expect that such tests will be specifically constructed. However, I urge you to clearly distinguish between two different scenarios in your mind: a bug and a feature of implementation. For example, exploiting collisions in hash tables, quadratic tests for sorting in Java — these are examples of using features of the standard library. The presence of such tests is a feature of problem preparation, and they may either be present or absent in the test set.
In any fairly large and complex software, there are bugs. This is especially true for compilers with their aim to optimize the resulting code. Sometimes the line between a bug and a feature is thin and undefined. I am not ready to take responsibility on our part for individual attention to cases of probable bugs in compilers. In other words, if a participant writes code that encounters unexpected behavior from the compiler/OS, we will not be able to individually understand and help in this situation. On the other hand, I am closely monitoring the situation and paying attention to widespread instances of any such problems.
I think that 32-bit versions are stable. But currently, I am working on resolving the situation more systematically, rather than fighting it using half measures.
Read the previous response.
I really hope that switching to a modern OS (and likely to clang++ as well) will resolve the issue. However, I'm fairly certain that this won't be the last bug in the compiler/OS, and over time, we will discover new ones.
I haven't delved deeply into this issue. It seems that in the current setup, even if somehow resolved, the problem will emerge in some other unexpected place. I prefer to try moving forward.
Many bugs in the world are quite unstable to reproduce. This is an example of one of them. The method of launching for solutions during testing and during custom invocation is the same.
It seems to me that this problem is clearly reproduced only on specific versions of Windows 7. This does not mean that there are no other problems in Linux or newer versions of Windows. Tests by maxplus (thank you!) show that there are some irregularities in other setups as well, but we expect that they have little impact on the testing of problem solutions. In any case, I plan to make the main setup one in which such problems do not reproduce at all.
Apparently, this particular bug does not reproduce on Linux. However, even on Codeforces, we lived for a long time without noticing it. I don't know and cannot confidently assert what happens on other systems, especially considering the wide variety of versions, hardware, security patches, etc. Regarding the switch to Linux: yes, it is a labor-intensive and complex task. We have a huge number of problems (checkers, author solutions, generators, etc.) that may not work or work unpredictably on other systems. In some cases, they are written in languages/dialects whose support in Linux significantly differs. I should note that the number of participants using Windows is twice as many as those using Linux and iOS combined. |
|
+97
We are working to make our problem ratings better. Stay tuned for updates! Actually, on clist there are many weird ratings too. I can't say it is perfect:
There are more examples like these if you examine clist carefully. |
|
+26
Curious, why does your example give TLE when submitted, but not during custom invocation? |
|
+3
I think so. If you're not sure, just stick to the time-tested 32-bit versions. |
|
+145
Thank you for this investigation. I have introduced a new language: C++20 (GCC 13-64). Please test it. My tests show that this issue has been fixed in this version. The current plan is to hide all other 64-bit C++ compilers except for the new C++20 (GCC 13-64). |
|
0
Just erase all personal data from your user account and don't use it anymore. We don't store personal data long-term. |
|
+3
|
|
+4
Please, try again now |
|
6 times. I will repeat, 6 times in different contests you cheated, using someone else's solutions or sharing your own. After each time, you were warned that your account would be banned. What do you want from me? You deserved the punishment. |
|
+22
I fixed this problem. |
|
+2
Thank you. It appears that the issue was not the result of https://codeforces.me/blog/entry/105779 However, it can be seen here https://web.archive.org/web/20210416021306/http://codeforces.com:80/contest/382/problem/D Thus, the incorrect rendering has been occurring for at least three years. The most challenging aspect of addressing such bugs isn't the backend repair but ensuring backward compatibility. Fixing this might impact other problems that depend on the current behavior. A probably better solution would be to correct such issues in Polygon. Do you know of any other incidents involving similar problems? |
|
+67
You cheated in no less than 4 rounds. And those were clear coincidences. I think you're a hair's breadth away from a ban. |
|
+21
I have switched Kotlin 1.9 to use the JRE 8 32-bit. Now, all your example submissions on 1.9 are as fast as on 1.6, or even faster. Please conduct your benchmarks and share the results. Additionally, I will reinstate Java 8 32-bit but will remove Java 11 and 17. You see, I prefer not to maintain more than two versions for a single language (ideally, just one). Supporting additional versions introduces complexities. C++ is an exception due to its popularity. However, even with C++, when adding new versions, I find it necessary to phase out the oldest ones. |
|
+43
Everything comes to an end. We say goodbye to the magic of the New Year. Santa Claus is already actively casting spells to roll back the masquerade. Here are some statistics for you. A total of 70712 magic masquerades were applied.
Or by color:
|
| Name |
|---|


