It would be nice if we could logging with Open Id and also mark "remember me for a month". I was logging in with Open Id today, and it kept forgetting me. I had to eventually try hard to remember my password... Good thing I did.
For example the "Ask a question" link. Or the links with the submission number in practice that show you your code and the case with the mistake.
I tested in chromium and they work all right.
Anyone else experiencing this?
With the advent of contests that are 24 hours long, they can get a little too long if you start a virtual contest for them and are done with the problems after a couple of hours and do not really plan to do anything more, yet you have to wait the whole 24 hours for it to finish. You currently can just log out and go to standings though, so this is only a slight issue.
And a question, would deleting the virtual contest do this, or will it also remove the participation stats from the round's unofficial standings?
This is as minimal of an issue as possible, but how about a small minimize button that makes the problem tags part of problems in practice room hidden by default?
The thing is although tags are useful to find problems or to know the classification of a problem once you give up, when you try to solve a problem for real they sort of give away the classification while you are reading the problem statement.
Edit: Since minuses indicate that this is not welcome anymore. I will no longer post links to my blog or mention it in this site when I write explanations about a Codeforces round.
More shameless plugs.
Some explanations. Edit: Ok, D and E are ready. Albeit the explanations are vague...
It may be pointless to do this. Nickolas wrote the problemset and she likely has an editorial ready.
Hopefully I'll get out of division 2 with this.
It wasn't a great day, but at least there are explanations for problems B to E.
So sad, I would have solved C in round 8 since I noticed how to make my memo solution work in time (by making it forcefully consume the first element that is still in the bitmask) but... So what I did was that when I encode the used pairs, I use (x,N) for a "pair" that is just a single element, that's what generated the mistake: