* Display random words of encouragement for successfully redeemed passcodes
* Refactor redeeming into smaller functions, using more jQuery logic
* Add redeem "handlers" - combinations of "decoders" and "formatters" for each taxonomy of item
* Add heuristic item guessing. If IITC can't figure out directly what an item is, try to guess what taxonomy of item it would be closest to. (For instance, if an item is truly unknown, but has a "rarity" attribute, it's going to be close to a modResource. Likewise, if an unknown item has a "level" attribute, it's going to be close to a resourceWithLevels.
** Tailor formatting and decoding based upon that guess. Worst case: the item is truly a mystery. Don't discard it: display it in a default format.
** Let the user know if we tried to heuristically guess an item. This won't happen unless something changes on the Ingress backend.
* Show table by default, offer plaintext option for reward copy-pasting
* Use recommendations from https://plus.google.com/115907431535033114848/posts/PVV9j4fTR2m for item plaintext listing
* Break passcode redemption responses and errors into window.REDEEM_* variables
* If an item isn't known, don't simply let it slip into the Aurbis. Log it separately.
* Don't show AP or XM if the passcode didn't give any.
