Write a message handler that captures !meme <search terms> that does a Google video search to find most relevant video and echoes the link and shorttext back into the channel.

Example usage:

<cwvh> compress twice for half the savings
<jane> !yt hank hill do I look like a jpeg
<botplate> http://youtu.be/QEzhxP-pdos - "For when someone posts a compressed image/uses Windows XP to save a jpeg..."
<cwvh> exactly.

If anyone has bot ideas that they wanted to throw out, toss 'em in here.

There is currently a validate method stubbed out.

Right now, Any IRC server that is speaking the correct protocol will not cause problems.
However, an ill-formatted message will cause us to crash.

Validation and error checking should be implemented according to RFC 2812

Perhaps an exception should be thrown on an invalid message, or maybe just return null. That is still up for discussion.

Regardless, IRCBot should not go down on an invalid message.

Add application level logging with a logging library like log4j. For bonus, add the ability to write logs to IRC to help with remote debugging.

Some handler that responds to !<botname> help or maybe just !help

This might include adding another abstract method to the handler class, which is something like

abstract string getHelpMessage();

This way, the help handler could iterate over all the bots handlers and tell us about the functionality of each handler the bot has

Currently MessageHandler works with raw IRC messages.

It would be nice for the core bot to parse incoming messages into some object that corresponds to an IRC message according to the IRC client protocol, RFC 2812

MessageHandler would then have to be changed to work with Messages rather than raw strings

Investigate moving transport from java.io to netty

Edit the top-level README.md to include how to build BotPlate and have the bot join #ufoa-acm channel on freenode.

Be sure to lookup how to stylize your instructions with Markdown so that they are easy to read!

According to the IRC Protocol there are 2 cases for message parameters.

The current implementation of Message.java removes the prefix and the command, then splits by a space character to seperate the parameters and trailing part of the message.

In the case where the separation between the parameters is implicit due to there being exactly 14 parameters, all space characters will be removed from the trailing part of the message.

First write a test case which exercises this bug, then fix it.

Convert MessageHandler.java to an interface and write a concrete implementation for "PONG" messages that implements your new interface.

Modify BotPlate to read from a configuration file for its username, IRC network, port, etc. This could change the API of IRCBot.java or you might have another class that reads configuration and then constructs an IRCBot. Investigate modern configuration formats such as XML, YAML, JSON.

Convert things like class IRCBot to the preferred case style of class IrcBot. Look through all the source code and directory names for similar change opportunities.

BotPlate should be testable on a local developer machine without requiring a network connection or actual IRC server. Investigate the use of a dependency injection framework such as Google Guice.

New to DI? You can start with a video describing what "factories" are, and how DI makes code simpler to read, easier to test, and easier to modify.

Java has a some fairly established guidelines for formatting source code. This task would be to re-format all the source files in BotPlate. Eclipse can do this, but be careful, you might accidentally have hard tabs enabled!

When making stylistic fixes it is important to change only the style. Do not be tempted to fix code or make new features as it makes reading the changes as a reviewer very difficult.