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.
Tweetping, Twitter traffic in real time
21–30 of 41 posts
Re: Tweetping, Twitter traffic in real time
#22Very 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?
Ya I'd like to know also
It's only geolocated tweets. No projection, just a render with Nodejs w/ Socket.io, Processing.js and Backbone.js !
Re: Tweetping, Twitter traffic in real time
#23what? no link to the github repo?
Re: Tweetping, Twitter traffic in real time
#24I just realized that they don't have twitter in Australia!! ;)
Re: Tweetping, Twitter traffic in real time
#25I think europa should be europe, for correctness's sake
Re: Tweetping, Twitter traffic in real time
#26How are they getting the data? Twitter's APIs seem so limited these days.
It struck me seeing this how rare it is now to see any kind of Twitter experiment. Complete 180 from a few years back.
Re: Tweetping, Twitter traffic in real time
#27Nice. I like trendsmap as well. www.trendsmap.com
Re: Tweetping, Twitter traffic in real time
#28Curious 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.
Re: Tweetping, Twitter traffic in real time
#29Curious 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 effi…
That's true! http://blog.lightjs.org/2013/01/svg-canvas-divs/
Chrome is 62% faster than Firefox, Safari 85% and IE10 67%
Re: Tweetping, Twitter traffic in real time
#30Sites Down - I'm upset I was trying to show this around.