limit frequency of ban activations within a time period

shelleybridge commented

2018-08-02 16:32:41 +00:00

(Migrated from github.com)

With the proliferation of cloned accounts in telegram, the instance of malicious attack by a single or group of people using cloned accounts to outvote and mass ban members indiscriminately during non-peak graveyard hours is an increasing risk. By having a parameter to set total number of allowable bans within a time period (e.g. 10 bans within a 24-hour time frame) will prevent such mass ban flooding as a result of this malicious intent.

shelleybridge commented

2018-08-02 17:36:37 +00:00

(Migrated from github.com)

if the above suggestion is not easy to implement, perhaps just having a minimum time period from last ban user set parameter will suffice (e.g. last ban must have been x mins before new ban voting can happen). the time lag between each new ban may be enough to dissuade such ban flooding attacks

backmeupplz commented

2018-08-02 18:24:29 +00:00

(Migrated from github.com)

Nice suggestion. I'll implement the setting for the time delay between bans then

shelleybridge commented

2018-08-02 22:45:37 +00:00

(Migrated from github.com)

Cool! Thanks so much for your time and effort in doing this. cheers mate

backmeupplz commented

2018-11-27 07:19:29 +00:00

(Migrated from github.com)

@shelleybridge you can now specify the time limit in /time ;)

Rows
Columns

limit frequency of ban activations within a time period #6