Hrm this happens sometimes when the Twitter API fails in a weird way. Try again? One of the cool things of Tweepsect is it runs 99% in-browser JS (including al

Hrm this happens sometimes when the Twitter API fails in a weird way. Try again? One of the cool things of Tweepsect is it runs 99% in-browser JS (including all the API calls). There's only a small piece of the OAuth that had to be done server-side which lives on AppEngine. I need to add better error handling to that someday. :)