clist.by stopped updating recent Codeforces problems. Anyone knows what’s going on?
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | Benq | 3792 |
| 2 | VivaciousAubergine | 3647 |
| 3 | Kevin114514 | 3603 |
| 4 | jiangly | 3583 |
| 5 | turmax | 3559 |
| 6 | tourist | 3541 |
| 7 | strapple | 3515 |
| 8 | ksun48 | 3461 |
| 9 | dXqwq | 3436 |
| 10 | Otomachi_Una | 3413 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 157 |
| 2 | adamant | 153 |
| 3 | Um_nik | 146 |
| 3 | Proof_by_QED | 146 |
| 5 | Dominater069 | 145 |
| 6 | errorgorn | 141 |
| 7 | cry | 139 |
| 8 | YuukiS | 135 |
| 9 | TheScrasse | 134 |
| 10 | chromate00 | 133 |
clist.by stopped updating recent Codeforces problems. Anyone knows what’s going on?
| Название |
|---|



Codeforces has updated its API rules lately. Take the
contest.standingsendpoint as an example:I suspect these changes are the reason behind the recent issues with clist.by and why Carrot has stopped working.
You can also refer to this blog.
Really sad… clist is super useful for tracking problem difficulty. Hope Codeforces updates ratings faster.