[eluser]jpcody[/eluser]
Hmmm...looks like it's giving me a false boolean return. But this has nothing to do with Twitter actually going down. Could this be some sort of issue with exceeding a rate limit? Is there any way instead of running the database on a page refresh I can have it run in the background every so often? Every 10 minutes or so?
The API limits to 150 requests per hour, and I am making requests very often as I'm refreshing the page to test different things. I could very easily see this being the issue.