dgw
Cleared @HumorBaby as assignee, since he's been very busy lately. This is up for grabs if anyone has the itch to work on it.
@Exirel That should be sopel-irc/sopel-extras#34, but yes. :grin: I'm actually going to retitle the issue, because referring to them as "mIRC control codes" is no longer accurate. While mIRC may...
Implementation thought: https://github.com/sopel-irc/sopel/issues/1768#issuecomment-625857898
After implementation discussion on IRC, we've (@Exirel and I) decided that it'll be cleaner to do this in 8.0 after we no longer have to worry about Python 2 support.
We are now in the 8.0 dev cycle and firmly located in py3-only land. This can be implemented with the use of keyword-only arguments to the relevant decorators now.
Postponed for rework of internals to make this and other rule-related features work better. You can see some of the discussion [here](https://github.com/sopel-irc/sopel/pull/2288#discussion_r920529011) (the rest was on IRC).
If the command becomes `.update --yes`, then someone will complain that it should be `.update --yes --really`… But a nonce approach would be reasonable: `.update` (or the `nickname_command` equivalent) on...
Could be a good start, yeah. Thanks for the pointer! I'm just shaking my head a bit that you didn't even have to change the docstring for `core.hostmask_blocks` in that...
Pushing off to Sopel 7. Version 6.6.0 has gotten too bloated, and this can wait until the next major release.
Just a few weeks left before target release date for 7.0 and this isn't even started. It can wait.