| # | User | Rating |
|---|---|---|
| 1 | tourist | 2887 |
| 2 | Petr | 2711 |
| 3 | dzhulgakov | 2692 |
| 4 | hos.lyric | 2652 |
| 5 | WJMZBMR | 2635 |
| 6 | Egor | 2583 |
| 7 | peter50216 | 2545 |
| 8 | ivan.metelsky | 2529 |
| 9 | rng_58 | 2528 |
| 10 | RAVEman | 2508 |
| # | User | Contrib. |
|---|---|---|
| 1 | Alex_KPR | 166 |
| 2 | Egor | 146 |
| 3 | SkidanovAlex | 141 |
| 3 | Nickolas | 141 |
| 5 | natalia | 138 |
| 6 | Ripatti | 134 |
| 7 | ivan.popelyshev | 133 |
| 8 | yeputons | 127 |
| 9 | I_love_natalia | 126 |
| 10 | kuniavski | 125 |




It'll be so until that someone submit a new solution (if the problem wasn't closed; if closed - NO WAI), that again passes pretests And tests, that used to hack this person's solution before.
If BF/load are issues just add an X seconds delay between hacking attempts.
I don't really think it would be useful to try "hacking" at all. In TC challenges were already too much of an unusable gimmick for most div1 coders. But if besides of the risk of losing points, you also add that you cannot resubmit any more and that you have to use time during coding phase it is too much.
One more argument for making penalty for unsuccessful hacking - it should stop hacking flood and brute force hacking :-D
IMHO, with your system the whole idea of combining the coding and the hacking phases together almost doesn't make sense. I agree that the importance of hacking is now emphasized, but well, that's the feature of the format. By the way, in alpha round #20 ivan.popelyshev started to hack solutions only after he submitted all 3 problems himself, and still made it to the 1st place.
As for the tracking of the scoreboard — I'm sure there will be improvements of the interface that will make this easier.
I liked the idea of silent and multiple hacking by Kalinov. It makes sense.
1. The way I understand it, we cannot hack at problems we haven't submitted and locked ourselves. But we might have formulated usable test cases, even if we failed to submit. Would it be possible to lock a problem we haven't submitted - in effect we forfeit our chance to submit the problem any more in the contest - and then challenge?
2. In TopCoder, the text of solution code is unobtainable by copy-paste or any other way. This is essential to prevent automated challenges. Is there a similar restriction in the new format?
On the whole, this new format looks promising. Looking forward to the first rated match.
No, you can't copy-paste other's solution.
You can still hack others
P.S. I can see that this way you will be mention his cheating and will disqualify him, but it's just a matter of canceling the potential of cheating as much as you can. Also, note that you won't even think of cheating if the process is done for a small value of N.
Solution: Don't let someone hack another ones solution for more than once (or twice)
ایول
Sorry for my bad English
Here's a sample Java solution for problem A from beta round #1
1. Proceed to the "Contests" page. (link)
2. Enter one of the previous contests. (example)
3. Proceed to the "status" page (status)
4. Find some accepted solutions in Java
5. Look at the code clicking the solution ID link.
P.S. It seems to be that you just print the answers for the sample tests. Instead you should read the input data from the standard input stream.
What about the following idea: after the finish of each contest, problemsetters upload all tests to all their problems as an archive (to some site). It's not difficult for authors to take an archive from the system ('Polygon') where the problems are created.
I don't know when the feature of viewing test data will be available on Codeforces, so I suppose this is the best solution. It's really not a good idea to ask tests in comments on the site, IMHO.
I am asking because some hacks may expose bugs that the system tests may not cover. In such a situation, a solution may get accepted because the author of the hack failed to check the solution or was in a different room.
How can I see the whole input in Source view? i.e. Test #6
Unfortunately, it’s impossible.