Oh my god, Codeforces is once again jammed by a massive number of new accounts without ratings, turning into "Queueforces". This might be a problem.
Oh my god, Codeforces is once again jammed by a massive number of new accounts without ratings, turning into "Queueforces". This might be a problem.
| # | User | Rating |
|---|---|---|
| 1 | jiangly | 3810 |
| 2 | Benq | 3676 |
| 3 | Kevin114514 | 3655 |
| 4 | maroonrk | 3463 |
| 5 | strapple | 3447 |
| 6 | Um_nik | 3387 |
| 7 | heuristica | 3322 |
| 8 | turmax | 3317 |
| 9 | tourist | 3307 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 156 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | Um_nik | 143 |
| 5 | Errichto | 139 |
| 6 | adamant | 137 |
| 7 | AmShZ | 135 |
| 8 | maroonrk | 133 |
| 9 | BledDest | 132 |
| 10 | qwexd | 129 |
Most of them are unrated and submit solutions too frequently. I suspect they’re bots.
Agreed
They should limit the frequency of submissions for unrated accounts. The queue times are honestly way too annoying these days.
this was my first submission after 6 months still in queue :[
When will this problem be fixed?
It's been like almost 2 hours and my submission is still in queue
It’s been an hour and still in queue Hopefully it gets fixed today
They really need to do something about this, it's getting too frequent and annoying these days :(
+
Read this : queue approach blog
Useful trick. Why do ppl downvote?
every botted submission has a UUID at the end. 347605306 347605303 347605385. wouldn't be surprised if this is some training for LLMs and the UUID is being used for tracking.
And got WA on test 1.Seemed that the examples weren't being used as the very first testcases are mostly examples that are given in the discription.Also,obvious AI style for coding.
Every time I visit Codeforces I get slapped with a Cloudflare captcha, but these bots can submit whatever they want whenever they want
+1
FlareSolverr fixes that problem, cloudflare isn't that good of a CAPTCHA. FlareSolverr is just a proxy that handles cloudflare btw, can't get easier to bypass, you don't even need to integrate it to your bot, you just need to use it as a proxy
i guess that they use cloudflare servers
patience is also a skill
It is crucial to add limitation of submission frequency or AI detection. The headquarters may need to control the situation by punishing (or banning) unrated (or rated) accounts when they "abolish" the judging process.
it's hard to punish those unrated acc. they are just innumerable. btw im wondering why didnt the cloudflare human verification work
here i am waiting for a wa
xD
guys it's true that 15 hours ago the queue is long,
but the newest one I think the judge died instead of long queue.
L cloudflare
I also checked problemset status and found several bot-like accounts flooding the queue. And I observed same pattern across : - Submission every 1-3 mins for hours with no breaks - Random compiler - No retries even if solution is not accepted
This behavior looks automated and could be one of the reasons the queue keeps getting jammed.
Like : Codernikkk;drnbrhrdt;pp031608;
faishal_052;kohlaaaa;imraquibe
PS:not accusing anyone personally-just sharing evidence for admins to check.
What is happening? I submitted my first problem of the day at 8:52 AM still it is showing judging? Is their any testing going through codeforces?
It's just a lot of bot accounts submitting every 3-4 minutes all day thus the queue gets quite long sometimes so just wait ig.
wtf is going on with 724g
https://codeforces.me/contest/724/status/page/1?order=BY_JUDGED_DESC
It appears to be impersonating the usernames of many rated users. For instance, this ETO-leaders account is mimicking the legitimate ETO-leader by adding an 's'.
what are they even achieving from this?
for training their llm or something
bruh
I think CF can temporary disable submissions from some specific problems which are seemed to be spam. I saw in status page has many submissions for problem 724G. In the future, CF can do the same thing when count the number of submissions is high (for problems are not in contest). I guess this may help to fix the "in queue"
thought that problem is just chosen randomly.maybe someone wanted to attack CF?thus banning one problem is of no use.as some of the bot accounts even mimick those of rated users,i thought that might be an organised abuse/attack?
At least it may help us at the moment. If anyone pick problems randomly and attack, I think it's impossible to prevent
finally recovered from in queue :)
again long queue
Codeforces should ban unrated first time submission in contests
It's so much frustrating
Captcha is easily solved by bots instead, we should use internet memes. for example, we ask the new account:
which number is special? 67 or 71 ?