-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature request: anti-laziness features for testsolvers #80
Comments
Maybe preventing quitting testsolves is a bit draconian since i guess sometimes the problem sucks or the author fucked up the answer. I just think there should be some mechanism preventing people from just like recklessly creating and terminating testsolving sessions (e.g. rate limit). |
just to reiterate the proposal from Discord: Let everyone pick a role upfront: casual or serious For casual testers:
The "official" solves come from serious testers, who provide real data on problem difficulties.
I like this suggestion. I propose the names "casual" and "hardcore". And in the acknowledgments we'd split those by role (hardcore is a lot more work, so I'd like to give extra shout-out to people who are willing to do it). |
I think we can also allow hardcore => casual after people are satiated from testsolving and want to cruise through the rest of the list to see what else they did. So maybe for acknowledgments, we'd include a special shout-out to everyone who solved at least N problems / M bulbs correctly before switching to casual, and then include everyone in the general testsolver list. |
Proposal:
We have an issue with people who just want to look at the problems but don't actually want to put in the effort to testsolve them which is ruining the feedback system.
The text was updated successfully, but these errors were encountered: