lOthBroK286's blog

By lOthBroK286, history, 3 months ago, In English

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)?

  • Vote: I like it
  • +20
  • Vote: I do not like it

»
3 months ago, # |
  Vote: I like it +40 Vote: I do not like it

It might also be possible that someone innocent is accused of cheating without them realizing their source code being shared across

»
3 months ago, # |
  Vote: I like it +16 Vote: I do not like it

remove hacking ?

»
3 months ago, # |
  Vote: I like it +4 Vote: I do not like it

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.

  • »
    »
    3 months ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    well sometimes code fails in system test as well, where we can't resubmit.

»
3 months ago, # |
  Vote: I like it +5 Vote: I do not like it

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?

  • »
    »
    3 months ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    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?

    • »
      »
      »
      3 months ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      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

      • »
        »
        »
        »
        3 months ago, # ^ |
          Vote: I like it 0 Vote: I do not like it

        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.