a sort of primordial ooze for programs about natural language.
variously, "mission impossible", "my introduction", or "message instantly", this chatbot answers questions using an unannotated corpus of data, namely, a list of answers, each with several questions that the given answer might correspond to. in this sense, it's more about categorization than question answering.
the bot implementation(s) are somewhat decoupled from the messaging services, and messaging over Slack is supported.
connecting the bot to Slack requires appropriate permissions in a workspace. the email address that is used to create a workspace will have appropriate permissions.
after logging in to a workspace with appropriate permissions, create a bot user, copying down the API token before saving.
to add a bot to a channel, @botname in that channel.
to remove, /kick @botname.
for dev and deploy, fill in the config files
mibot/resources/config/dev.edn.example
mibot/test/clj/mibot/slack_test_fixture.edn.example
with channel names and bot tokens
the program is designed to be used from Clojure repl.
before firing up the repl, there's a a small amount of "glue" to Java libraries that need be compiled, so run
mibot$ lein with-profile base javacfirst and every time src/java changes.
then run lein repl to start the repl, and from there
(go :some-bot)and(stop)will start and stop a bot called:some-bot, provided:some-botis present in bothconfig/dev.ednand(keys user/bot-constructors)(run-all-tests)will stop the currently running bot, make certain the repl has the current state of the source tree loaded, and (of course), run all the test files.
the Slack integration is currently the only halfway worthwhile thing about this portion of the repository. few of the half-formed ideas floating around the source tree have coalesced into chatbot form. also, as you've probably already gathered from this readme, the codebase is somewhat lacking in design stamina due to a prioritization of fiddling with the bot implementation over clean code in all namespaces.