Then that all stopped. No more whitelisted IPs for search, no more new whitelisted accounts for API calls, and then they stripped all my whitelisted accounts of their 20k/hr API calls and put them all back at the standard 150/hr or whatever.
And what's worse is the network is bigger than ever. Instead of scaling API access up with network size, they scaled it down. This is really a shame as I think Twitter is terribly interesting to with it from an academic standpoint, but unless you have huge money to shell out for API calls or direct access you're screwed.
It's just one data point, but I was impressed with how much more efficient Chrome was than FF.
Chrome is 62% faster than Firefox, Safari 85% and IE10 67%
The following error was encountered while trying to retrieve the URL: http://tweetping.net/
Connection to 184.108.40.206 failed.
The system returned: (111) Connection refused
The remote host or network may be down. Please try the request again.
Your cache administrator is webmaster.
iam love twitter and right now iam watching a show called #domian and iam looking for that hashtag and there are per minute about 30 tweets and i dont see them on your site.
iam from germany.
or did i just overlooked something?