errors=panicOk, and that should be #GlitchBot (being) moved, I think.
RIP @glitchbot, long live @glitchbot !
(Huh, the git shorthash not having any letters in it makes it look fake. XD )
Ugh, #GlitchBot still doesn't have a new home and botsin.space goes read-only tomorrow.
*sigh*
Guess I know what I'll be doing that day...
Guess #GlitchBot will need a new home again. :/
Ok, of course I couldn't leave it alone so now it should be fixed. XD
(Turns out if you updated the environment and thought you deployed the code that uses that new environment, but don't check if that actually happened, then you can get issues.
Who would have thought.)
Hmmm, not sure what's up with #GlitchBot but it's not working.
Let's hope a restart fixes it...
It took waaaaaay longer than I thought or wanted, but #GlitchBot is now running with way more current libs and so can also understand WebP pics.
(Thanks to the one user who has tried feeding it a webp pic. This one's for you.)
Anyway, everything should work as expected again.
What I want to do: Making a tiny bugfix in #glitchbot
What I'm actually doing: Debugging the shaky tower of python environments and dependencies to find the error that stops me from actually starting on the bugfix.
Ugh, WebP...
Every now and then #glitchbot sends me an error message as catches some exception or other and on one hand I should probably hunt down that error and fix it, but on the other hand it's a nice reminder the bot is still running? XD
errors=panicEvery now and then I look into my #GlitchBot's mentions and see that people actually use the thing and that makes me very happy. 
