From JRo's implementation

[Grissess]

Things added:

• Module: "spikebot" for limited interoperability with SpikeBot (currently only karma)
• Module: "inject" for injection/introspection using FIFOs on OSs that support them (currently *nixes, AFAIK)
• Library: "ircbot"; see below.

  Things changed:

• Better handling of Unicode: the ircbot library was incorporated under license and changed slightly to handle Unicode at the network level, where it is most stable. Other modules were slightly changed to accommodate.
• New hook functions in modules: "init" for startup, "finish" for shutdown.

[boamaod]

Thanks a lot, I appreciate the pull request, however I want to keep my branch as simple and as minimal as I can.

By that I mean that the main goal of my Skype to IRC bot is to broadcast Skype chat messages to IRC and vice versa, so different technologies or even ideologies incorporated in software (free/open software and protocols versus the rest) don't hinder the communication. However, all the extras provided by expandability of IRC can never made to be fully available through Skype, so I find there is no point in trying to force it. It's the problem of inferior software development model that Skype is using and I am not really in a position to solve this problem and I think I should not put my efforts into that.

However, I am willing to accept pull requests to implement Skype chat better or make the bot more universal and follow standards, good practises etc, but pull requests should be proposed in smaller functional chunks, so I can review the code. I also want to keep my branch modular, that is I don't want to hardcode and start maintaining modules, that can be used from their respective sources.

If you have hints of that kind of improvements made in commits embraced in your pull request, I can check these out myself, however making new pull requests would be more effective.