eir
eir copied to clipboard
Eir is an IRC client bot framework, written primarily for freenode utility functions. It is, however, highly extensible using C++ or Perl, and is used by other projects as well.
Profiling has determined that this is due to the eir computing the bot privset for each user it sees on join. One proposal to fix this is to defer this...
we could change `WHERE mask LIKE ?` to `WHERE LOWER(mask) LIKE ?` and pass the query mask in lowercased, but that's not IRC casefolding. might be difficult to do this...
this isn't a massive problem but if someone is called `[]` it's a bit weird to see a log notice for `{}` setting a ban
In `cmd_query`, $sender is not lowercased, while in `cmd_btset`, it is. https://github.com/freenode/eir/blob/06b7e42eb297fcb3f9c7a63d7d899b064d070446/scripts/bantracker.pl#L312 https://github.com/freenode/eir/blob/06b7e42eb297fcb3f9c7a63d7d899b064d070446/scripts/bantracker.pl#L373
``` Please comment on the following: ban[127515] nick!user@host was set on #channel by stwalkerster!~stwalkers@wikimedia/stwalkerster on 2019-10-15 09:52:35Z and had an expiry date of 2019-10-16 09:52:35Z. ~999999999d my reason for "essentially...
This is the output of ./eir: ``` Aborting due to exception: * /root/eir/modules/storage/json.so: undefined symbol: _ZN4Json5Value4nullE (std::exception) ```
Currently, if an op sets a ban duration in a format eir doesn't recognize (e.g. `~1y` thinking it will be a year-long ban), this will silently assume the ban to...
This should fix issue #16.
Context Often we quiet someone, then the quiet expires, we need to re-quiet (soon, or not soon), and we start thinking what duration to set. Was the user a problem...
1. I set the ban: 17:01 -!- mode/#wikimedia-ops [+b $x:Lorena_ramos_💜] by Luke081515_ (default expiry 5h for that channel) 2. eir tried to remove it: 22:09 -!- mode/#wikimedia-ops [-bo $x:Lorena_ramos_ð_R\ eir]...