README rejiggering

Added some info on a fork I found, and reorganize/revise the change list.

README.md

@@ -7,6 +7,10 @@ license and copyright Tamás Márki.
 
 The original code was itself a port of a mIRC script, probably the one found at http://hawkee.com/snippet/5301/
 
+There is also an unobot.py version maintained within the @myano/jenni repo, but it is as different from this version
+as this version is from the code it was built on. A few ideas from that repo may make their way into this one at some
+point, but most of the development here up to now was done before discovering the other fork.
+
 ## Changes
 This fork includes (but is not limited to including) the following updates:
 
@@ -19,12 +23,14 @@ This fork includes (but is not limited to including) the following updates:
 * Added `cards` command for players to have the bot send them their hand again in case they were in another channel
   when their turn came and the notice was therefore sent to the wrong window.
 * The module now supports a game in each channel, rather than being limited to playing UNO in only one channel.
+  * Games can be moved from channel to channel, as well, by the game owner or a bot admin, so as to allow a flourishing
+    discussion in a channel where UNO is being played to continue uninterrupted while the game moves elsewhere.
+  * The bot owner can query for a list of channels in which UNO games are running (useful as preparation for updates,
+    bot server maintenance, etc.).
 * Score saving uses JSON objects instead of hardcoded format strings. While less compact, it is much more easily
   understood by a human reader, and is easier for the bot owner to edit if corrections are needed.
 * The "top 10" list has been renamed from `unotop10` to `unotop` and only displays five (5) entries to reduce spam to
   the channel.
-* The bot owner can query for a list of channels in which UNO games are running (useful as preparation for updates,
-  bot server maintenance, etc.).
 * Use new decorators from Phenny's successor, Willie, soon to be renamed to something else, probably for the last time
   — see #willie @ freenode. This project's name will likely change to match Willie's new name when it is decided.
 * Updated syntax to take advantage of new bot framework features.