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

Lower ragequit/disconnect timeout if you have playbans #5252

Closed
wants to merge 463 commits into from

Conversation

thomas-daniels
Copy link
Member

Up to 4 playbans, the ragequit and disconnect timeouts stay the same. The timeout value goes down steeply from there on, to ~10% of the original value at 30 playbans. Here's a plot of the disconnect timeout (seconds) in function of the number of playbans you acquired:

Partial #5239

@thomas-daniels thomas-daniels mentioned this pull request Jul 3, 2019
8 tasks
@thomas-daniels
Copy link
Member Author

On hold until we have a good way to distinguish abusers and people with a very unstable connection (i.e. playban false positives).

ornicar and others added 27 commits July 22, 2019 09:48
as to discourage account creation bots
… the z-index of the button that toggles table/graph
#5244 upping the z-index of the plots in the lobby graph to be greater than…
ornicar and others added 24 commits August 15, 2019 08:53
Inactive player should become provisional in 365 days
* master:
  remove ur-IN in favor of ur-PK
  remove io-IO in favor of io-EN
    using unicode instead of innerHTML hook
  i18n: hidden puzzle rating
  simplify puzzle side view using trans.vdom
  i18n: mainline
  i18n: remove "only ongoing games"
  i18n: tweak simulAddExtraTime
  i18n: unauthorized -> unauthorised
  remove "Initial position" from renderIndexAndMove
  do not translate "FEN"
  update stockfish.js (v10.0.2: fix horde double pawn push)
  Revert "Inactive player becomes provisional in 365 days"
  keep params when switching study embed chapter
  Inactive player becomes provisional in 365 days
…nicar/lila into lower-dc-threshold-with-many-playbans
@thomas-daniels
Copy link
Member Author

thomas-daniels commented Aug 21, 2019

@ornicar Can we revisit this, with the sit/dc counter being implemented now? Please see my new commits.

Changes done: playbans needed is at least 4, sit counter must be -4 or worse. At this point, we can be pretty sure about them being abusers. Though, let me know if you want to tweak any number.
The new function for calculating when to consider someone "gone" is original * (1 - 0.8*sqrt(log10(x))) where x is playban_number - sit_counter (sit_counter is negative so it adds up here). This ensures a reduction to 25% (i.e. x = 8 = 4 - -4) to 0% (but let's make sure it doesn't go below 2%).

@thomas-daniels
Copy link
Member Author

I'm not sure what went wrong with that merge commit and why there are suddenly so many changes. I'll fix my stuff and just open a new pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet