-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select judge to submit on #79
Comments
Duplicate of #77. |
Sigh, misleading issue names. My bad. TooManyIssuesException. |
Wait, on further discussion with @FatalEagle this is not a duplicate and the title of #77 is what I thought it was, so not misleading. Reopened. |
We shouldn't encourage users to religiously select judges as it defeats the purpose of multiple judges. |
If it's a 3-level deep nested dropdown, it'd be pretty inconvenient to select at all times. Rather, I see people using regular submit until they have an AC solution, then submitting under the fastest judge for ranking. Which in my opinion is more fair since our judges have unequal capacity. |
Maybe require something even more annoying like a codecha to submit on a particular judge. |
Yea, something annoying like that would prevent abuse. |
And of course admin exemption from codechas. I REALLY REALLY HATE IT. |
Another idea: either submit codecha, or do a survey (a bit of funds for servers) to submit. http://screencloud.net/v/5rmi |
Alright as long as we make it hard but not too bad to warrant registering a new account. |
This'd be really nice for admins, and debugging. |
Useful to prevent spam submissions to get the fastest judge. Doesn't impact our performance much, either.
The text was updated successfully, but these errors were encountered: