So I think everyone knows what happened in the previous contest. One of the problems was the same as one of the problems in an old contest. Now, I think this on its own is not an issue as it happens in almost every contest nowadays(maybe not exactly identical but the idea is the same) and if someone has studied that problem before it is fair for them to solve it. The huge issue was that people were mentioning that they have seen the problem somewhere in blogs and comments so people that have not seen that problem before were also informed. I think one idea is to remove the ability of posting comments and blogs during contests. This would have a great effect but it would not stop the cheatings completely. another improvement that can be done is to block the access to previous submissions on old problems THAT ARE NOT YOUR OWN SUBMISSIONS during a contest; With this method, people that have solved a problem before can still access it but people that just want to copy paste something can't. Now this does not solve the problem of coincidence with problems on another platform but these are two improvements that I only see pros on and not any cons. Feel free to share your ideas.
→ Pay attention
→ Streams
→ Top rated
| # | User | Rating |
|---|---|---|
| 1 | ecnerwala | 3649 |
| 2 | Benq | 3581 |
| 3 | jiangly | 3578 |
| 4 | orzdevinwang | 3570 |
| 5 | Geothermal | 3569 |
| 5 | cnnfls_csy | 3569 |
| 7 | tourist | 3565 |
| 8 | maroonrk | 3531 |
| 9 | Radewoosh | 3521 |
| 10 | Um_nik | 3482 |
→ Top contributors
| # | User | Contrib. |
|---|---|---|
| 1 | maomao90 | 174 |
| 2 | awoo | 165 |
| 3 | adamant | 161 |
| 4 | TheScrasse | 160 |
| 5 | nor | 158 |
| 6 | maroonrk | 156 |
| 7 | -is-this-fft- | 152 |
| 8 | orz | 146 |
| 8 | SecondThread | 146 |
| 10 | pajenegod | 145 |
→ Find user
→ Recent actions
Codeforces (c) Copyright 2010-2024 Mike Mirzayanov
The only programming contests Web 2.0 platform
Server time: May/01/2024 11:35:55 (j1).
Desktop version, switch to mobile version.
Supported by
Blocking other people's submissions won't help as they can always check the editorial.
Well, The editorial code is also a submission and i don't think many people that solved the previous F could implement it on their own even if they knew the solution
I suggest blocking the ability to post comments/make blogs during the contest, so people cannot tell each other that this exact problem can be found somewhere else. And if someone personally saw the problem previously and is able to locate it during contest, I don't think it is bad tbh.
yes you are right. However with the new "Youtube cheating method" people can still inform each other. Now since most of the cheaters are dumb, they cannot really change the solution and therefore would get caught if they are given the solution code. and because of codeforces rules the only way you can use a copied code during a contest, is to provide the proof that that code was written before the contest. so if cheaters have access to old submissions they can provide the proof and they would get out of the situation safely. so either that rule needs to be modified in someway or the old submissions from other people should be blocked. and if someone has intentions of using someone else's template during a contest they can just save it somewhere before the contest starts.