Dan Boger
Dan Boger
out of ~140k factoids, about 5 will be affected. Still think it should be a plugin though, not on by default -- both for avoiding unneeded complexity in the main...
Yeah, should have a default value for that column, and either start making use of it or just remove it all together.
Back in the day, this was the thinking: RE - a flag that indicates that the trigger for the factoid wasn't a string, but is a regular expression, and should...
I'd suggest opening new issues for the ones you want to implement. I think this particular issue is obsolete? On Thu Feb 05 2015 at 12:15:05 PM dgw [email protected] wrote:...
Yeah - parsing that might be tricky. If we do, supporting 'replace foo with bar there' might be nice too - edit on the last returned factoid. And I'd certainly...
We used to have support for that, and decided it was too spammy (especially that last one). If we going to restore it, it should be guarded in a config...
I'd say if it's a plugin, we can have it off by default, and have it added to the sample config, so that new installs will have it on.
Wait, who else would have access to these things in the database? Ideally, I'd want just 'db_*' to remain in the yml.
Yeah, not a bad idea to implement a 'password' field, which can only be SET in privmsg, and never read. Also, the yml file should still support specifying irc server...
As mentioned in the other issue, I think all formatting should be stripped from triggers before they're matched. On Sat, Oct 1, 2016 at 2:58 PM dgw [email protected] wrote: >...