Sugar_539's blog

Someone copied my code for Problem A during Codeforces Round #696 (Div 2)
By Sugar_539, history, 3 years ago, In English

User named "shree_e" has copied my code for Problem A and submitted it during the ongoing contest (Codeforces Round #696 (Div 2)) after I locked my submission. But as far as I know no one should be able to see my code until they've made a successful submission during the contest. But this guy @shree_e was able to copy my code without a successful submission from his side. I have not used ant online platform to edit and test my code. Today, I received a mail from codeforces warning me of copying code (or distributing my code).........but that isn't the case. For proof, I have attached screenshots regarding the submission details of me (Sugar_539) and that of shree_e's.

My(Sugar_539) — 104788438 (time submitted : 20:28)

shree_e — 104803384 (time submitted : 20:51)

Based on the time, Codeforces system has skipped the submissions of shree_e, but also I was given a strike, which is unfair. I hope the Codeforces community is with me on this!

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

Comments Comments (12)
| Write comment?
»
3 years ago, # |
  Vote: I like it +12 Vote: I do not like it

There is actually a way that this happens , a person who submits can then give code to others who haven't yet submitted . And it's so unfortunate that this happened to you. I think this feature can cause real troubles with the rising amount of unethical practices . I would request everyone to suggest ways to deal with it.

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

    Ok, are you suggesting that I gave him my code (from outside) ? No way, I don't even know that person (@shree_e). (Also, there's no way for me to prove my point here!)

    → Reply
    • »
      »
      »
      3 years ago, # ^ |
        Vote: I like it +34 Vote: I do not like it

      No, actually someone other who has also solved it and locked it can always see your solution and give it to someone.

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

        OMG! I had no idea such things happen. So is it better to not lock our solutions?

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

          If you're likely to make hacks, then lock it. If you normally don't hack, then don't lock it.

          → Reply
          • »
            »
            »
            »
            »
            »
            3 years ago, # ^ |
              Vote: I like it +3 Vote: I do not like it

            Usually I don't hack, so I think it's better not to lock!

            → Reply
    • »
      »
      »
      3 years ago, # ^ |
        Vote: I like it +14 Vote: I do not like it

      No , i meant someone else locked his submission and then shared your code to the user you are talking about.

      → Reply
»
3 years ago, # |
  Vote: I like it -8 Vote: I do not like it

In my opinion on contest hacking should be stopped. This is helping people to cheat easily.

→ Reply
»
3 years ago, # |
  Vote: I like it +8 Vote: I do not like it

I have just written a blog on it. people lock their code and view others code and make them public.

→ Reply
»
3 years ago, # |
  Vote: I like it +16 Vote: I do not like it

Maybe allowing hacking phase only after the contest can be a solution to tackle these issues.

→ Reply