No I did not copy paste wrong, the JSON parser cannot parse the received data from this API because the ‘source’ value data are incorrect formatted in result to brake up the API.
Also the example of the users/search in https://dev.twitter.com/rest/reference/get/users/search cannot be parsed by mine JSON parser neither into any of the online JSON Viewer’s tools on internet.
EDIT: I think the ‘source’ value data should be URLEncoded in order to not break the hole API JSON results
Example:
"source": "<a href="//www.tweetdeck.com%5C%22" rel='\"nofollow\"'>TweetDeck</a>",
Should be:
"source": "%3Ca%20href%3D%22%2F%2Fwww%2Etweetdeck%2Ecom%255C%2522%22%20rel%3D%27%5C%22nofollow%5C%22%27%3ETweetDeck%3C%2Fa%3E",