[twitter-dev] Frozen timelines
Hi A number of my users, including me, are reporting that their /statuses/ home_timeline is frozen from about 10 hours ago. It only seems to show your own updates in the stream and nothing from anyone else. Any ideas or news on this? Many thanks Richard
[twitter-dev] tidy method for spotting new followers?
I've been asked to produce an automated response to new followers and I'm scratching my head over how to go about handling this. I have the login to the accounts in question, we're not fancy enough to have Oauth, and I may or may not have access to the email account behind the given Twitter ID. I don't think a third party Oauth tool fits with where we're headed. How are others doing this? Scanning followers, greeting, and then putting them on a private list of those who've received a greeting? We minimize the amount of context we keep as a matter of policy - if we can perform a given process with DMs, lists, and favorites it's very likely something we ought to not be doing in the first place. So ... I am curious to hear how others have solved this problem. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717
Re: [twitter-dev] Best way to auto-discover new followers
A method via the streaming API to get friendship / follower updates would be nice. Now it may be better to use the users/followers method instead of followers/ids. The reason is this is ordered from newest to oldest based on when the user followed you. So you would start paginating from the start and keep going until you reach a known follower. At that point you should have a list of all new followers. You would still need to scan the entire follower list to find unfollows (if you need that info). Josh On Sat, Mar 13, 2010 at 1:31 PM, Zero zeroh...@qoobly.com wrote: I currently need to auto-discover new people who have started following me. Here's how I do it: 1. Periodically pull in my followers using '/followers/ids.json'. 2. Compare to my list of known ids to find new ids. The slight downside of this is it seems somewhat inefficient (for twitter). If there was access to an event stream of follow/unfollow requests this would be much easier. It also seems like it could be done with less latency. That is, if I have a lot of followers, I'm not going to want to burden the system by fetching the whole list at a high frequency. However, if I were just fetching the latest follows, it seems like I could do this at a higher frequency and not affect twitter. Questions: 1. Is there a better way to do what I want with existing API? 2. Are there emerging features that could make this better? Thanks, Zero
Re: [twitter-dev] Best way to auto-discover new followers
Oh and also the benefit of users/followers is it includes all the user information. If you are just maintaining a social graph of ids, then pulling down all the ids via followers/ids would be the way to go. I think for most users this just requires a few requests. Josh On Sun, Mar 14, 2010 at 9:42 AM, Josh Roesslein jroessl...@gmail.comwrote: A method via the streaming API to get friendship / follower updates would be nice. Now it may be better to use the users/followers method instead of followers/ids. The reason is this is ordered from newest to oldest based on when the user followed you. So you would start paginating from the start and keep going until you reach a known follower. At that point you should have a list of all new followers. You would still need to scan the entire follower list to find unfollows (if you need that info). Josh On Sat, Mar 13, 2010 at 1:31 PM, Zero zeroh...@qoobly.com wrote: I currently need to auto-discover new people who have started following me. Here's how I do it: 1. Periodically pull in my followers using '/followers/ids.json'. 2. Compare to my list of known ids to find new ids. The slight downside of this is it seems somewhat inefficient (for twitter). If there was access to an event stream of follow/unfollow requests this would be much easier. It also seems like it could be done with less latency. That is, if I have a lot of followers, I'm not going to want to burden the system by fetching the whole list at a high frequency. However, if I were just fetching the latest follows, it seems like I could do this at a higher frequency and not affect twitter. Questions: 1. Is there a better way to do what I want with existing API? 2. Are there emerging features that could make this better? Thanks, Zero
Re: [twitter-dev] Frozen timelines
This is (was) a known issue. Status blog update here http://status.twitter.com/post/447344319/some-users-experiencing-frozen-timelines ---Mark http://twitter.com/mccv On Sun, Mar 14, 2010 at 1:13 AM, Rich rhyl...@gmail.com wrote: Hi A number of my users, including me, are reporting that their /statuses/ home_timeline is frozen from about 10 hours ago. It only seems to show your own updates in the stream and nothing from anyone else. Any ideas or news on this? Many thanks Richard
[twitter-dev] Additional Delimiter
I'm consuming the Streaming API using the filter method (tracking some
user ids). I've noticed that I'm getting an extra, undocumented, line
before each length delimiter.
I connect and get the following coming down the pipe:
{{{
HTTP/1.1 200 OK
Content-Type: application/json
Transfer-Encoding: chunked
Server: Jetty(6.1.17)
5DE
1496
{coordinates:null, ... snip ..., id:10487365330}
A52
2636
{coordinates:null, ...snip ..., id:10487377907}
592
1420
{coordinates:null, ... snip ..., id:10487298462}
}}}
Now, the Streaming API docs say, Statuses are represented by a
length, in bytes, a newline, and the status text that is exactly
length bytes. Note that keep-alive newlines may be inserted before
each length.
This suggests the following read loop code (based on and equivalent to
the way tweepy's consumer is implemented):
{{{
length = ''
while True:
c = s.recv(1)
if c == '\n':
break
length += c
length = length.strip()
if length.isdigit():
length = int(length)
status_data = s.recv(length)
# do something with the data
}}}
However, if you look at the third status data from above, you see that
the extra line can sometimes be a digit, in that case ``592``. Which
fairly effectively borkes the consumer.
Now, I can hack that read loop in quite a few ways to accomodate this
extra data coming down the pipe. Question is, what's the best way to
do so? Is this something I can rely on, e.g.: I can look for a line
above the length delimiter? Will it always have three chars? Do
statuses always have 1000 bytes?
Plus I'm wondering whether this has always been the case, or if there
are broken consumers missing tweets out there?
Thanks,
James.
Re: [twitter-dev] Search by Client
from http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search http://search.twitter.com/search.atom?q=landing+source:tweetie On Sun, Mar 14, 2010 at 3:33 PM, Christian christian.frei...@googlemail.com wrote: Hi There, is it possible to reveal all Tweets placed by a specific client (my client)? Hope someone could help me THX Chris -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Best way to auto-discover new followers
Thanks for the tip, I do have to augment the information by fetching the user info with a second call, so this will eliminate all that messiness. On Sun, Mar 14, 2010 at 7:45 AM, Josh Roesslein jroessl...@gmail.comwrote: Oh and also the benefit of users/followers is it includes all the user information. If you are just maintaining a social graph of ids, then pulling down all the ids via followers/ids would be the way to go. I think for most users this just requires a few requests. Josh On Sun, Mar 14, 2010 at 9:42 AM, Josh Roesslein jroessl...@gmail.comwrote: A method via the streaming API to get friendship / follower updates would be nice. Now it may be better to use the users/followers method instead of followers/ids. The reason is this is ordered from newest to oldest based on when the user followed you. So you would start paginating from the start and keep going until you reach a known follower. At that point you should have a list of all new followers. You would still need to scan the entire follower list to find unfollows (if you need that info). Josh On Sat, Mar 13, 2010 at 1:31 PM, Zero zeroh...@qoobly.com wrote: I currently need to auto-discover new people who have started following me. Here's how I do it: 1. Periodically pull in my followers using '/followers/ids.json'. 2. Compare to my list of known ids to find new ids. The slight downside of this is it seems somewhat inefficient (for twitter). If there was access to an event stream of follow/unfollow requests this would be much easier. It also seems like it could be done with less latency. That is, if I have a lot of followers, I'm not going to want to burden the system by fetching the whole list at a high frequency. However, if I were just fetching the latest follows, it seems like I could do this at a higher frequency and not affect twitter. Questions: 1. Is there a better way to do what I want with existing API? 2. Are there emerging features that could make this better? Thanks, Zero
Re: [twitter-dev] Additional Delimiter
On Mar 14, 2010, at 5:43 PM, thruflo wrote: […] However, if you look at the third status data from above, you see that the extra line can sometimes be a digit, in that case ``592``. Which fairly effectively borkes the consumer. From that list you posted: 0x5DE is 1496 + 6 bytes (4 bytes for “1496” plus 2 LFs) 0xA52 is 2636 + 6 bytes 0x592 is 1420 + 6 bytes Now, I don’t know whether it’s correct that it’s returning a length in hex followed by a length in decimal, but the lengths do appear to be correct if you interpret the first number as hex. Twitter will have to respond whether this is the correct behavior or not. — -ed costello
Re: [twitter-dev] Additional Delimiter
On Sun, Mar 14, 2010 at 5:43 PM, thruflo thru...@googlemail.com wrote: [..] I've noticed that I'm getting an extra, undocumented, line before each length delimiter. What's the command you're sending to twitter and the URL you’re using? I can’t replicate this (am just getting the decimal length in the responses). -- -ed costello
Re: [twitter-dev] Additional Delimiter
You appear to be looking at the raw HTTP chunk transfer encoded stream. The
documentation assumes that you are using a HTTP client, not the raw TCP
stream. If you are using the raw TCP stream, you can try to play games and
use the chunk encoding, but there are no guarantees that the chunks will
always align with the payload.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Sun, Mar 14, 2010 at 3:43 PM, thruflo thru...@googlemail.com wrote:
I'm consuming the Streaming API using the filter method (tracking some
user ids). I've noticed that I'm getting an extra, undocumented, line
before each length delimiter.
I connect and get the following coming down the pipe:
{{{
HTTP/1.1 200 OK
Content-Type: application/json
Transfer-Encoding: chunked
Server: Jetty(6.1.17)
5DE
1496
{coordinates:null, ... snip ..., id:10487365330}
A52
2636
{coordinates:null, ...snip ..., id:10487377907}
592
1420
{coordinates:null, ... snip ..., id:10487298462}
}}}
Now, the Streaming API docs say, Statuses are represented by a
length, in bytes, a newline, and the status text that is exactly
length bytes. Note that keep-alive newlines may be inserted before
each length.
This suggests the following read loop code (based on and equivalent to
the way tweepy's consumer is implemented):
{{{
length = ''
while True:
c = s.recv(1)
if c == '\n':
break
length += c
length = length.strip()
if length.isdigit():
length = int(length)
status_data = s.recv(length)
# do something with the data
}}}
However, if you look at the third status data from above, you see that
the extra line can sometimes be a digit, in that case ``592``. Which
fairly effectively borkes the consumer.
Now, I can hack that read loop in quite a few ways to accomodate this
extra data coming down the pipe. Question is, what's the best way to
do so? Is this something I can rely on, e.g.: I can look for a line
above the length delimiter? Will it always have three chars? Do
statuses always have 1000 bytes?
Plus I'm wondering whether this has always been the case, or if there
are broken consumers missing tweets out there?
Thanks,
James.
[twitter-dev] Twitter Search: The page you were looking for doesn't exist.
hi, am using twitter search returning json for webpage output. just got this messag returned with this url: http://search.twitter.com/search?q=ands=phrase=ors=nots=tag=lang=allfrom=gp04lchto=ref=near=within=15units=misince=2010-03-01until=rpp=15 seems i cannot use the 'Since this date' and 'Until this date'. please rectify. regards
