Real-time geolocated tweets

iambot wrote: post #3

I'm not seeing anything happen... just a map, and a bunch of xhr-polling requests (I'm assuming from socket.io)... - using firefox 13 on Win7

Try again.

Re: Real-time geolocated tweets

#5

Post by far-I » Sat, Jun 16, 2012, 5:23 PM UTC

Tyrant505 wrote: post #2

This is almost addictive to watch. Very impressive!

that's exactly what I was going to say! I love it. It's funny, I live in Nova Scotia, Canada and there's a tweet every 5 minutes, not even.

Re: Real-time geolocated tweets

#6

Post by antihero » Sat, Jun 16, 2012, 5:42 PM UTC

Hey that's pretty neat. Would be cool to style it up so it's beautiful.

Re: Real-time geolocated tweets

#7

Post by timaelliott » Sat, Jun 16, 2012, 5:51 PM UTC

Something is broken, at least for me. It always resorts to XHR-polling instead of websockets.

http://pure-waterfall-1016.herokuapp.com/socket.io/1

Always returns xhr-polling method which really isn't ideal for this.

Re: Real-time geolocated tweets

#8

Post by danzajdband » Sat, Jun 16, 2012, 5:56 PM UTC

timaelliott wrote: post #7

Something is broken, at least for me. It always resorts to XHR-polling instead of websockets. http://pure-waterfall-1016.herokuapp.com/socket.io/1 Always returns xhr-polling method which really isn't ideal for this.

It's not broken. Heroku free plan doesn't allow for websockets. The demo code on https://github.com/danzajdband/Tuiter/tree/master/examples/m... it's prepared to use webosockets first.

Re: Real-time geolocated tweets

#9

Post by timaelliott » Sat, Jun 16, 2012, 5:57 PM UTC

danzajdband wrote: post #8

timaelliott wrote: post #7

Something is broken, at least for me. It always resorts to XHR-polling instead of websockets. http://pure-waterfall-1016.herokuapp.com/socket.io/1 Always returns xhr-polling method which really isn't ideal for this.

It's not broken. Heroku free plan doesn't allow for websockets. The demo code on https://github.com/danzajdband/Tuiter/tree/master/examples/m... it's prepared to use webosockets first.

Ah, well that sucks but explains why it was occurring :)