Yep. I was part of the Web Ecology Project in 2009-2010 and we were able to get pretty awesome access to Twitter at the time. I had a good dialog on a weekly basis it seemed with their API team and they were super responsive and supportive of us. Although, whenever I asked what we needed to pay for full Firehose (which some companies were getting) I couldn't get an answer from them, and I think they only wanted to talk with huge companies.
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.
There's so much potential information there, and some very neat things you can do with it. But for me at least, their new API policies completely turned me off of making cool things with it. Not that the API isn't still powerful.
Very cool! Mind providing some background on how you've rendered the world map and determine tweet coordinates? Are you mapping the tweets' latitude and longitude through some projection formula?
This was really cool. The office is having internet connectivity problems right now, and after we fixed it, this page loaded, and for a brief moment, I felt like a hacker from the movies :D
Curious about the CPU usage of canvas apps on older systems, I ran this in FF and Chrome. (I'd classify the system I'm on at the moment as a mid-tier business PC from 2008.) FF maintained a CPU usage mostly in the 33-40% range and Chrome in the 18-23% range. CPU usage would spike up to 75-90% in FF, whereas the largest spike in Chrome was only 40%.
It's just one data point, but I was impressed with how much more efficient Chrome was than FF.
I made a project that is similar - shows a bit more information except its only for the US and you need to search a specific word/hashtag. http://tweetpleth.herokuapp.com/
Incredibly well done and excellent execution. However, there is a noticeable delay/lag that totally took me out of the user experience. Even though the concept was really cool, I wouldn't mind if everything was slowed down a bit so I get what's actually going on and there was a bit less lag.
that means the less popular locations get even less exposure, as there are plenty of places in the less developed world of which Twitter location (desktop) is unaware of.
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.
