Despite claims to the contrary, Twitter seems to be escaping ampersands in the JSON response. And <> will need to be converted anyway

Claims to the contrary:

- http://code.google.com/p/twitter-api/issues/detail?id=1695
Merge pull request #9 from firesock/master

Despite claims to the contrary, Twitter seems to be escaping ampersands ...