rewhile's blog

By rewhile, 13 months ago, In English

This blog will compile a list of codeforces issues along with all the times Mike has ignored complaints about them

1. Unreasonable delay for viewing submissions [+973]

No MikeMirzayanov reply

2. Cloudflare misconfiguration [+1232]

Posted CF should rename itself to Cloudflare instead of Codeforces by nor

No MikeMirzayanov reply, nor has since deleted all of their blogs on codeforces

3. IP ban + blocked by the administrator [+105]

Happens right after the DDOS of Codeforces Round 1010 (Div. 1, Unrated), I myself also couldn't login that day

No MikeMirzayanov reply, silent fix (+ one extra cloudflare page on login)

What's up with this abomination of cloudflare usage? I think https://atcoder.jp/login is more reasonable:

4. Recently, your account was used to crawl [+105]

djm03178's account also got flagged as crawling bot for joining codeforces educational round hacking phase

No MikeMirzayanov reply, radio silent as always

5. Hacking issues

Couldn't hack today by sorry12000 where he couldn't get points hacking A

This also affected dorijanlendvaj. 2 years later he lost 50 points due to an interactor bug but offered no rejudge

No MikeMirzayanov reply

6. API issues

If you've used a rating predictor, for example carrot (40000 users as of April 2025)

You might have noticed that it doesn't work for a long period of time. This is because Mike enabled cloudflare even for apis during contest, which got a workaround in meooow25/carrot#67

It worked for a while again until he started to take down the user.ratedList api during contest too:

MikeMirzayanov did make a comment about this api 3 years ago. However, it seems like there was no further communication.

∞. The list could stop here

Despite almost graduating from university, when I type c in browser it autocompletes to codeforces.com instead of chatgpt.com

It is not unreasonable to ask for accountability when CF has become the de-facto competitive programming community website.

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

| Write comment?
»
13 months ago, hide # |
 
Vote: I like it +9 Vote: I do not like it
»
13 months ago, hide # |
Rev. 2  
Vote: I like it +49 Vote: I do not like it

I would not be against these policies if these are really, really needed to keep CF alive. However, it's simply wrong to block tons of random actions that should normally be available in any working website even without explaining the need for them to the users. It's even more wrong to automatically assume that the normal users have done something malicious and flag them when their activities should never even be close to anything harmful to the website. Like what, opening 50 submission pages in 2 hours kills the website so that they should be banned from opening another single submission page for 7 hours? Is this joke?

Please administrators, show yourselves up and explain. Why do you need to do this to us?

»
13 months ago, hide # |
 
Vote: I like it +1 Vote: I do not like it

We need kenkoooo but for codeforces, any sponsors?

»
13 months ago, hide # |
 
Vote: I like it +59 Vote: I do not like it

"Despite almost graduating from university, when I type c in browser it autocompletes to codeforces.com instead of chatgpt.com"

This sentence goes hard bro! Same here.

»
13 months ago, hide # |
 
Vote: I like it +26 Vote: I do not like it

'or we will ignore you' Sorry, but I am curious what can we do?

  • »
    »
    13 months ago, hide # ^ |
     
    Vote: I like it +10 Vote: I do not like it

    We can just leave codeforces and migrate to other platforms ig

»
13 months ago, hide # |
 
Vote: I like it +127 Vote: I do not like it

We need "Things I don't know (MikeMirzayanov edition)"

»
13 months ago, hide # |
 
Vote: I like it +14 Vote: I do not like it

I agree, it would be nice if we can be keep up to date with what's new with the site, it's very annoying when features just stop working suddenly with no warnings whatsoever.

»
13 months ago, hide # |
 
Vote: I like it -11 Vote: I do not like it

Damn it's weird how all of the sudden everyone cares so much about these nonissues once the blog was posted. If it were deleted, no one would care once again.

  • »
    »
    13 months ago, hide # ^ |
    Rev. 2  
    Vote: I like it +23 Vote: I do not like it

    are you retarded? just because we don't say it doesn't mean no one notices what's happening. there has been blogs about all of these issues, most just gets attention for a few days and gets forgotten, dont blame us for your 30s tiktok attention span, monkey

»
13 months ago, hide # |
 
Vote: I like it +15 Vote: I do not like it

CF dead xD

»
13 months ago, hide # |
 
Vote: I like it 0 Vote: I do not like it

Day 2 of asking for a resolution as no answer happened yet.

»
13 months ago, hide # |
 
Vote: I like it +8 Vote: I do not like it

dead internet theory

»
13 months ago, hide # |
 
Vote: I like it +13 Vote: I do not like it

I'm gonna add to 3.: the button you need to click (the 3rd verification click you need to make!) doesn't appear on Brave and maybe other browsers. Sure, I'm competing from Chromium or Firefox and problem solved, but it's a stupid, unnecessary inconvenience.

  • »
    »
    13 months ago, hide # ^ |
     
    Vote: I like it +16 Vote: I do not like it

    I can't reproduce it on Brave. It works exactly as on Chrome for me.

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

      Interesting. I'll record the process and send you with details.

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

      Update: after a bit of experimenting to find out why you didn't reproduce it, I found out one of my privacy extensions was blocking something in the Cloudflare process. I verified that Cloudflare analytics is still blocked without that extension, selectively disabled only that extension only for CF and it works.

»
13 months ago, hide # |
 
Vote: I like it +91 Vote: I do not like it

Hi. Please, read the response: https://mirror.codeforces.com/blog/entry/141490.