View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005675 | unreal | ircd | public | 2020-05-17 19:16 | 2022-01-04 22:50 |
Reporter | syzop | Assigned To | argvx | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | resolved | Resolution | fixed | ||
Product Version | 5.0.4 | ||||
Fixed in Version | 6.0.2-rc1 | ||||
Summary | 0005675: rate limit +x/-x | ||||
Description | Because such changes can be quite annoying, depending on client- and serversettings. Suggested by Koragg. | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
In my honest opinion, if such a rate limit is applied, it should only be applied to -x, that way if someone accidentally -x'es or is tricked into doing so they can easily +x again ASAP, however if +x is also reate limited then there can be a delay before they are able to do so. Plus with only -x being rate limited, you wont be able to +x until you have already -x'ed anyway so that in turn prevents a -x/+x flood as well. |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-05-17 19:16 | syzop | New Issue | |
2020-05-17 19:16 | syzop | Assigned To | => syzop |
2020-05-17 19:16 | syzop | Status | new => acknowledged |
2020-05-17 19:16 | syzop | Description Updated | |
2020-05-17 19:19 | Jobe | Note Added: 0021582 | |
2021-12-31 15:25 | syzop | Assigned To | syzop => argvx |
2021-12-31 15:25 | syzop | Status | acknowledged => assigned |
2022-01-04 22:50 | argvx | Status | assigned => resolved |
2022-01-04 22:50 | argvx | Resolution | open => fixed |
2022-01-04 22:50 | argvx | Fixed in Version | => 6.0.2-rc1 |