In div 2 rounds, we can lock our submission and hack others code, cheaters use this opportunity to cheat or leak solutions during contest. How about hacking phrase starts right after contest ends and last for 1 or 2 hours (Unlike 12 hours in div 3 or educational round)?
→ Обратите внимание
До соревнования
CodeTON Round 9 (Div. 1 + Div. 2, Rated, Prizes!)
29:47:03
Зарегистрироваться »
CodeTON Round 9 (Div. 1 + Div. 2, Rated, Prizes!)
29:47:03
Зарегистрироваться »
*есть доп. регистрация
→ Лидеры (рейтинг)
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 4009 |
| 2 | jiangly | 3823 |
| 3 | Benq | 3738 |
| 4 | Radewoosh | 3633 |
| 5 | jqdai0815 | 3620 |
| 6 | orzdevinwang | 3529 |
| 7 | ecnerwala | 3446 |
| 8 | Um_nik | 3396 |
| 9 | ksun48 | 3390 |
| 10 | gamegame | 3386 |
| Страны | Города | Организации | Всё → |
→ Лидеры (вклад)
| № | Пользователь | Вклад |
|---|---|---|
| 1 | cry | 167 |
| 2 | Um_nik | 163 |
| 3 | maomao90 | 162 |
| 3 | atcoder_official | 162 |
| 5 | adamant | 159 |
| 6 | -is-this-fft- | 158 |
| 7 | awoo | 157 |
| 8 | TheScrasse | 154 |
| 9 | Dominater069 | 153 |
| 9 | nor | 153 |
→ Найти пользователя
→ Прямой эфир
Codeforces (c) Copyright 2010-2024 Михаил Мирзаянов
Соревнования по программированию 2.0
Время на сервере: 22.11.2024 11:47:58 (j1).
Десктопная версия, переключиться на мобильную.
При поддержке
It might also be possible that someone innocent is accused of cheating without them realizing their source code being shared across
exactly
remove hacking ?
No, just while hacking no one can submit solutions.
Congratulations, you have rediscovered topcoder hacking :)
I agree that with cheater incidents on the rise, this might be a good way to still keep hacking in contests without delegating it solely to an uphacking phase (though an extra hacking phase might make participation lower because people would need to stick around for longer, and "bounty-hunting" might become a collective effort).
As a byproduct, it'll also reduce proof by AC incidents because people would be more careful about submitting solutions, since currently they rely on being able to resubmit if they get hacked.
well sometimes code fails in system test as well, where we can't resubmit.
Ok, but a cheater can only leak a solution to a problem they've already solved, so surely if they leak someones solution and that person gets flagged for plagiarism, it's easy to deduce who the cheater is?
But in general it is impossible to deduce whether it was the solution author who leaked it or if it was someone else in their room who solved that problem too. How do you solve this issue?
If someone gets flagged for plagiarism, then they can appeal it and then maybe someone can check whether there was someone in the room who looked at their code during the contest.
If there was, then you could also look at previous contests and see if that person has looked at other people's code shortly before they got flagged for plagiarism.
Of course there is still the problem of people just going ahead and making new accounts to avoid this
Yeah, that makes sense in the steady state, but it is a bit too late once someone has already suffered at the hands of such cheaters. In my opinion, doing something that prevents this scenario altogether is a better idea, since getting falsely accused of plagiarism is an unpleasant experience and leaves a negative mark on the person's profile, regardless of whether they actually cheated or not.