Weechat: anti_flood_prio_high and low in milliseconds instead of seconds

Created on 22 Jul 2017  路  3Comments  路  Source: weechat/weechat

Hello,

It would be nice to have these settings in milliseconds instead of seconds.

Currently you can only set it in seconds, and when sending multiple lines at a time the output speed is too slow even if set to 1 second, and if set to zero seconds the output is too fast and it usually triggers server side flood protections and you get kicked (as you should).

So my suggestion would be for this parameter to allow settings like 100ms, 300ms, 500ms, etc. (without the ms) which is usually faster for sending multiple lines and you can fine tune it for each network's flood protection threshold.

I could help with the development if necessary.

Thanks!

feature

Most helpful comment

Yes, @sim642. So if the unit is changed, the options will be renamed. Users will lose the old value (with a warning), but there will be no confusion with the value between seconds and milliseconds.
I already planned to change this unit and use milliseconds, which will cause some changes in the internal IRC timers.

All 3 comments

The issue with changing the unit used by these options is that it'd break all existing configurations. Someone with a default value of 2 (s) currently would after this change have it at 2 (ms), which is not what they wanted.

Yes, @sim642. So if the unit is changed, the options will be renamed. Users will lose the old value (with a warning), but there will be no confusion with the value between seconds and milliseconds.
I already planned to change this unit and use milliseconds, which will cause some changes in the internal IRC timers.

Thank you @flashcode!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tyll picture tyll  路  7Comments

mitchellwrosen picture mitchellwrosen  路  5Comments

craigmaloney picture craigmaloney  路  3Comments

victor-catalyst picture victor-catalyst  路  4Comments

Strykar picture Strykar  路  4Comments