globau / firebot Goto Github PK

karama module: 👍 as ++ and 👎 as --

currently firebot connects over :6667, which prevents it from joining channels that require ssl.

Today I got a weird ping from firebot, in this conversation:

noida: firebot you are dead to me
firebot: But you are 'ProgramFOX'...

Context: http://logs.glob.uno/?c=mozilla%23introduction&s=21+Dec+2014&e=21+Dec+2014#c188718

When capella said firebot: forget you are dead to me, firebot replied that it never knew "you are dead to me", and the command is still invokable.

What's so special about this command?

(4/6/2016 6:12:29 PM) firebot: New support.mozilla.org - Knowledge Base Software bug 1262653 filed by [email protected].
(4/6/2016 11:03:51 PM) firebot: New support.mozilla.org - General bug 1262723 filed by [email protected].

each of these should trigger firebot to fetch bug info (summary etc) from bmo and report.

people often have a different irc name, and most bugzilla accounts have them in the form of :ircname, so using that in the irc communication (to create a ping, or to let others link the bug owner with someone in the channel) would probably be more useful than the email handle.

the 'amo' command used to perform a google search on addons.mozilla.org.
as the google module is no longer supported, the amo command is gone.

it should be possible to hit amo's api to perform searching:
eg. https://services.addons.mozilla.org/en-US/firefox/api/1.5/search/adblock/all/4

return just the name and a link to the addon from the element (remove the querystring and /en-US). max line length of 250, max results 3

firebot, amo adblock
"Adblock Plus" https://addons.mozilla.org/firefox/addon/adblock-plus

sort of recently the seen command has started returning "i've never seen X" for all queries.
the database still contains the entries, and there aren't any errors thrown.
restarting firebot makes it work for a while before it fails again.

i suspect we're hitting some sort of bug with either DB_File or tie'ing due to the massive size of the seen databases. migrating seen to a sqlite database is likely to fix this.