I messed up in the assertions and had the verify type as signed for some hosted assertions. The validator wasn't doing a great job of reporting or stopping on that error, so it would fall through and hit the `verify-hosted` error. I increased the error handling on `openbadges-validator` so when this happens in the wild we get better errors, and I fixed the problem here so we can actually test the hashed/unhashed hosted badges.
Addresses issue #167. When a string was being passed in before, it would not immediately fail and instead see it as an array with `"string".length` members which is dumb and wrong. Instead of making it error, I Just made it more lenient so that the first argument can be a string or an array.
Instead of a raw email comparison on the frontend, check recipient at the same time we check existence of a badge and send it back to the front.