Skip to content
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

Open
vEnhance opened this issue Dec 13, 2023 · 3 comments
Open

Feature request: anti-laziness features for testsolvers #80

vEnhance opened this issue Dec 13, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@vEnhance
Copy link

Proposal:

  • Prevent giving up on a testsolve early.
  • Prevent testsolving multiple problems at once.

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.

@vEnhance
Copy link
Author

vEnhance commented Dec 13, 2023

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).

@vEnhance
Copy link
Author

just to reiterate the proposal from Discord:

Let everyone pick a role upfront: casual or serious

For casual testers:

  • Access to all problems and solutions, no locks or timers
  • Their job is finding and upvoting the best problems. They'll narrow the longlist down to a shortlist of 20-25 problems.
    It's fine if they just browse and pick what grabs their interest
  • We're not looking for strict contest conditions - their solve times will be unofficial

The "official" solves come from serious testers, who provide real data on problem difficulties.

  • If they focus on the shortlist of 20-25 problems, we could get higher per-problem coverage, even with fewer serious testsolvers
  • Problems like * get way more testsolvers than average, thanks to the upvote count. People want to work on high-quality problems.
  • They can work in parallel with casual testers. No need to wait for a formal shortlist, just testsolve as new favorites emerge

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).

@vEnhance
Copy link
Author

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.

@howard36 howard36 added the enhancement New feature or request label Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants