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

Configuration of Flood Protection #1342

Closed
deathbybandaid opened this issue Jun 6, 2018 · 7 comments
Closed

Configuration of Flood Protection #1342

deathbybandaid opened this issue Jun 6, 2018 · 7 comments

Comments

@deathbybandaid
Copy link
Contributor

I think the Flood Protection should be configurable from the config file.

I have my bot behind ZNC for multiple reasons, and prefer the adjustability of it's flood protection, so the bot doesn't get kicked.

I think adding this to the core.config would be beneficial.

@dgw
Copy link
Member

dgw commented Jun 6, 2018

Not super high on the priority list right now, but a PR adding this would get a look.

@deathbybandaid
Copy link
Contributor Author

Do you think any of this is still relevant/usable?

f58fa9f

@dgw
Copy link
Member

dgw commented Jun 7, 2018

As far as I can see from #908, that was probably left unmerged because Embolalia pushed back on having config settings, and then @larsks closed it when the conversation stalled.

If you want to use that commit as a starting point (presumably you've read through #908 already?), I can't think of a reason not to. I would just ask that you rebase f58fa9f onto current master to keep credit for that code around in the commit log (and fix the typos in the commit message while you're at it, seeing as @larsks fixed them in the top PR comment anyway).

Out of courtesy, I also pinged @larsks. I think it's nice to ask people before building on unfinished code.

@dgw dgw mentioned this issue Nov 10, 2018
@dgw dgw added this to the 7.0.0 milestone Nov 13, 2018
@dgw
Copy link
Member

dgw commented Nov 13, 2018

This seems like a good feature to add in the next major version, so I've assigned it to the 7.0.0 milestone.

@deathbybandaid With no answer from @larsks in the last 5 months, I think it's safe for you to have at this if you're still interested in working on it.

@predakanga
Copy link

This feature is one of the last remaining roadblocks in un-forking our own copy of Sopel, so I thought I'd offer the patch myself.

@Exirel
Copy link
Contributor

Exirel commented May 21, 2019

so I thought I'd offer the patch myself.

Oh, that's lovely, thank you! ❤️ In one way or another, I hope Sopel 7 will be able to replace your fork, so you don't have to maintain it—I know how much time it can require!

@Exirel
Copy link
Contributor

Exirel commented Jul 6, 2019

As I see it, #1518 fixed that (and the documentation is on its way).

@Exirel Exirel closed this as completed Jul 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants