Sometimes copying passcodes from https://plus.google.com/communities/108599095839806789745 will contain an invisible character(s) at the end which causes it to be invalid. This patch will remove non printable characters from a passcode before submitting it to Ingress.
I've found the bytes 0xefbbbf sometimes appear which is a BOM character.
* Pass the entire acquired item into resource decoders instead of the attribute in question. Generic 'resource' objects have things we need to examine.
* Formatted support for the `resource' taxonomy (portal keys and JARVIS/ADA). Remove standard 'default' taxonomy in favor of this.
* Let individual items override their own primary key (for example, JARVIS/ADA are both a FLIP_CARD, but we don't want to smash them together)
* Let the server-side item name override the "hard-coded" name in IITC
* Assuming that passcodes can eventually work like portal hacks, add support for the MEDIA and PORTAL_LINK_KEY item types.
* Change plaintext and HTML display for modResources in anticipation of link amplifiers
* Log entire JSON response to the console if we have to guess about items.
* Add more encouragement.
* Add Jarvis/ADA JSON responses, fake media items, and fake portal keys to json_examples.
* Don't use digit format for plaintext redemption
* Remove unneecessary 'return true' statements
* Passcode guessing doesn't dirty up the results window as much
* Add asterisks to names for all types of guess
* 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.
