I had a sort of aha moment last night. It involves more work on my Twitter app. Although I’m restricted by the number of calls I can make per week, I can work around that by using a different logic to get the information I’m requesting from Twitter. This involves a rather large rewrite of some workhorse portions of my code, but I’m going to work in some backup so that I can deal with Twitter status returns of 200/empty for accounts that really aren’t (this was a major issue in making this all work before). Most likely I’ll depend more on the statuses_count if I come across a reported empty that most likely isn’t really empty.
Twitter’s own API says:
Requests for more than the limit will result in a reply with a status code of 200 and an empty result in the format requested.
However, they’re responding with the same empty response/200 status when I’m asking via a valid request and I get drop-kicked by the unicorn.
I’ve got a few more ideas on how to make the app even more appealing from an information side as well, but I’m not going to list that here for fear of scope-creeping myself out of existence… also, I’m going to wait on reporting more information for when I can get what I originally wanted to display actually working consistently and accurately.
I think I figured out scale 
