Tweetping, Twitter traffic in real time
31–40 of 41 posts
Re: Tweetping, Twitter traffic in real time
#32Re: Tweetping, Twitter traffic in real time
#33How 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
#34----
The following error was encountered while trying to retrieve the URL: http://tweetping.net/
Connection to 91.121.175.82 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.
Re: Tweetping, Twitter traffic in real time
#35Re: Tweetping, Twitter traffic in real time
#36Are you sure? the webpage showed me these: ---- The following error was encountered while trying to retrieve the URL: http://tweetping.net/ Connection to 91.121.175.82 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.
Re: Tweetping, Twitter traffic in real time
#37Earlier quoted context omitted.
Data come from the Twitter Streaming API https://dev.twitter.com/docs/streaming-apis
Is the site getting the firehose stream though? How do you get that level of access?
Re: Tweetping, Twitter traffic in real time
#38This is pretty awesome, but I would like to be able to dig in deeper. After looking at it for a couple minutes, there's really nothing more I can do.
Re: Tweetping, Twitter traffic in real time
#39Earlier quoted context omitted.
Is the site getting the firehose stream though? How do you get that level of access?
They're probably using the 'sample' firehose, which is not protected and still serves a few tweets per second.
Re: Tweetping, Twitter traffic in real time
#40Earlier quoted context omitted.
Is the site getting the firehose stream though? How do you get that level of access?
They're probably using the 'sample' firehose, which is not protected and still serves a few tweets per second.