Hey Codeforces!
I made a thing and I want to share it with the community.
We wanted to keep track of achievements and submissions in our team and using Codeforces status page is not really handy. Therefore, I introduce to you Team dashboard.
Here you can find some kind of a timeline for each member of your team, showing last submissions, contests and even blog posts on Codeforces.
Using this script is pretty easy, just specify up to 3 handles in the address, separated by semicolons (please check below). Also please keep in mind that this script was made in 3-4 hours, so there is almost certainly a handful of bugs. Also, the script asks a lot of queries to the Codeforces API, so sometimes not all requests are answered. You should wait a couple of seconds and try again.
Visit right now and bookmark your team:
http://weaselcrow.com/pro/cf/team/?h=Radewoosh;Errichto;kostka
You can also compare yourself with your archenemy:
http://weaselcrow.com/pro/cf/team/?h=kostka;olekluka
Upd: fixed some bugs, including incorrect places and no response if no one from the team submitted anything.
Upd2: fixed bug with blocked blogs.
Upd3: you can now request as many days as you want, adding d argument, for instance:
http://weaselcrow.com/pro/cf/team/?h=mnbvmar&d=60
Please use it carefully, as requesting too many days will probably timeout.
Upd4: added team rating, as calculated by Codeforces.
Upd5: added problem ratings.
Can you make links to cf to be opened in a new tab?
I can, but you can also hold ctrl while opening a new link. ;)
Looks like script has problems with numbers
I'm currently investigating why some handles are causing errors. Sorry about that!
It looks like this is the problem:
http://codeforces.com/api/user.blogEntries?handle=2fid
I will soon fix this.
Something is wrong
Same error message as the one in the previous comment: "Some error happened, please check if all handles are valid or please try again in a few moments."
Same problem: http://codeforces.com/api/user.blogEntries?handle=IMKortam
Should be fixed in a couple minutes.
Sounds good. But I think codeforces's status page is enough for me.
What's more, I think this website is a bit slow.
I know it's kinda slow, mostly because of a limit of at most 5 API requests per second.
Can't it handle more handles??(wow what a sentence!!) Because sometimes it's not just about comparing a single team...
It can, but then everything becomes pretty unreadable. You can always open many cards with different handles.
According to the latest blogs, Codeforces becomes Polishforces :)
But you made very cool thing, seriously!
Cool!
However it only shows records over the past one month. It would be better if a longer timeline is available.
I thought that a month was enough in most cases, but I'll rethink it. Thanks for suggestion!
You can now add a new argument &d=60, meaning the number of days shown. Please use it carefully, as requesting too many days will probably timeout.
The app seemed to be down now. It say "Connection timed out" whenever I try to use the app.
I cannot reproduce the problem. Can you add some details?
I just click on the link provided in the blog (http://weaselcrow.com/pro/cf/team/?h=Radewoosh;Errichto;kostka) and it show the following screen:
That's really strange. I know that the script is really slow, but I cannot do anything faster without caching and storing some data from Codeforces, which I am not a big fan of (because it will take some time to implement it correctly). Can you try with one handle and check if the problem still occurs?
For some reason, the app is working now.
That's awesome. I am really sorry, but I have absolutely no idea what was the problem.
Hey kostka i am trying to add up my handle but its not working(Some error happened, please check if all handles are valid or please try again in a few moments.) just for my handle...I dont know my team handles are easily added but not mine. Can you tell me the reason?
The same thing happens to me. My handle exists, but not my teammates.
Could you please take a look at this issue, kostka?
I will look into it next week.
My guess is that it might be related to the fact that you are muted (you cannot write blogs). It was a reason for some bug before and maybe something similar happened again. I will look into it later next week.
Thanks, I'll wait till next week.
Solved! (Just write a blog ...)