Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new (optional) method of detecting account sharing. If enabled, the script will keep track of a user's history and analyze it for account sharing.
The following settings are added to change how this works:
USER_HISTORY_BAN_ENABLED
: This variable is a boolean flag that enables or disables the history-based banning feature. Set to "true" to enable history-based banning, and "false" to disable it. On a busy server, this can potentially consume a large amount of memory, especially ifLOOP_DELAY_SECONDS
is set very low, orUSER_HISTORY_LENGHT_HRS
is set very high.USER_HISTORY_LENGTH_HRS
: This variable specifies the duration in hours for which the user's streaming history should be considered when evaluating for history-based banning.USER_HISTORY_BAN_IP_THRESH
: This variable sets the maximum number of unique IP addresses a user is allowed to have in their streaming history within the specifiedUSER_HISTORY_LENGTH_HRS
before being considered for account sharing.Fixes #14