Project name.

[Andrewnetwork]

Since we intend on dramatically widening the scope of what lambda bot provides, should we rename our fork to something else?

[calledtoconstruct]

I was thinking this as well!

Yes, I think we should. Always recognise the great work of the original team and the lambdabot project, but the purpose of this project seems to be somewhat different.

[Andrewnetwork]

If we are really going to double down and make this primarily a Twitch bot, we should probably name the bot to reflect that. Something like, for the lack of imagination, haskell-twitch-bot perhaps. Or we can make a name for it. Depends on people's goals and what they want to do with this. Also, if we start integrating with the twitch extension system, then we start going even beyond a bot. It's like a bot + twitch extensions backend server in that case.

[calledtoconstruct]

I don't know if I'd go as far as to say it's going to be primarily a Twitch bot, there are other streaming platforms, and systems like Discord, Slack, fb messenger, etc, that can be integrated with their own plugin.

However, I do agree that we are diverging from lambdabot significantly.

Here are some ideas:

• octothorpe-bot
  -- Use the # as the default prefix for commands.
  -- not sure if that would work on discord

• clerk-bot

• communicant

• robot-overlord