Re: [twitter-dev] Re: 401 to site streams since yesterday
I've seen 2 things recently that can cause it. 1) Your user you connect with becomes deauthed from the app, or 2) I upgraded my version of roauth gems in ruby today, and it broke the way I was handling params and I was getting 401s. I expect your reason is probably something different though. Have you tried a verify credentials call with your user you connect with? Cheers, Tim. On Fri, Jul 22, 2011 at 1:17 AM, Fabien Penso fabienpe...@gmail.com wrote: Am I the only one having this issue? On Thu, Jul 21, 2011 at 9:19 AM, Fabien Penso fabienpe...@gmail.com wrote: Hi, Any idea why the site streams give me 401 for the last 16 hours ? I haven't changed anything and I don't understand why it would change? This is for @appnotification Thanks. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
Re: [twitter-dev] is sitestream losing tweets?
I haven't tested it thoroughly to be 100% certain it's the cause, but I suspect it's skipping the occasional fav and rt. Tim. On Wed, Jun 1, 2011 at 11:50 AM, Michael michaelzen...@gmail.com wrote: In my setting, user Y has authorized my user X for sitestreaming purpose. In most cases, whenever Y tweets, X can get it in 1~2 seconds. However, sometimes (say once a day), the tweet of Y was never received by X. Note that in the mean time, the http connection that X established with twitter is in fine condition. Has anyone observed the same thing? Or is sitestream beta known to lose tweet? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Twitter group API
No, there's not. On Tue, Mar 15, 2011 at 1:03 PM, Richard fireston...@gmail.com wrote: Does anyone know if there is program available to create several groups using one Twitter account and allowing you to message each of those groups individually? For example - Twitter.com/username Group 1 (100 followers) Group 2 (56 followers) Group 3 (77 followers) I would like to send separate messages to each of those groups. Please let me know if you know of any way to do this via API or a 3rd party program. Thank you. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Hoping to clear my confusion about Twitter's announcement
Hey Ryan, Raffi, Taylor, Matt, and other Twitter staff, I've been confused about Ryan's post, and some of the follow up comments. Some of the tweets I've seen since have been reassuring that my original interpretation of Ryan's email was inaccurate. I thought you were saying 'no new client apps allowed', and I'm very relieved to hear I was wrong. I wanted to follow up with a few more questions and comments to make sure I understand Twitter's message correctly. Twitter staff, if I have anything wrong here, please correct, or rephrase to be more accurate. Please excuse the length of this and the number of questions at the end of the email. Changing the API rules is changing the contract we have, and as I'm so invested in the ecosystem (my family's livelihood now depends on it), I want to be completely sure I understand what the new contract is that you're introducing. First off, some background. Ryan said that developers are welcome to develop things that Twitter has said developers shouldn't be doing - shouldn't is guidance only, and not a prohibition. Twitter will only interfere with applications if they break the API TOS. Tweets related to this (clicking on the last one and viewing the thread is easiest): - https://twitter.com/joestump/status/47094929796759552 - https://twitter.com/rsarver/status/47095346899320832 - https://twitter.com/timhaines/status/47096379306291203 - https://twitter.com/rsarver/status/47096690288771072 - https://twitter.com/timhaines/status/47097497679708160 - https://twitter.com/rsarver/status/47097681591545856 Furthermore, the most disturbing paragraph for me in Ryan's announcement: If you are an existing developer of client apps, you can continue to serve your user base, but we will be holding you to high standards to ensure you do not violate users’ privacy, that you provide consistency in the user experience, and that you rigorously adhere to all areas of our Terms of Service. This and the preceding paragraph together could be interpreted to mean that developers aren't allowed to build NEW client apps. According to the tweets above, they are allowed, but Twitter is advising developers that they should focus their efforts elsewhere. Likewise, existing applications will be held to high standards. As Ryan clarified in his tweets, these applications won't be interfered with unless they break the API TOS. So all told, the email itself doesn't introduce anything new rulewise; you can do anything you want within the API TOS, but if you break the API TOS you'll potentially have your app revoked. No change here. You won't be applying a subjective 'high standard' or 'high bar' and revoking an app unless it breaks the API TOS. Phew! You are remaining an open API, within the confines of your stated rules. However, the email was accompanied with changes to the API TOS (of course Twitter can make any change to the API TOS at any time - including adding further restrictions in the future). This round of changes included amongst other things, the addition of section I.5, adding restrictions to what client applications may and may not do. For the purposes of this email, I'm considering my own application, Favstar, a client. While it doesn't allow you to tweet at the moment, it will in the coming months, therefore meeting the criteria specified in the API TOS for Favstar to be regarded as a client. My questions: 5a: Your Client must use the Twitter API as the sole source for features that are substantially similar to functionality offered by Twitter. Some examples include trending topics, who to follow, and suggested user lists. *Question re 5a:* Favstar has for a long time offered 'suggested user lists' in the form of it's popular page ( http://favstar.fm/popular-on-twitter-by-tweets-with-50-favorites) Is this feature now in breach of the API TOS? If it is in breach, does this place Favstar in breach until the feature is removed? *Question re 5a:* If I was to add features that surfaced 'popular themes' found in tweets that Favstar collects, would this be considered similar to Trending topics, and put Favstar in breach of the API TOS? *Question re 5a:* Favstar users can buy 'bonus features', and receive a slew of extra features. I've recently started promoting these users on the site. If follow buttons were added to their avatar's in the places of promotion, could this be considered as a 'who to follow' feature that would put Favstar in breach of the API TOS? 5c: Your Client cannot frame or otherwise reproduce significant portions of the Twitter service. You should display Twitter Content from the Twitter API. *Clarify Please re 5c:* This seems like it could be applied pretty generally, and I'm not sure what what constitute a breach of it. Could you provide some examples? 5d: Do not store non-public user profile data or content. *Question re 5d:* Favstar collects and stores tweets that are favorited. Some of those tweets
Re: [twitter-dev] Streaming Unfollow events through Site Streams
David, what you're seeing is what I'm seeing too - and it's what I'd expect to see. On Fri, Jan 21, 2011 at 6:25 AM, David dtran...@gmail.com wrote: Should we be seeing unfollow events for both when our tracked user is the source and the target? I'm only seeing unfollow events where the tracked user is doing the unfollowing. Best, David -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming Unfollow events through Site Streams
Unfollow events have been turned back on.
On Wed, Jan 19, 2011 at 4:10 PM, Yusuke Yamamoto yus...@mac.com wrote:
Thanks for your prompt response!
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
On Jan 19, 2011, at 16:04 , Tim Haines wrote:
Yes, I expect so.
On Wed, Jan 19, 2011 at 2:51 PM, Yusuke Yamamoto yus...@mac.com wrote:
Twitter4J already supports the feature.
http://twitter4j.org/jira/browse/TFJ-529
Will the it come back later?
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
On Jan 19, 2011, at 14:33 , Tim Haines wrote:
Just incase anyone else is playing with these, the unfollow events were
just removed (deploy was rolled back).
On Wed, Jan 19, 2011 at 5:14 AM, Matt Harris
thematthar...@twitter.comwrote:
Hey everyone,
Starting today we will be streaming unfollow events through Site Streams.
These events are being streamed to allow you to keep the social graph of
your users current without the need to query the REST API.
We require that you only surface actions that are organically displayed
on Twitter. This means, for example, executing the unfollow and delete
actions but not publicly displaying them to end users. (Section II.4.B of
the API Terms of Service - http://dev.twitter.com/pages/api_terms ).
The event will be the same format as follow except the event type will
be unfollow. For example:
{
for_user: 123456,
message: {
created_at: Thu Jan 12 21:55:04 + 2011,
target: {
user object for user 123456 - the person being unfollowed
},
event: unfollow,
source: {
user object for user 987654 - the user unfollowing the
target
},
}
}
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources:
http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming Unfollow events through Site Streams
Just incase anyone else is playing with these, the unfollow events were just
removed (deploy was rolled back).
On Wed, Jan 19, 2011 at 5:14 AM, Matt Harris thematthar...@twitter.comwrote:
Hey everyone,
Starting today we will be streaming unfollow events through Site Streams.
These events are being streamed to allow you to keep the social graph of
your users current without the need to query the REST API.
We require that you only surface actions that are organically displayed on
Twitter. This means, for example, executing the unfollow and delete actions
but not publicly displaying them to end users. (Section II.4.B of the API
Terms of Service - http://dev.twitter.com/pages/api_terms ).
The event will be the same format as follow except the event type will be
unfollow. For example:
{
for_user: 123456,
message: {
created_at: Thu Jan 12 21:55:04 + 2011,
target: {
user object for user 123456 - the person being unfollowed
},
event: unfollow,
source: {
user object for user 987654 - the user unfollowing the target
},
}
}
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming Unfollow events through Site Streams
Yes, I expect so.
On Wed, Jan 19, 2011 at 2:51 PM, Yusuke Yamamoto yus...@mac.com wrote:
Twitter4J already supports the feature.
http://twitter4j.org/jira/browse/TFJ-529
Will the it come back later?
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
On Jan 19, 2011, at 14:33 , Tim Haines wrote:
Just incase anyone else is playing with these, the unfollow events were
just removed (deploy was rolled back).
On Wed, Jan 19, 2011 at 5:14 AM, Matt Harris thematthar...@twitter.comwrote:
Hey everyone,
Starting today we will be streaming unfollow events through Site Streams.
These events are being streamed to allow you to keep the social graph of
your users current without the need to query the REST API.
We require that you only surface actions that are organically displayed on
Twitter. This means, for example, executing the unfollow and delete actions
but not publicly displaying them to end users. (Section II.4.B of the API
Terms of Service - http://dev.twitter.com/pages/api_terms ).
The event will be the same format as follow except the event type will
be unfollow. For example:
{
for_user: 123456,
message: {
created_at: Thu Jan 12 21:55:04 + 2011,
target: {
user object for user 123456 - the person being unfollowed
},
event: unfollow,
source: {
user object for user 987654 - the user unfollowing the
target
},
}
}
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Streaming Site API hogs at some stage
The best practices guide (or some doc) explains the streaming connections have heartbeats every 60 seconds or so. You should listen for them. If you don't hear one for 90 seconds, drop the connection and reconnect. On Sun, Jan 2, 2011 at 7:48 PM, Artem Skvira artem.skv...@gmail.com wrote: Hi all, I have a strange problem. After successful oAuth session is established and request to, say, http://betastream.twitter.com/2b/site.json is sent, I start receiving some data. New tweets flow in, notification of deleted messages occasionally show up, the usual. However, after some time the activity ceases. If I look at the TCP connection in the list of OS connections - it is still there - or at least netstat tells me so: sudo netstat -p | grep node tcp0 0 192-168-1-2..:34897 128.242.250.199:www ESTABLISHED 9008/node Do you have any idea why this might be happening? Could that possibly be twitter's fault? Can I somehow tell that connection became 'frozen' so I can re-start it? Thanks! Art -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] API for TOP Tweets
Hey Rajat, Those are tweets that have been faved by @toptweets. You can retrieve favs from that user. You can also get the favs from @toptweets_de and the other languages if you want to. Tim. On Fri, Dec 3, 2010 at 4:06 PM, rajat rajat.triu...@gmail.com wrote: I wonder which API to use to get TOP Tweets as shown on twitter home page without login. Any sugession ? Thank you. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: oAuth still working for everyone.?
Hey Taylor, Thanks for rolling this back. It seems odd that you'd push this out without notice when you know it will break apps. Or was there notice somewhere? Can you deploy your new code to a test endpoint so people (myself included) can test that their new code complies with your new requirements? Cheers, Tim. On Fri, Dec 3, 2010 at 7:59 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We're going to rollback a subset of these changes for now. Before we give this another try, we'll let everyone know the specific pain points and give some time to adjust to them. In the meantime, those who experienced trouble today will want to verify that their libraries are doing the right thing in regard to the bullet points I posted above. Also useful is making sure that you don't send additional headers related to basic auth in an OAuth request, that you're using the proper, versioned api-subdomain end points, etc. Dave: It's pretty crucial that you send an oauth_verifier on the access token step. It's not valid OAuth 1.0a without it. Sorry about the mess folks. We should never have let these bugs persist for so long. Taylor On Thu, Dec 2, 2010 at 2:45 PM, Tom van der Woerdt i...@tvdw.eu wrote: Waiting doesn't help solve the issue. The spec hasn't changed, the API is just a bit more watching for the mistakes which some developers tend to make. I'd recommend diving into the code and fixing the errors, instead of asking the Twitter API team to accept your broken OAuth implementations. :-) Tom On 12/2/10 11:42 PM, LeeS - @semel wrote: I am using this library on all my sites: https://github.com/jmathai/twitter-async, all of which are now broken and fail to let anyone log in. Any way this can be rolled back until all the various oAuth libraries people are using are brought up to date? Lee On Dec 2, 5:35 pm, Dave-twiendsi...@davesumter.com wrote: Thanks Taylor, yip unfortunately I wrote my oauth code about 18 months ago, before most of the libraries were out, so there could be anything wrong. It's probably not 100% spec compliant, which is probably why it broke. I've tracked down the issue to the access_token exchange part of the process. The access token's that I have from before are still working, just can't get new ones. I've noticed I'm not passing oauth_verifier back in the request, which could be causing the issue.. Will let you guys know how I get on... Thanks for the pointers Dave On Dec 2, 9:57 pm, Taylor Singletarytaylorsinglet...@twitter.com wrote: We've corrected a number of long-standing OAuth-related bug fixes -- mainly in areas where we more liberal than we should have been when verifying signatures. Here are a few things to verify: * Verify that you are using your consumer key where the consumer key is supposed to go. Compare this to what you see for you app on dev.twitter.com * Likewise, verify that you are using your consumer secret where it is supposed to go. Compare this to what you see for you app on dev.twitter.com * Laugh at the obviousness and absurdity of a check like that. Cry a little because we already know some people were doing the wrong thing here, especially on end points that didn't require authentication. * Verify that your timestamps are in range * If you're sending a request to a resource that doesn't require authentication but you're including OAuth credentials: - we used to just give you a free pass even if the credentials were incorrect. Hey, it doesn't require auth, so why bother checking? - now we check this. if you pass us an OAuth header or anything that looks like an OAuth-based request, we will check it for validity, even if it's a resource that doesn't require auth. We haven't changed anything about our actual core signature validation code -- what was a valid signature before should be a valid one now. We're just checking the validity in more use cases than we were previously, and checking other validity points we were flexible with previously. Taylor On Thu, Dec 2, 2010 at 1:32 PM, Twitlongerstu...@abovetheinternet.org wrote: I'm seeing a lot of invalid/expired token errors. On Dec 2, 9:21 pm, Dave-twiendsi...@davesumter.com wrote: I noticed I've just started getting 401's for all my oAuth requests. Seems to be happening on more than one site for me.. My application keys and status still look good.. Just wondering if anyone else is having an issue..? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi
Re: [twitter-dev] Identify Suspended Accounts
Hey Dusty, It's currently assigned to @al3x, I'm sure he'll get to it some day. ;-) I have a list of about 28k suspended ids or deleted accounts, out of around 8m I have on file. I'm pretty sure there's maybe 5% or so false positives in there, as accounts become unsuspended but I don't have an automatic process in place checking for that. The 5% guess is based on a manual check about a month ago. I'd be happy to share this list with you if Twitter's not going to provide something themselves. Perhaps we could swap ids.. Cheers, Tim. On Thu, Nov 11, 2010 at 11:12 AM, DustyReagan dustyrea...@gmail.com wrote: If memory serves, Twitter is still returning suspended accounts in the followers API calls. I try to identify and mark these users in my own database so I don't display them to my end user, however this is a difficult and resource intensive task. One in which I have to worry about false positives. Does anyone know of a service that is simply a reliable ever updating giant list of suspended accounts that I can rub against my database to clean it? Alternatively, if the API would stop returning suspended accounts in the follow data, I could skip this data cleanup step. ;) This has been an issue for at least a year and a half now. http://bit.ly/agSBZ7 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Copying or Importing Twitter Lists
And it was given a medium priority in June. I wonder if Twitter can schedule an API week now that Hack week is done. T. On Thu, Nov 4, 2010 at 4:08 PM, Orian Marx (@orian) or...@orianmarx.comwrote: We're actually only a bit more than a month away from the one year mark from when this was first requested, yay! Here it is: http://code.google.com/p/twitter-api/issues/detail?id=1296 This ticket was merged: http://code.google.com/p/twitter-api/issues/detail?id=1657 On Nov 3, 5:39 pm, Quy quyten...@gmail.com wrote: I know I can page but can I get more than 20 members somehow from another call? Maybe Twitter can great another social graph API that returns 500 members in one API call like we can do today for friends/ followers. Quy On Nov 2, 8:20 pm, Edward Hotchkiss edw...@edwardhotchkiss.com wrote: paging. look for obj-next_cursor_str, begin with -1 - it's a string Best, -- Edward H. Hotchkisshttp:// www.edwardhotchkiss.com/http://www.twitter.com/edwardhotchkiss/ -- edward.png 3KViewDownload On Nov 2, 2010, at 9:10 PM, Quy wrote: Is there a better way to grab all the members of list? This API call only returns 20 members at a time so it'll take 25 calls to get a 500 member list: http://dev.twitter.com/doc/get/:user/:list_id/members Quy On Nov 2, 12:29 pm, Ken D. k...@cimas.ch wrote: Don't know of any public tool, but as you suggest it won't be hard to make one. If you were planning to use the list /create_all method, see this thread first:https://groups.google.com/group/twitter-development- talk/browse_threa... On Nov 2, 7:54 pm, Quy quyten...@gmail.com wrote: Is there a tool out there that allows me to copy a Twitter List? For example, I've created a new account and wanted to migrate my Twitter Lists over to this new account or I want to copy an existing public Twitter List and edit it to my liking. I'm thinking of creating a simple tool using the Twitter API but will this hit any rate limiting if this is a public tool? Quy -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] How to count tweets with snowflake?
No. On Thu, Oct 28, 2010 at 8:59 PM, Augusto Santos augu...@gemeos.org wrote: Hi folks, Is there a way to count how many tweets are between two snowflakes id? With the ids from today I can count around 1 billion tweets per day. Thanks, Augusto. -- http://geotweets.gemeos.org/ -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] REST API Rate Limiting
Hey there, Perhaps your IP is blacklisted. Mine was once for a short time. When it was a % of calls were still accepted for some reason. Do you see the same sort of results despite which api call you make? If you do you might want to send a note to a...@twitter.com with your ip address asking them about it. Cheers, Tim. On Thu, Oct 14, 2010 at 4:53 PM, mihai.fa...@olivestudio.net mihai.fa...@olivestudio.net wrote: Hello. I have a problem with getting the user_timeline of an user. The limit is to 150 per hour, yet I get blocked at about the 3rd call. I moved my app to 3 different servers, all are working except the server from where it's supposed to be. Searched for a blacklist or something didn't find anything. So I have to wait about 15 minutes before I can check again and is very hard to develop my app this way. Anybody has an idea why one site would get blocked at 3rd call ? Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Fwd: Twitter Support: update on Favstar50celeb has been suspended.
Hi Developer Advocates, I received this message today after @favstar50celeb has been unsuspended. Can I ask for a little more insight as to why @favstar50celeb was suspended and others like @favstar50 haven't been? Cheers, Tim. -- Forwarded message -- From: JuneClippers notifications-supp...@twitter.zendesk.com Date: Thu, Oct 7, 2010 at 8:49 AM Subject: Twitter Support: update on Favstar50celeb has been suspended.. To: favstar50celeb favstar50ce...@favstar.fm ## Please do not write below this line ## Ticket #1251243: Favstar50celeb has been suspended. :-( This account is used... http://twitter.zendesk.com/tickets/1251243 -- *JuneClippers, Oct 06 04:49 pm (PDT):* Hello, This account was suspended for reply spam. The reply feature is intended to make communication between people on Twitter easier. Twitter monitors the use of the reply feature to make sure that it's used as intended and not used for abuse. Using the reply feature to post messages to a bunch of users' replies tabs is considered an abuse of the feature, which results in account suspension. I have now un-suspended your account. Be sure to review the Twitter Rules, as repeat violations may result in permanent suspension: http://twitter.com/rules Thank you, JuneClippers This email is a service from Twitter Support -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Site Streams - Unfollow Events?
Favstar offers a different UI based on whether you're following someone or not, and different services based on whether you're following @favstar or not. If site streams provided unfollow data it would make it extremely easy to keep the relationship info up to date. OneForty.com was also interested in it.. Tim. On Thu, Sep 30, 2010 at 12:42 PM, John Kalucki j...@twitter.com wrote: Please describe your use case for unfollows on Site Streams... -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Wed, Sep 29, 2010 at 5:09 PM, tsmango tsma...@gmail.com wrote: Ah I wasn't able to find that. It's a shame if true. Thanks for the information. On Sep 29, 6:05 pm, Tim Haines tmhai...@gmail.com wrote: Seen this answered about 1 - 2 weeks ago. Answer is no. On Thu, Sep 30, 2010 at 6:23 AM, tsmango tsma...@gmail.com wrote: I was hoping for some clarification on the social events delivered to a Site Stream. The documentation (http://dev.twitter.com/pages/ site_streams) doesn't specifically mention unfollow events and I'm not seeing them. I am seeing follow events, as expected. User Streams, however, are said to support both follow and unfollow events. Are the plans to add unfollow events to Site Streams? Thanks, in advance! - @tsmango By the way, Home Timelines being delivered through Site Streams is really incredible. I can't wait to get this stuff into my production environment. Thanks, again! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk - @tsmango -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Site Streams - Unfollow Events?
Seen this answered about 1 - 2 weeks ago. Answer is no. On Thu, Sep 30, 2010 at 6:23 AM, tsmango tsma...@gmail.com wrote: I was hoping for some clarification on the social events delivered to a Site Stream. The documentation (http://dev.twitter.com/pages/ site_streams) doesn't specifically mention unfollow events and I'm not seeing them. I am seeing follow events, as expected. User Streams, however, are said to support both follow and unfollow events. Are the plans to add unfollow events to Site Streams? Thanks, in advance! - @tsmango By the way, Home Timelines being delivered through Site Streams is really incredible. I can't wait to get this stuff into my production environment. Thanks, again! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Streaming API skips users
Thanks for following up with this Ginny. Brian has just pushed version 0.7.8 of the gem, which fixes this. Tim. On Tue, Sep 28, 2010 at 5:16 AM, Ginny Hendry ginnyhen...@gmail.com wrote: For anyone else who is having this problem, the fix has been identified but has not yet been published as a new gem version. What happens is that it skips some tweets. The ones it skips are the ones that happen to have a message length in hex that includes a zero character so it will seem pretty random which ones get through and which ones don't. Here's how to fix it: First update the gem and see if it is a version later than 0.7.7. If it is, you should be OK. If it's 0.7.7 or earlier, change one line of code: Look in the gem source code on your system for the yajl-ruby gem and find the file lib/yajl/http_stream.rb. Edit line 151 from break if line.match /0.*?\r\n/ to break if line.match /^0.*?\r\n/ Adding that one character will correct the error. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Status Updates
Hi, I have a bot that does something similar to this. If you do 100 spread out over the course of a day you'll be fine. If you did 100 in the course of an hour, Twitter would (very likely) suspend your account. They have monitoring in place for when certain thresholds are crossed, but they don't disclosed the threshold in the interest of it not being abused. Cheers, Tim. On Tue, Sep 21, 2010 at 8:51 PM, Goran Popovic goranpopo...@gmail.comwrote: They are notified once and that's it ;) Well I got an idea to notify users lets say each 10 minutes ( ie. 100 users found today..and instead of notifying them immediately when they are found ..they would be added in a database..and then notified one by one every few minutes). I think that would be the best solution. On Sep 21, 11:11 am, Tom van der Woerdt i...@tvdw.eu wrote: As far as I know, that's no problem - a lot of services do that. Just don't make it spammy (sending more than 1 tweet per week to one user without first getting his/her permission, etc) and allow users to opt-out (better even would be opt-in but that wouldn't be good for your service, right?). Tom On 9/21/10 8:44 AM, Goran Popovic wrote: Hello! I have a delicate question about status updates. Is it against the Twitter TOS to send tweet every time script finds another candidate? Let me explain more.. Few days ago I've created a website called hottwittz.com. Script finds users who said that they are hot / sexy, and allows users to to vote. Every few minutes script checks for new candidates and then adds them to database.. Until yesterday, when script found new user, new tweet was written to notify the user that he's been added.. Something like @username you have been added Currently there are 50 - 100 users found each day...and i'm not sure if sending lets say 100 similar tweets each day would be considered spam.. So is this considered spam? Is this against rules or is maybe some better way to notify users? This is needed because users have option to write to me and be deleted... First impressions are great and in most cases people are flattered and call their friends to vote for them. This is just an example to describe my problem. Thank You Goran Popovic -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] OAuth limit exceeded and error message reads 'Basic authentication is not supported'?
Hi guys, I haven't fully confirmed this is what's going on, but it appears an account I use for doing only user/show calls, and ONLY via oauth is getting some bad error messages. I think in this case the account has hit it's oauth rate limit, and a few more user/show calls have been attempted. The error message being returned is a 401 and has a response body saying: Basic authentication is not supported when it should perhaps read rate limit exceeded. Cheers, Tim. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] How does one know when a user revoked an app?
Hi, You want to save their ID rather than their screen name, as screen names change often. And as Tom hinted at, there's no callback. You can either call verify_credentials the first time they show up, or wait till you attempt to make another call on their behalf and handle the failure due to incorrect credentials. Tim. On Sun, Sep 5, 2010 at 7:26 PM, StuFF mc m...@stuffmc.com wrote: I couldn't find some callback but I obviously need to know when a user revoked my app. Or maybe I'm doing something wrong. Probably. Here's the idea: When a user accepted (we're speaking OAuth obviously) the app, I save his screen_name. Based on that, I auto log him to twitter the next time he logs on the website. If I don't have a screen_name, I will display a sign in with twitter badge, instead of saying @name is connected, but if a user revoke, I still think I'm connected/accepted. Cheers. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] sample (gardenhose) feed slowdown
This was addressed in a previous email to the list. @jkalucki acknowledged a bug and was going to report on it soon.. On Fri, Jul 16, 2010 at 3:57 PM, Kam kamerondeckerhar...@gmail.com wrote: Hi, we've noticed that we're receiving about 1/4-1/3 the number of tweets that were coming in two days ago. This seems to have begun the night of 14.07 at around 23:54 EST. The connection to the stream was dropped, and when our client automatically reconnected we saw this decrease in the number of messages received. Has anyone experienced a similar problem or know of a reason why this happened? Admins: I can send along our account information in a email if you think it might be a whitelisting problem. Thanks!
Re: [twitter-dev] wating for whitelist confirmation for over a week
Ryan posted to this list, or announced it somewhere recently that they would process them after the world cup finished. He asked people not to write or re-request. Give it another week. Tim. On Mon, Jul 12, 2010 at 3:47 AM, hkimscil hkims...@gmail.com wrote: I have been waiting for being whitelisted over a week period. Should I write Twitter about the confirmation? Is there anyway to check the status of my request? Thanks!
Re: [twitter-dev] Any chance to get more than 20,000 calls per hour?
Question for you, Why is someone with 1m followers going to care about which ones are spammers? Or for that point, why is someone with 10k followers going to care? I'm curious. Apart from knowing 735 of my 10,000 followers are spammers, what's the benefit? I guess that's going to be the secret sauce you reveal on launch. :-) Tim. On Fri, Jul 9, 2010 at 11:42 PM, deadlychaos deadlychaos...@gmail.comwrote: Hi there, We have been building this application since 6 months now. It is anti- spam app which works with very different algorithms and has been very useful for twitter user (we have tested it with 150 calls). But the problem is our apps dig out lot of follower data to let the user know whether his followers are spam or not (it doesn't allow users to unfollow anyone). We all know, Twitter api consumes 1 call for retrieving 100 followers of a particular twitter user. Now 20,000 calls are ok with normal users but some celebrities like Aston Kutcher, Britney Spears and EV have more than 2 million followers which means we cannot track. If they were few it would be ok but day by day as Twitter is growing at amazing rate many users are passing the 2 million milestone. So our app becomes useless for these users and which makes it imperfect. This is totally anti-spam app and I am sure folks at Twitter will love it once it does its work to chop off spam users. I know there have been many such apps but this is something everyone would love. We are done coding our app just wanted to know how can we track users more than 2 million followers? Would whitelisting more than 1 ip and switching them be the right thing to do? Can Twitter allow more than 20,000 calls for 1 ip on special request? Hoping to get answers, Thank you!
[twitter-dev] Why Favstar's IP got blacklisted - monitor error rates
Hey guys, A few people have asked why Favstar got blacklisted, so I thought I'd post this here to answer, and perhaps allow others to prevent this happening to their own service. The reason given by Twitter for Favstar's blacklisting last Thursday was that it was [in theory] ignoring a high error response rate from Twitter, when it should have been backing off. This is undocumented, but Matt Harris has told me that if you see 10 errors per second, you should be responding with incremental back off. Implementing back-off based on rate limits alone is not enough. I'm seeking more details (timeframes, which errors, 10 out of how many requests per second etc) and will post them in this thread when I know more - unless Twitter does themselves. Cheers, Tim.
[twitter-dev] If your IP gets blacklisted
Hey guys, Wanted to share a few details about last nights experience in case anyone else gets hit with it. Hopefully it can save you a few hours troubleshooting if it happens to you. Favstar's IP address was blacklisted by twitter yesterday. When this occurs, they don't inform you of it. Instead, you start seeing percentage of your requests blocked. Not all of them, just some of them. For me it varied between the 50% and 80% range. In the way I do my logging, these appeared as timeouts, so at first I thought the API was suffering overload, and when @mccv told me there was no overload, I fell in to trap of trying to diagnose either what was wrong with my server, or what was wrong with the network in between. What I should have done, is ran a curl in verbose mode (-v). This tells you that your connections are being refused: ~/current: curl -i -u my_account:fuuu! http://api.twitter.com/1/account/rate_limit_status.json -v * About to connect() to api.twitter.com port 80 (#0) * Trying 128.242.240.157... Connection refused * Trying 168.143.161.29... Connection refused * Trying 168.143.162.45... Connection refused * Trying 128.121.146.109... connected snip correct/incorrect response When I tried this from another server, my connections were never refused. When I tried this from the blacklisted server, I would see something like the above. Sometimes I'd get a successful response, sometimes I'd get curl: (52) Empty reply from server which googling for is useless, and sometimes I'd get curl: (7) couldn't connect to host. If you'd like to see Twitter make a reasonable attempt to notify 3rd parties when they are blacklisted, please vote on this issue: http://code.google.com/p/twitter-api/issues/detail?id=1658 Cheers, Tim.
Re: [twitter-dev] Is there small size follow button?
I'd consider using this if there was a small one available too. On Fri, Apr 30, 2010 at 12:12 PM, paloalto sungh...@gmail.com wrote: Follow button in @anywhere api is too large. Is there a way to choose a smaller size?
[twitter-dev] Twitter buying Tweetie
Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
Dewald, I'm surprised that you failed to mention that Twitter can also advertise the heck out of it on Twitter.com and via tweets etc - millions for further development - and very significant marketing resources available too. I disagree with your sentiment though. Twitter's free to build or buy whatever they want to. As a third party developer it's one of the risks you take on when you start building on someone else's platform. If you don't acknowledge that, you're being naive. Sure it's going to suck if they do something to harm Favstar, but I'm aware it's a risk - and I'm going to try and keep innovating to keep Favstar useful for users regardless. Tim. On Sat, Apr 10, 2010 at 2:18 PM, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: 403 on duplicate post - when?
Learnt something here. I knew you couldn't post the same tweet twice in a row. But Twitter is also blocking you from repeating a tweet you posted earlier in the day? So you can't Tweet: A B AThis one won't go through? If this is the case, how far back does it check for duplicates? Guy Kawasaki must hate this. :-) Tim. On Wed, Mar 24, 2010 at 5:28 AM, Mark McBride mmcbr...@twitter.com wrote: Yes, that's a hole in the current logic. I'll work on getting the N-n case handled. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:12 AM, Dewald Pretorius dpr...@gmail.comwrote: Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Problem - Two user with the same screen_name, Example below
Out of curiosity, how many have you found like this? Cheers, Tim. On Wed, Mar 17, 2010 at 8:59 PM, georgios kapero...@gmail.com wrote: Hi I was under the impression that screen_names are unique but I came across two different users having the same screen_name: http://api.twitter.com/1/users/show.xml?user_id=110332760 http://api.twitter.com/1/users/show.xml?user_id=122406923 The screen_name is Y_H_B and when we access the User Show method by screen name (http://api.twitter.com/1/users/show.xml? screen_name=Y_H_B) or go to their twitter page (http://twitter.com/ Y_H_B) then we are looking at the user with id = 110332760 Does anyone know if this is a bug or a known issue? What happens with the ghost user 122406923? Is it a valid user? They don't seem to have a twitter page since the Y_H_B screen_name is used by someone else. Thanks Georgios
Re: [twitter-dev] Over Capacity Message on App Pages
There's a bug in that page. If your app has too many users, it fails to load. Mark (or was it Raffi?) said they were fixing it last year, but I guess it's pretty low on the priority list. Tim. On Thu, Mar 11, 2010 at 9:26 PM, Jesse Stay jesses...@gmail.com wrote: I'm trying to access my app page here: http://twitter.com/oauth_clients/details/61 and I keep getting the over capacity fail whale message. In addition, when I pass my request_token, verifier, etc. to the access_token method ( http://api.twitter.com/oauth/access_token?oauth_consumer_key=...blah..blah..blah) in a normal browser window it prompts me for a plain auth username and password - is this normal behavior when testing in the browser? Thanks, Jesse
Re: [twitter-dev] Over Capacity Message on App Pages
Email them offlist and I'm sure they'll look it up for you. Sent from my iPhone On 11/03/2010, at 9:51 PM, Jesse Stay jesses...@gmail.com wrote: So how do I verify my consumer key is correct? I would imagine that page would be pretty important - how can you edit your app without it? I'm also curious about why I'm being prompted for basic auth on http://api.twitter.com/oauth/access_token Thanks, Jesse On Thu, Mar 11, 2010 at 1:37 AM, Tim Haines tmhai...@gmail.com wrote: There's a bug in that page. If your app has too many users, it fails to load. Mark (or was it Raffi?) said they were fixing it last year, but I guess it's pretty low on the priority list. Tim. On Thu, Mar 11, 2010 at 9:26 PM, Jesse Stay jesses...@gmail.com wrote: I'm trying to access my app page here: http://twitter.com/oauth_clients/details/61 and I keep getting the over capacity fail whale message. In addition, when I pass my request_token, verifier, etc. to the access_token method (http://api.twitter.com/oauth/access_token?oauth_consumer_key=...blah..blah..blah ) in a normal browser window it prompts me for a plain auth username and password - is this normal behavior when testing in the browser? Thanks, Jesse
Re: [twitter-dev] bulk user show API
Raffi, does the limit mean that if you call this API for 20 users at a time, you can only use it 50 times per hour? Cheers, Tim. On 12/03/2010, at 4:48 AM, Raffi Krikorian ra...@twitter.com wrote: hi all. we launched an endpoint yesterday that allows you to fetch 20 users by user_id or by screen_name at a time -- we call this our bulk user show API. for example, to retrieve user objects for user IDs 12863272 , 3191321, 9160152, 8285392 and simultaneously screen names of rsarver and wilhelmbierbaum, put together the following authenticated request http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,8285392screen_name=rsarver,wilhelmbierbaum and you will receive an XML array of those six user objects. you can find more documentation at http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup . thanks! -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] bulk user show API
Raffi, Is there a limit on how many user/show requests can be done apart from the standard 20k rate limit? I'm thinking the limit of 1000 user objects per hour is frustratingly low too. It's making me hesitate in my decision to use it. Tim. On Fri, Mar 12, 2010 at 8:34 AM, Raffi Krikorian ra...@twitter.com wrote: i wouldn't necessarily and harshly say useless :P it still prevents you from having to make 1000 user/show requests (which you can't do right now). On Thu, Mar 11, 2010 at 10:59 AM, Michael Steuer mste...@gmail.comwrote: Oh wow, I missed that. I understood it was rate limited at 1000 calls/hour (which would come out to 20k user objects) Having a limit of only 1,000 user objects an hour, renders this new API pretty useless! Come on! I thought the idea was to give developers who now do 10's of thousands of user/show calls a more efficient alternative?!?! On Mar 11, 2010, at 10:11 AM, Abraham Williams 4bra...@gmail.com wrote: My understanding is that it is 50 users/lookup API calls x 20 user objects per call = 1000 user objects. Not 1000 users/lookup calls of 20 user objects. Abraham On Thu, Mar 11, 2010 at 10:06, Michael Steuer mste...@gmail.com mste...@gmail.com wrote: Erm, doesn’t 20,000 x users/show equate to 1,000 x users/lookup ? Or are you whitelisted for more than 20,000 API calls an hour? On 3/11/10 9:53 AM, Abraham Williams http://4bra...@gmail.com 4bra...@gmail.com wrote: So for something like Intersect [1] where I have to do sometimes tens of thousands of profile lookups per hour I should stick with users/show? Or can I get an account whitelisted for more lookups per hour? Abraham On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian http://ra...@twitter.com ra...@twitter.com wrote: hi all. we launched an endpoint yesterday that allows you to fetch 20 users by user_id or by screen_name at a time -- we call this our bulk user show API. for example, to retrieve user objects for user IDs 12863272, 3191321, 9160152, 8285392 and simultaneously screen names of rsarver and wilhelmbierbaum, put together the following authenticated request http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,8285392screen_name=rsarver,wilhelmbierbaum http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,8285392screen_name=rsarver,wilhelmbierbaum and you will receive an XML array of those six user objects. you can find more documentation at http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup. thanks! -- Abraham Williams | Community Advocate | http://abrah.amhttp://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Incorrect favorited value for home_timeline
Hi, There's been an issue open for this since December and it's assigned to Raffi. http://code.google.com/p/twitter-api/issues/detail?id=1270 Tim. On Thu, Mar 11, 2010 at 3:35 PM, _ado adri...@tijsseling.com wrote: I queried home_timeline and got an incorrect favorited status for a retweet. The tweet in question was not favorited at all by me. The call to home_timeline was authenticated, so according to the api docs on favorited (boolean indicating if a status has been marked as a favorite by the authenticating user), the value for favorited in this case should be 'false'. I'm I understanding it wrong or is the data incorrect? status created_atThu Mar 11 01:16:30 + 2010/created_at id10298971327/id textRT @MrBigFists: Oh, I'm not going to cry over spilled milk. But make no mistake, if you spill my steamed milk with two shots of espresso .../text sourcelt;a href=quot;http://favstar.fmquot; rel=quot;nofollowquot;gt;Favstar.FMlt;/agt;/source truncatedtrue/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/in_reply_to_user_id favoritedtrue/favorited in_reply_to_screen_name/in_reply_to_screen_name retweeted_status created_atWed Mar 10 14:54:22 + 2010/created_at id10274344282/id textOh, I'm not going to cry over spilled milk. But make no mistake, if you spill my steamed milk with two shots of espresso... I will cut you./text sourceweb/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/in_reply_to_user_id favoritedtrue/favorited in_reply_to_screen_name/in_reply_to_screen_name user id47569242/id nameJonathan/name screen_nameMrBigFists/screen_name ... snip ...
Re: [twitter-dev] Re: Twitter API and ETags - No 304s?
Hi Phil, Thanks for sending through the examples. I must have been setting the header incorrectly - missing the quotes or something. It does indeed work for favorites too, whether authenticated or not.. Tim. On Wed, Feb 24, 2010 at 2:15 PM, philoye phil...@gmail.com wrote: On Feb 22, 1:31 pm, Tim Haines tmhai...@gmail.com wrote: The Twitter API returns ETags, that seem to change when the content changes and otherwise not. It doesn't seem to return 304's when the same ETag is sent back to it though. Has anyone seen it send 304s? The API always seem to return no-cache and past expiry headers, it *does* send 304's when you pass the etag in a If-None-Match header: $ curl --head http://twitter.com/users/show.xml?screen_name=philoye HTTP/1.1 200 OK Date: Wed, 24 Feb 2010 01:13:10 GMT Server: hi X-RateLimit-Limit: 150 X-Transaction: 1266973990-97869-341 Status: 200 OK ETag: 3022db84cebe898b561a397c20063f5e Last-Modified: Wed, 24 Feb 2010 01:13:10 GMT X-RateLimit-Remaining: 136 X-Runtime: 0.02109 Content-Type: application/xml; charset=utf-8 Pragma: no-cache Content-Length: 2057 X-RateLimit-Class: api Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Expires: Tue, 31 Mar 1981 05:00:00 GMT X-Revision: DEV X-RateLimit-Reset: 1266976693 Set-Cookie: _twitter_sess=BAh7CDoRdHJhbnNfcHJvbXB0MDoHaWQiJTA0MWYzMTQyNGZjMjU5MTJlYWQz %250AOWU1MzhhMmYxZTkzIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFz %250AaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- ba31f1ea9e0800e1b4c3d564484c8fdf6885183d; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close $ curl --head --header 'If-None-Match: 3022db84cebe898b561a397c20063f5e' http://twitter.com/users/show.xml?screen_name=philoye HTTP/1.1 304 Not Modified Date: Wed, 24 Feb 2010 01:13:41 GMT Server: hi Connection: close ETag: 3022db84cebe898b561a397c20063f5e Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Vary: Accept-Encoding Set-Cookie: _twitter_sess=BAh7CDoHaWQiJTRiYTlkN2RlODVhN2NlNmMzMWM3MWY4Y2FhNGUwZjc4Igpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsAOhF0cmFuc19wcm9tcHQw-- fce6e5410dc71d9720ac35c5470bc7220e8b4ceb; domain=.twitter.com; path=/ The key is to send the ETag in a If-None-Match header, not an ETag header. I still don't understand why the Cache-Control and Expires headers are set this way though. Cheers, p.
[twitter-dev] Twitter API and ETags - No 304s?
Hey guys, The Twitter API returns ETags, that seem to change when the content changes and otherwise not. It doesn't seem to return 304's when the same ETag is sent back to it though. Has anyone seen it send 304s? I'm making calls against the method to retrieve favorited tweets. Tim.
Re: [twitter-dev] complete Retweet functionality in thirdparty apps
Last time I checked you couldn't see who RT'ed beyond the first 20.. And everything else is time-expensive.. Tim. On Fri, Feb 19, 2010 at 9:49 AM, Abraham Williams 4bra...@gmail.com wrote: What retweet functionality is it not posible to replicate using the API? I can not think of any. It might take a number of API calls to collect all the data but it is all there. Abraham On Thu, Feb 18, 2010 at 06:17, srikanth reddy srikanth.yara...@gmail.comwrote: Replicating all the retweet functionality is currently not possible (Twitter obviously doesn't use the same api) Rate limit is okay with me (getting 350 with api.twitter.com) On Thu, Feb 18, 2010 at 4:13 AM, Abraham Williams 4bra...@gmail.comwrote: Seems like you should be able to replicate all of the retweet functionality on twitter.com but it will probably take a lot of API calls. Abraham On Tue, Feb 16, 2010 at 12:29, srikanth reddy srikanth.yara...@gmail.com wrote: Hi Has anybody implemented complete Retweet functionality (retweets by others, by you, your retweets) in their app. There are couple of issues with retweets api see here http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fb44e38e034cb9b7?pli=1 I would like to know if any one has implemented the complete Retweet functionality with some work around. Thanks Srikanth -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] complete Retweet functionality in thirdparty apps
Try it. On Fri, Feb 19, 2010 at 10:06 AM, Abraham Williams 4bra...@gmail.comwrote: Docs say 100 and I don't see any open issues specifying otherwise. Abraham On Thu, Feb 18, 2010 at 13:01, Tim Haines tmhai...@gmail.com wrote: Last time I checked you couldn't see who RT'ed beyond the first 20.. And everything else is time-expensive.. Tim. On Fri, Feb 19, 2010 at 9:49 AM, Abraham Williams 4bra...@gmail.comwrote: What retweet functionality is it not posible to replicate using the API? I can not think of any. It might take a number of API calls to collect all the data but it is all there. Abraham On Thu, Feb 18, 2010 at 06:17, srikanth reddy srikanth.yara...@gmail.com wrote: Replicating all the retweet functionality is currently not possible (Twitter obviously doesn't use the same api) Rate limit is okay with me (getting 350 with api.twitter.com) On Thu, Feb 18, 2010 at 4:13 AM, Abraham Williams 4bra...@gmail.comwrote: Seems like you should be able to replicate all of the retweet functionality on twitter.com but it will probably take a lot of API calls. Abraham On Tue, Feb 16, 2010 at 12:29, srikanth reddy srikanth.yara...@gmail.com wrote: Hi Has anybody implemented complete Retweet functionality (retweets by others, by you, your retweets) in their app. There are couple of issues with retweets api see here http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fb44e38e034cb9b7?pli=1 I would like to know if any one has implemented the complete Retweet functionality with some work around. Thanks Srikanth -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] complete Retweet functionality in thirdparty apps
On Fri, Feb 19, 2010 at 10:24 AM, Abraham Williams 4bra...@gmail.comwrote: File a bug report. I've given up on bug reports as a way of getting bugs fixed. Maybe when twitter gets more support staff on board the bug reports might become useful again.
Re: [twitter-dev] favorites paging limit?
Hey TJ, This just came up in another thread. The limits are talked about here: http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits I'd expect roughly 3200 to be available as per other timelines.. Tim. On Thu, Feb 18, 2010 at 12:28 PM, TJ Luoma luo...@luomat.net wrote: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-favorites doesn't mention any limits to the page parameter. Through trial and error I figured out that curl --location --referer ;auto -D - -s --netrc 'http://twitter.com/favorites.xml?page=175' was too much but curl --location --referer ;auto -D - -s --netrc 'http://twitter.com/favorites.xml?page=174' seems to work. At 20 per page, that works out to 3,480. TjL
Re: [twitter-dev] huge Fail Whale quotient suddenly
Hey Raffi, It would probably be helpful for a lot of us if the status blog (or another secondary indicator) was more accurate in terms of being a problem/no problem indicator. Even if it didn't have an indication as to cause or expected time to resolve, just a little flag that said 'we acknowledge an increased error rate right now' it would be helpful. Tim. On Wed, Feb 17, 2010 at 7:27 PM, Raffi Krikorian ra...@twitter.com wrote: yeah - by the time we got ready to put the post up, on this particular issue, we had solved the problem. On Tue, Feb 16, 2010 at 6:30 PM, Abraham Williams 4bra...@gmail.comwrote: Never did get a post on status.twitter.com on this. Abraham On Mon, Feb 15, 2010 at 15:24, Raffi Krikorian ra...@twitter.com wrote: we're aware of the issue and are working on it - i expect a post to status.twitter.com in a bit. On Mon, Feb 15, 2010 at 3:17 PM, Yu-Shan Fung ambivale...@gmail.comwrote: We're seeing the same thing, especially with OAuth. Nothing's posted on status.twitter.com yet. Any updates? Thanks! Yu-Shan On Mon, Feb 15, 2010 at 2:50 PM, Cameron Kaiser spec...@floodgap.comwrote: Over the last few minutes, I'm seeing a huge jump in Fail Whales. What happened? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Everyone is entitled to my opinion. -- James Carpenter - -- “When nothing seems to help, I go look at a stonecutter hammering away at his rock perhaps a hundred times without as much as a crack showing in it. Yet at the hundred and first blow it will split in two, and I know it was not that blow that did it, but all that had gone before.” — Jacob Riis -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] verify_credentials returning the wrong user id
Hey Scott, Just guessing here, but I think you may be looking at the (most recent) status id that is returned, rather than the user id? Tim. On Mon, Feb 15, 2010 at 5:08 PM, Scott Aikin haw...@gmail.com wrote: I've encountered a strange problem where sometimes verify_credentials gives me the wrong user id. In these cases the number is usually very large and is different each time. All the other user details are correct. How can this be?
Re: [twitter-dev] Re: Application Suspended
Dewald, Try looking in the google cache. I'm surprised it was allowed to live for as long as it did. http://74.125.155.132/search?q=cache:o2N2KuZsuYgJ:www.gotwitr.com/+gotwitrcd=1hl=enct=clnk It was basically a spam enabler. T. On Mon, Feb 15, 2010 at 11:27 AM, Dewald Pretorius dpr...@gmail.com wrote: I cannot comment on what Jim's site did or didn't do, since he has pulled all descriptive information from the site. Nevertheless, it is highly disturbing that applications are being suspended without any notice. This particular site seems to have had a contact form, plus it was OAuth, so the owner could have been contacted via the email address on file for the Twitter user that owns the application. Yes, some apps do stuff that warrant suspension. But, to just suspend an app with no communication is bad. If Twitter don't want to give some sites the opportunity to correct transgressive behavior (I know they do communicate in some cases), at the very least send an email to the owner with, Your service has been suspended because..., and give a clear path and instructions on how the situation can be remedied as soon as possible. I'm going to say it again, Twitter: Your rules are vague and nebulous. Not everyone understands and interprets the rules the way you do internally. You must realize that actions like these sometimes shout so loud that we cannot hear when you say, We care about our developers. Rightly or wrongly, here's a developer who has lost face with his user base, and has been in the dark for 4 days now. The message it sends to us, the other developers, is a very bad message. If you properly communicated with Jim, he probably wouldn't even have posted about it here. On Feb 14, 3:56 pm, Jim Fulford j...@fulford.me wrote: Hello, I need some help. 4 days ago I started getting emails from my users that they could not login to our site using the Oauth service. I checked my site and it said my application had been suspended. I did not get any email from Twitter, they just deactivated my application so nothing works. I have sent in two support tickets, but gotten no response. 2 days ago, I took my site downwww.gotwitr.com so that I would stop getting support email from my users. I have had this site up for 5 months, and I have over 5000 users have used the service. I am so glad that I have never charged for the service, this would be a nightmare. If they would let me know what our site, or one of our users did to get banned, we would be glad to fix it. We have tried to make our site as Twitter API friendly as possible. We are 100% Oauth, we have never saved or requested any users passwords. We only let our users hit the Twitter API 1000 times in a 24 hour period We have all of our tools that follow or unfollow use individual user verification, (no mass follow or unfollow) An email with the issue would have been great. Not getting a response in the last 4 days that my site has been down is really not acceptable! Thanks
[twitter-dev] Limit on number of concurrent requests
Hi there, Is there a limit on the number of requests that will be processed per IP concurrently? I've been playing about and it seems to make 100 requests, the responses come back in roughly the same total time whether I use 10 or 100 threads. Still digging to see if it's something at my end holding things back. Tim.
[twitter-dev] Re: Limit on number of concurrent requests
Cancel that. 100 threads gives a much better result than 10 threads on my production servers in the states (Ubuntu). I wonder why it makes no/little difference on OSX Leopard from Australia.. Tim. On Thu, Feb 4, 2010 at 3:45 PM, Tim Haines tmhai...@gmail.com wrote: Hi there, Is there a limit on the number of requests that will be processed per IP concurrently? I've been playing about and it seems to make 100 requests, the responses come back in roughly the same total time whether I use 10 or 100 threads. Still digging to see if it's something at my end holding things back. Tim.
Re: [twitter-dev] favourites_count on user profile is not updated !
Ono, I think it's been this way for 8+ months? Tim. On Thu, Jan 21, 2010 at 1:14 AM, ono_matope matope@gmail.com wrote: Hi, Twitter team! I'm @ono_matope I made a fav-crawler that fetches favourite-feeds only when favourite_count of the user profile information (whitch is retrieved by or list members API) get increased. This mechanism will lat me crawl your data in less resouces. But I've noticed that the user's favourites_count attribute that retrieved by user/show or some other API does NOT to be updated even though he created a new favourite. Through some experiments, I found out following specifics. 1. When user created new favorites, his user info does NOT update. 2. That will be updated only when he tweets, follows someone or do some other activities but creates favourites. ...My new crawler development has been stuck : ( I would like to request that favourite_count attribute to be updated without any other activities, please. Thank you. @ono_matope
Re: [twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010
Yet, those 775 accounts have the potential ability to reach up to 775,000+ (+, considering the number of retweets they each get) of Twitter's user base. When they're dissatisfied, people hear. IMO those are the ones Twitter should be going out of their way to satisfy. Add to that the fact that many of those are the ones willing to pay the biggest bucks when/if Twitter implements a business account, they could also be a contributing factor to Twitter's revenue model in the future. It makes total sense for Twitter to support those ~775 accounts. If they're ignored, they'll take their followers with them. Jesse Getting way off topic, but I think you're wrong here. They won't be taking their followers anywhere. Commonly the majority of the large number of followers aren't engaged followers. http://dashes.com/anil/2010/01/nobody-has-a-million-twitter-followers.html Anil's blog post matches my own experiences with traffic fluctuations after receiving tweets. Tim.
Re: [twitter-dev] Re: Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
On Thu, Jan 14, 2010 at 10:52 AM, ryan alford ryanalford...@gmail.comwrote: I've been using OAuth for more than 3 months now, about 8 hours a day during the week while at work, using my own library and my own twitter client. I've never had an issue with stability. Now the desktop implementation is crappy(been posted about 50 billion times), but other than that, I've never run into issues with OAuth. Now I don't use search or streaming, though I don't even know if those use OAuth. Is there a specific stability issue? Ryan I've found it just as stable as the rest of the API. It's not perfect, but is generally pretty good. My main concern is that I'd like the mobile pages to be formatted for mobile devices. Oh - and the ability to delegate between apps. Sooo looking forward to that. Tim.
Re: [twitter-dev] Support from a...@twitter.com sucks!!!
Twitter's been trying to hire new support staff for quite a while now. You'll probably remember Doug's email. From what I can determine, they've had no luck finding people, because it's still the engineers answering questions in here. They're stretched. Saying something sucks and following it with !!! probably doesn't help the moral of the guys who are helping - often out of hours from what I can see. I feel the frustration too, but there's definitely more constructive things you can do about it. Why not send out a tweet, or message to your other networks saying Twitter's looking for support staff? Tim. On Tue, Jan 12, 2010 at 5:50 PM, Dewald Pretorius dpr...@gmail.com wrote: I sent very specific questions to a...@twitter.com, not knowing that it is now being automatically fed into the Zendesk Twitter helpdesk system. The answer I received back consisted of: - I suggest that you check out the API wiki for this information: http://apiwiki.twitter.com/ . We also have a very active and helpful community at http://groups.google.com/group/twitter-development-talk , where our API team interacts with developers on a regular basis. You may want to join the group to participate in conversations about topics like these. Hope that helps, Support -- Well, F-ING D-UH!! Thanks for nothing.
Re: [twitter-dev] Missing favorites... please help!
Mark, Are you guys fixing people 1 by 1 as they are reported? Tim. On Wed, Jan 6, 2010 at 12:20 PM, Mark McBride mmcbr...@twitter.com wrote: Orian, is this still an issue? If so let me know... ---Mark http://twitter.com/mccv On Tue, Jan 5, 2010 at 3:18 PM, Abraham Williams 4bra...@gmail.com wrote: I just check out her favorites in my browser and loaded up the last 80 no problem. It was probably just a glitch with Twitter Abraham On Tue, Jan 5, 2010 at 16:35, Orian Marx (@orian) or...@orianmarx.com wrote: I'm trying to help @whitneyhess figure out what happened to her favorites. Until yesterday she had several hundred favorited tweets, many of which were critical to her ongoing business as a freelancer. Currently Twitter is returning 20. If anyone has any insight into what is going on it would be *greatly* appreciated. -- Abraham Williams | #doit | http://hashtagdoit.com Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
Re: [twitter-dev] Missing favorites... please help!
Mark, I've told users a week or so ago via @favstar that you're fixing this - I thought you'd be resolving the issue for everyone. Can I give people some advice on how to report it if it's happening to them? What's the way you'd prefer to hear from them? Tim. On Wed, Jan 6, 2010 at 2:06 PM, Mark McBride mmcbr...@twitter.com wrote: Yes, although we're keeping an eye on whether or not this is a large trend. ---Mark http://twitter.com/mccv On Tue, Jan 5, 2010 at 5:02 PM, Tim Haines tmhai...@gmail.com wrote: Mark, Are you guys fixing people 1 by 1 as they are reported? Tim. On Wed, Jan 6, 2010 at 12:20 PM, Mark McBride mmcbr...@twitter.com wrote: Orian, is this still an issue? If so let me know... ---Mark http://twitter.com/mccv On Tue, Jan 5, 2010 at 3:18 PM, Abraham Williams 4bra...@gmail.com wrote: I just check out her favorites in my browser and loaded up the last 80 no problem. It was probably just a glitch with Twitter Abraham On Tue, Jan 5, 2010 at 16:35, Orian Marx (@orian) or...@orianmarx.com wrote: I'm trying to help @whitneyhess figure out what happened to her favorites. Until yesterday she had several hundred favorited tweets, many of which were critical to her ongoing business as a freelancer. Currently Twitter is returning 20. If anyone has any insight into what is going on it would be *greatly* appreciated. -- Abraham Williams | #doit | http://hashtagdoit.com Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Docs wrong for retweets method? Count seems to be ignored if 20
Hey guys, I'm trying: curl -u timhaines:123#notreally http://twitter.com/statuses/retweets/5635825799.json?count=100 and only the first 20 RTs are being returned. Same with the xml method. The docs ( http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses-retweets) say you should be able to fetch up to the first 100. Am I doing it wrong? Or Doc/API bug? Tim.
Re: [twitter-dev] Platform announcements from LeWeb
Hey Ryan, Thanks for writing this up. Fantastic to have it summarized. Congratulations to the whole team on what you've managed to achieved so far - truly mind blowing. Looking forward to seeing what you bring in 2010. My 2c on what you announced here: 1) It's become frustrating to have the code.google.com issue tracker service only API issues. There's no good way to track and get notification on issues when they're not API related. (And if they're lodged in the API tracker, they get closed for not being API related). I really hope the new dev site you're putting together allows for both API and core twitter bugs to be reported, and it emails updates when someone from twitter acknowledges/updates/resolves. 2) Chirp - I really hope that you'll make videos of the content available on the web. Cheers, Tim. On Mon, Dec 28, 2009 at 6:24 PM, Ryan Sarver rsar...@twitter.com wrote: Hey all, Now that the dust has settled a bit and we are in the midst of the holidays I wanted to email everyone and provide some more details on the announcements we made a few weeks ago at LeWeb. *50,000 apps* We are continually amazed by all the incredible work the ecosystem does as a whole and we proud that developers have created over 50,000 applications that allow people to experience Twitter in so many different ways. We are really looking forward to what 2010 has in store as we put more emphasis on supporting the ecosystem better and maturing as a platform. We are humbled by and appreciative all the hard work you do. Please continue to give us feedback -- both good and bad -- on how we can support you better in your efforts to build awesome apps. *Auth announcements* With the recent launches of Retweet, Lists and Geotagging we have seen applications struggle to provide the experience they want for their users within the 150 req/hr limit. We are excited to open the skies up a bit and provide some more room for developers to work within. Starting in a few weeks all OAuth requests to api.twitter.com/1/ will be able to take advantage of a 10x rate limit increase. Basic Whitelisting still exists and is unchanged. We look forward to what this means in terms of the increased richness around the user experience in Twitter apps. *Developer Site* From the beginning we have used a disparate set of tools to help support the community -- from the apiwiki, to code.google.com for issues to this mailing group. It was a great way to get started quickly with fairly robust tools, but we need a place for developers to start from and help them find the right answers to their questions and help them solve their problems. We have announced a new Developer Site that begins to consolidate these communications channels and tools into a single place while adding some new, exciting tools to help developers. There will be new reference documentation, search, API console, API status dashboard (external monitoring service) and clearer documentation of policies. We are investing heavily in this area and will continue to improve the tools and content for the ecosystem to make sure that you have everything you need to get started and for continued support. We are really interested in getting your feedback on what will create a great site, so please let us know your wishlist of things that will help you be a more informed and more efficient developer. *Chirp - Twitter Developer Conference* Personally one of the most exciting announcements is that we will be throwing the first official Twitter Developer Conference which we are calling Chirp. It will be a two day event focused on equipping developers with all the tools they need to go forth and build great things. Day One will be filled with speakers from Twitter and the ecosystem talking about a broad range of topics like our roadmap, the Streaming API, how to develop desktop applications, sentiment analysis, user research and more. At the end of Day One we will kick off a 24-hour hack event with lots of great announcements and surprises already lined up. We'll also be filling Day Two with some workshops on specific topics for developers who want to dive deep in certain areas. There are lots of great surprises in store for the event and we hope to see lots of you there. *Firehose for everyone* Finally, the announcement that has garnered the most coverage and excitement. As I stated in the session at LeWeb we are committed to providing a framework for any company big or small, rich or poor to do a deal with us to get access to the Firehose in the same way we did deals with Google and Microsoft. We want everyone to have the opportunity -- terms will vary based on a number of variables but we want a two-person startup in a garage to have the same opportunity to build great things with the full feed that someone with a billion dollar market cap does. There are still a lot of details to be fleshed out and communicated, but this a top
Re: [twitter-dev] What is the expected behavoir of Retweeting a retweet
I'll give you an unofficial yes. This is exactly the way I understand it will work. If you star any of the RT's it's update1 that gets the stars too. On Fri, Dec 4, 2009 at 10:58 PM, Hwee-Boon Yar hweeb...@gmail.com wrote: I did an experiment. user1 tweets update1 user2 retweets update1 as update2 (a RT, with update1 embedded) user3 retweets update2, the embedded update is update1 instead of update2. I can't find documentation on this. Is this the expected behavoir? -- Hwee-Boon
Re: [twitter-dev] Lists API call not working?
They've turned off lists on twitter.com at the moment. I'd expect this would cause the API to stop working too.. On Tue, Dec 1, 2009 at 10:36 AM, LeeS - @semel lse...@gmail.com wrote: I'm trying to use this call from the documentation, which previously worked - now it doesn't: http://api.twitter.com/1/twitterapidocs/lists.xml I get redirected to http://api.twitter.com/lists/not_yet This seems to affect other API calls I've tried as well. Lee
[twitter-dev] Bad bug when editing lists on twitter.com
Hey Twitter guys, I had 2 lists. Both named My Favstar.fm List. One with slug 'my-favstar-fm-list, and the other with slug my-favstar-fm-list-8. (I'd created a few and deleted some with the same name). The list without the -8 suffix is the one I've been using in anger, and has 35 members. I've just been in to twitter.com to edit the my-favstar-fm-list list, adding a description My favourite tweeters from http:/favstar.fm. After the update, the slug was changed to my-favstar-fm-list-8. So I now have 2 lists with the slug my-favstar-fm-list. (IDs: 126147, 968546) Eeep. Tim.
[twitter-dev] Retweets - where are they placed on timeline
Hi guys, I'm wondering if anyone can clarify. The services I run often shown tweets that are several months old, and offer the RT button next to them. If someone clicks to RT the tweet, how does the tweet get presented to people that aren't following the original tweeter? Is it placed at the top of the timeline appearing as a new tweet, or is it placed at the time the original tweet was tweeted? i.e. months ago, so likely to never be seen? If it would be placed months ago, it makes RT pointless for older tweets, in which case I'll switch to 'classic mode' RT's. Tim.
[twitter-dev] Re: Bad ssl certs on some servers for api.twitter.com/1 ?
Hi Marcel, Thanks for following up on this. The bad cert responses I got were inconsistent. Often it would work fine, so what you've outlined here is one theory that would explain it. I think I'll switch back to twitter.com for this app, and look at using api.twitter.com in a future update. Tim. On Wed, Nov 18, 2009 at 7:46 AM, Marcel Molina mar...@twitter.com wrote: Ops has been trying to track down this problem for a while. They confirmed that all servers have the correct cert. The current hypothesis is that there are some rogue servers that are being load balanced to that we don't expect to be accepting api.twitter.com traffic that do not have the correct cert. Sorry it's not fixed yet. We hope we can figure it out soon as it's a blocker for the transition of api traffic from twitter.com to api.twitter.com. On Tue, Nov 17, 2009 at 7:41 AM, Mageuzi mage...@gmail.com wrote: I've been having this same issue when connecting to https://api.twitter.com. I would have thought that if it is a problem with my code, I would always get this error. However, it is intermittent. Most times it works, but a few times an hour I will get the error. Also, I never have this problem with https://twitter.com. On Nov 15, 6:46 pm, John Adams j...@twitter.com wrote: On Nov 15, 2009, at 1:16 PM, Tim Haines wrote: Hi there, I'm doing some dev work and I'm getting occasional ssl errors when making calls against api.twitter.com/1. The most recent was posting to favorites/create. Is it possible some of the servers have bad certificates? Or is it likely I'm doing something very wrong? All of our servers have the same certificates; We have had some people report a similar issue before and we verified all of the certificates at that time. I do know of people having validation issues when they don't have current versions of OpenSSL, a current Root CA bundle, or their code has problems processing chained SSL certificates. Which program are you using to make requests against api.twitter.com? curl? Firefox? Twitter's SSL certs are issued by RapidSSL/Equifax. Make sure you have the proper root CA certs installed. If you're using OpenSSL libraries directly, remember that OpenSSL ships without any Root CA certs installed. Curl users will have similar problems as well -- you'll want to run mk- ca-bundle to get the proper ca-bundle installed. The TTYtter developers have a script that pulls the current CA bundle from Mozilla, here: http://www.floodgap.com/software/ttytter/mk-ca-bundle.txt -john -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
Re: [twitter-dev] Re: Retweets - where are they placed on timeline
Hey Dewald, What if your twitter client had a feature of showing you tweets in your timeline that had been retweeted by 10 or more people? That's possible now. It was very very difficult before. Marcel, thanks for your reply earlier. I noticed something yesterday that indicated this 'probably' wasn't happening. (RT by NZKoz, which he's since deleted). I'll do more testing today, and likely find what was wrong with my testing yesterday. :-) Tim. On Wed, Nov 18, 2009 at 9:37 AM, Dewald Pretorius dpr...@gmail.com wrote: Marcel, This collapsing behavior is far from ideal and will cause people with busy timelines to completely miss retweets. Nobody is online 24x7, and if only the first retweet of an update is shown in a user's timeline, they will miss completely it if the first retweet happened several hours before they login and check their timeline. In other words, someone can retweet the same update while they are online and they still won't see it. From a Twitter-internal technical standpoint, new retweets are ideal because it eliminates a lot of duplication and accompanying processing and storage requirements. From a user's perspective, it is far from ideal. With old-style retweets, if I saw ten retweets of the same thing, I knew to check it out because obviously a lot of people felt it was something worth sharing with their followers. With the new retweets, I'm going to miss that completely. Even if I notice the first retweet, the retweeted by section may show only one or two people, and I won't know that the update was retweeted by twenty more people after I happened to look at it. In my irrelevant opinion, the new retweet feature is trying to fix something that was not broken. Dewald On Nov 17, 3:58 pm, Marcel Molina mar...@twitter.com wrote: Should appear as a new tweet with the time of the retweet, not the original tweet creation time. That assumes though that no one else has retweeted it to you yet. If someone else has then this additional retweet won't appear in your timelines except for the statuses/retweets/id resource that lists up to 100 retweets for a given tweet. Duplicates are collapsed out of the other timelines. On Tue, Nov 17, 2009 at 11:46 AM, Tim Haines tmhai...@gmail.com wrote: Hi guys, I'm wondering if anyone can clarify. The services I run often shown tweets that are several months old, and offer the RT button next to them. If someone clicks to RT the tweet, how does the tweet get presented to people that aren't following the original tweeter? Is it placed at the top of the timeline appearing as a new tweet, or is it placed at the time the original tweet was tweeted? i.e. months ago, so likely to never be seen? If it would be placed months ago, it makes RT pointless for older tweets, in which case I'll switch to 'classic mode' RT's. Tim. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Bad ssl certs on some servers for api.twitter.com/1 ?
Hi there, I'm doing some dev work and I'm getting occasional ssl errors when making calls against api.twitter.com/1. The most recent was posting to favorites/create. Is it possible some of the servers have bad certificates? Or is it likely I'm doing something very wrong? Tim.
[twitter-dev] Re: [twitter-api-announce] Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Hey Marcel, Just checking - You haven't rolled this change yet right?: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers It seems attempting to follow a user who doesn't exist (through the members post) results in a 500 at the moment, rather than a 404. Tim. On Thu, Oct 29, 2009 at 9:00 AM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Request for posting to list memberships - error codes
Hey Twitter crew, When trying to add a user to a list it makes sense if a 404 is returned (I think) both if the user isn't found, or if the list (id or slug) isn't found. It would be cool if the content of the response could say whether it was the user or list that wasn't found. Cheers, Tim.
[twitter-dev] Re: Social Graph Methods: Removal of Pagination
Just like everyone knew the twitpocalypse was coming - but people still got burnt - even some high profile apps. An earlier day in the week is prudent if it's a planned change. On Sat, Nov 14, 2009 at 7:14 PM, Josh Roesslein jroessl...@gmail.comwrote: Well I think most issues should have been long resolved by now. Cursors have been live for a while now and there was plenty of warning ahead of today. The turn off should have no affect if you have ported to Cursors. On Fri, Nov 13, 2009 at 11:25 PM, Naveen Ayyagari knig...@gmail.com wrote: I agree, friday is a poor time to make planned changes to the API... On Nov 13, 2009, at 11:58 PM, Jesse Stay wrote: I've already implemented this, but for future sanity, can you guys avoid doing these major updates on Fridays when we're all not focusing as much on work? That way if there happen to be any bugs or problems our weekends aren't ruined. This seems to be a frequent occurrence on the Twitter API. Thanks, Jesse On Fri, Nov 13, 2009 at 3:03 PM, Wilhelm Bierbaum wilh...@twitter.com wrote: As previously announced by Alex Payne on September 24th (see http://bit.ly/46x1iL), we're removing support for pagination from the / friends/ids and /followers/ids methods. As of that time we set a hard deadline of October 26th, 2009. The original date has passed as we tried to give all of our partners extra time, but we are going to need to make the change now. At some point today, the page and count parameters will be ignored by the /friends/ids and /followers/ids methods and we will only be supporting cursors. Unfortunately, due to architectural considerations, cursor identifiers are not predictable. This means that you will have to extract the next and previous cursor identifiers from the results returned to you. For example, to get Obama's followers, we would first perform a GET against: http://twitter.com/followers/ids/barackobama.xml?cursor=-1 Which returns XML similar to: id_list ids id30592818/id (... more ids ...) /ids next_cursor1319042195162293654/next_cursor previous_cursor-8675309/previous_cursor /id_list To retrieve the next 5000 IDs, we would then perform a GET against: http://twitter.com/followers/ids/barackobama.xml?cursor=1319042195162293654 Note that cursors are signed 64-bit integers. Please refer to the documentation for our social graph methods for more information: http://apiwiki.twitter.com/Twitter-REST-API-Method:-friends+ids http://apiwiki.twitter.com/Twitter-REST-API-Method:-followers+ids Thanks!
[twitter-dev] Re: Work At Home - Earn $900 Per Week
How does that work? He's sending using someone else's email address that's already been approved to post on this list? Tim. On Thu, Nov 12, 2009 at 11:03 PM, Andrew Badera and...@badera.us wrote: It's spoofed spam FWIW ... Google Groups (and probably a lot of email lists) provide little real authentication. Tightening up SPF records seems to be a fix. (use -all) ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Nov 12, 2009 at 5:01 AM, Tim Haines tmhai...@gmail.com wrote: You should be sending this as a DM. On Thu, Nov 12, 2009 at 10:55 PM, MANOJ NEHA neha4ma...@gmail.com wrote: Work At Home - Earn $900 Per Week Just Work 1-2 Hours A Day Earn $27,000 A Month No Investments, Work anytime From Anywhere !! Visit Here http://e-way-solutions.blogspot.com/And Start Earning Now.
[twitter-dev] Re: MGTwitterEngine - anyone added list support yet?
Hey Zac, That's what I decided to do too. Interested in your point of concern given as an example though. MGTwitterEngine gives you a UUID for each request right? So you should be dropping those into an array for your tracking purposes so you know where they came from and what for (and which account), and then respond appropriately? One of the things I didn't like about it is that I couldn't find an easy way to gain access to the response body if an error occurs. I realized the subset of API calls I need is so small that I should just roll my own anyway though.. Tim. On Thu, Nov 12, 2009 at 10:26 AM, Zac Bowling zbowl...@gmail.com wrote: I give mgtwitterengine credit for being there (was there for me in a snap once) and being there first for cocoa devs to drop in, but there are some nasties to it. It's async callback/delegate pattern is odd (try supporting multiple accounts with it and you understand quickly that you don't where the data is coming from because there is no handle back to the account). Twitter's api isn't overly complicated so it's easy enough to roll your own API wrapper, which is what did in my own project. Zac Bowling @zbowling On Nov 10, 2009 3:01 PM, Tim Haines tmhai...@gmail.com wrote: Hey guys, Has anyone added list support to @mattgemmell's MGTwitterEngine yet? Cheers, Tim.
[twitter-dev] MGTwitterEngine - anyone added list support yet?
Hey guys, Has anyone added list support to @mattgemmell's MGTwitterEngine yet? Cheers, Tim.
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Does creating the same list twice via sync'ed methods result in duplicate streams? Sent from my iPhone On 10/11/2009, at 7:20 PM, Eric Gilbert eegilb...@gmail.com wrote: I'm developing an app that builds a few lists. Since it seems the only way to add users to lists is one id per call (please let me know if I'm mistaken), I experimented with populating the lists asynchronously. Both seem to build the list fine, and of course async is much faster. Here's the strange thing: although the lists created with each method have the same membership list, the lists streams are not the same. (Sync seems to be doing the right thing, but I haven't verified this rigorously.) For example, see http://twitter.com/eegilbert/right vs http://twitter.com/eegilbert/notsoright Strange. Cheers, Eric
[twitter-dev] Pyramid scheme to gain followers
Wow - http://www.tweetpopular.com Sadly I bet a bunch of users go for this too.
[twitter-dev] Re: Is image shrinking broken?
It's broken. Add a star here: http://code.google.com/p/twitter-api/issues/detail?id=1158 On Tue, Nov 3, 2009 at 9:54 PM, janole s...@mobileways.de wrote: Would be cool to have this fixed as soon as possible. I'm getting a lot of complaints because my mobile client silently discards any oversized avatars ( 10kB .) It's not a good idea to download dozens of 200 kB avatars if you're not on a flatrate mobile data plan ;-) Also, scaling all those avatars on the mobile phone takes quite some time ... @janole On 3 Nov., 06:25, TCI ticoconid...@gmail.com wrote: I am noticing an increase in the number of avatar images which do not get shrinked in the smaller versions. It is most noticeable in the twitter.com homepage as the images load very slowly from top to bottom. How are your clients handling this? In my case I am assuming the shrinking is working and therefore my page load times are being affected. Example: http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4...http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4...http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4. .. are all the same...
[twitter-dev] False positives on protected status
Hey guys, Is anyone observing twitter returning false positives on user's protected status? i.e. saying they're protected when they're not? Tim.
[twitter-dev] Re: Twitter Lists: /user/list/members.xml returning only 20 at a time
Yeah - it's a little stingy right now. Seeing as there's a limit on 500 members, it would be nice if it could return all the id's in 1 hit.. Tim. On Sat, Oct 31, 2009 at 9:58 AM, Dave Briccetti da...@davebsoft.com wrote: Cursoring is working, but it seems wrong to get just 20 at a time. GET /abdur/research/members.xml?cursor=-1 GET /abdur/research/members.xml?cursor=1316585587587157646 yields the same as GET /abdur/research/members.xml?count=200cursor=-1 GET /abdur/research/members.xml?count=200cursor=1316585587587157646
[twitter-dev] Does a 404 *always* mean a deleted tweet?
Hi there, I'd like to start deleting tweets that have been removed from twitter. I'm a little hesitant though, as I don't want to delete tweets accidentally that haven't really been deleted. I've noticed a couple of occasional odd things with false 404s when retrieving favorites, so I'm unsure whether I should trust the 404's from a user or tweet fetch. Does anyone know of any circumstances whereby a 404 might be returned for one of these calls when the tweet isn't actually deleted? Perhaps one scenario is when a user is temporarily suspended, and they're later unsuspended. Or - some kind of occasional error in Twitter's API. Any discussion appreciated, Tim.
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Marcel, Great changes. A couple of questions: - How long can a list description be? - A title can only be 15 chars - will that remain unchanged? - Will there be a little overlap where memberships and subscribers will still work while people migrate to followers/following? It would be awesome if there was a way to retrieve all member ids and a separate call for subscriber ids - cursored if necessary. Also, filed an edge case bug around list error messages a couple of days ago. http://code.google.com/p/twitter-api/issues/detail?id=1145sort=-openedcolspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component Cheers, Tim. On Oct 29, 9:00 am, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Find username/screenname through email addresses
It made me laugh. Not helpful, but entertaining. Dhaval, there's no way for you to do what you want. Twitter doesn't make email or email related functions accessible to third party devs in any way. Not that I know of anyway.. Tim. On Wed, Oct 28, 2009 at 12:05 AM, Andrew Badera and...@badera.us wrote: Wow, smartest post EVER. BAN? ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Tue, Oct 27, 2009 at 7:03 AM, Harshad RJ harshad...@gmail.com wrote: You could try signing in with that email address. People usually have easy to guess passwords. After signing in, the link to the profile page will have the screen-name at the end of the URL. On Tue, Oct 27, 2009 at 4:20 PM, dhaval dhaval.parik...@gmail.com wrote: Is it possible to find the screen name of a twitter user from an email address? -- Harshad RJ http://hrj.wikidot.com
[twitter-dev] Re: Twitter Lists Issues
Hi Paul, I asked similar questions to these in the IRC channel when Marcel (@noradio) was in there answering questions. The answers I got: If someone has added you to a list, and you want off, you need to block the list owner. If you then unblock the list owner, you remain off the list until/unless they add you again. If you block them before they add you, they can't add you. There's no other way - api or otherwise - that you can remove yourself. This discussion took place a few days ago. It wouldn't surprise me if Twitter does add a friendlier way to remove yourself from lists in the future. Cheers, Tim. On Mon, Oct 26, 2009 at 10:46 PM, Paul Kinlan paul.kin...@gmail.com wrote: Hi Guys, This isn't technically an API issue but a usage issue of the new to arrive Lists API. Retweets (outside of the API) have had an issue where by it is pretty easy to fake a users tweet, for instance someone could easily produce a tweet as a RT that I have never ever said: RT @PaulKinlan OMG Guess who is standing for parliament http://somelinkto-a-rickroll.com Myself and a colleague have been talking about forgery/defamation through Twitter lists, for instance, if someone didn't like me they could create a new user (or use their user), create a list of Racists and add me to that list, or something similar that would cause me to be associated with. This list is listed in my profile when someone looks at me in the Lists Following me For example: http://twitter.com/PaulKinlan/example-list-of-bad-peeps (I will delete this soon), this will also be in @ev's profile http://twitter.com/ev/lists/memberships So just some quick questions: If I block a person, will they be able to add me to a list? If I block a person will I be removed from their lists they have generated? Without blocking a person, will I be able to remove myself from a list? Through the API we be able to remove ourselves from a lists? Cheers, Paul
[twitter-dev] Re: Deprecation Notice: pagination on several methods is being replaced with cursoring on October 26, 2009
I guess they haven't indicated otherwise, so you'd have to presume it's still going to go ahead? I half expect they'll delay it due to performance issues raised, but I wouldn't bank on it. Tim. On Sat, Oct 24, 2009 at 6:49 PM, DustyReagan dustyrea...@gmail.com wrote: Bump. Anyone know if page deprecation still scheduled to happen on Oct. 26th? On Oct 22, 3:17 am, Rich rhyl...@gmail.com wrote: I hope not, Apple are being especially slow at approving my update at the moment that includes the cursor changes! On Oct 22, 3:20 am, DustyReagan dustyrea...@gmail.com wrote: Is page deprecation still scheduled to happen on Oct. 26th? Is this deprecation happening on all methods that have the cursor parameter enabled? -Dusty On Oct 8, 5:26 am, Kyle Mulka repalvigla...@yahoo.com wrote: Will thepageparameter on /statuses/user_timeline (or on any of the other timeline methods) be deprecated as well? https://twitterapi.pbworks.com/Twitter-REST-API-Method%3A-statuses-us... I've noticed a lot of failures on /statuses/user_timeline recently. Instead of thepageparameter, is it better to use max_id? -- Kyle Mulkahttp://twilk.com-putyour friends faces on your Twitter background On Sep 24, 8:47 pm, Alex Payne a...@twitter.com wrote: Hi, Recently, we documented a new pagination mechanism for our social graph methods, /friends/ids and /followers/ids. Traditional page-based pagination doesn't dovetail with our recent backend changes, and we've now exposed acursor-based pagination mechanism that's far more reliable. Today, we've documented that this new pagination mechanism is also available for the /statuses/friends and /statuses/followers methods. With that change, we're setting a hard deprecation date for traditional pagination on these four methods: October 26th, 2009. That's over a month from now. Once deprecated, we'll simply ignore the page parameter if it's sent by a client, and you'll get the default number of items for the method you're calling. For more information, seehttp:// apiwiki.twitter.com/Twitter-API-Documentation. Thanks. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Adding members to lists via API
Hey guys, I've just played around with adding members to a list via API. It turns out I can add protected members who I don't follow, but I can't add people that have blocked me. Not being able to add people who have blocked me makes sense. I'm wondering what the theory is behind being able to add protected members though? I guess there probably is a few reasonable use cases - i.e. keep a list of people I've sent a follow request to - and if their tweets don't show anyway, then what's the harm right? Just an observation I thought might be interesting to discuss. I need to update my error messages for adding users that have blocked. One of my testers struck this over the weekend. Tim.
[twitter-dev] Newly deleted tweets and Suspended/Protected Users
Hi there, Is there a way to bulk retrieve id's of tweets that have recently been deleted, or users that have been suspended or that have protected themselves? Cheers, Tim.
[twitter-dev] Favs not being recorded, or are seriously delayed
Hey guys, It seems when visiting twitter.com, and clicking on the star to add tweets to my favorites list, the favs aren't actually showing in my favorites list. (even 5 mins later) Just mentioning it so it gets on the radar if it's not already. Cheers, Tim.
[twitter-dev] Not cool to RT a protected tweet
Hey guys, @ev: It's not cool to RT a protected tweet http://twitter.com/ev/status/4955618846 Will the new RT api disallow you from RT'ing protected tweets? I think this would be a good move. Tim.
[twitter-dev] Re: API Proposal : Bulk fetch of user details
http://code.google.com/p/twitter-api/issues/detail?id=1078 On Fri, Oct 23, 2009 at 7:52 AM, Harshad RJ harshad...@gmail.com wrote: Hi, I am collating the thoughts in this thread [1] into a proposal to improve the efficiency of social-graphing applications. A common API access pattern for social-graphing applications seems to be: 1. Get the friend/follower ids of a user with [*friends/ids*] or [* followers/ids*] 2. Get user details one at a time with [*users/show*] (This approach saves on bandwidth by not using the [*statuses/friends*] method, as that would return redundant info when traversing a network) Now, since [*users/show*] is not a paginated API, it is easily possible to save bandwidth and connection overhead by clubbing multiple requests in one call. For a social-graphing application, the amount of user information needed is minimal. For example, the following amount of information would be sufficient for my application [1]: ?xml version=1.0 encoding=UTF-8? user id1401881/id screen_namedougw/screen_name followers_count1031/followers_count friends_count293/friends_count created_atSun Mar 18 06:42:26 + 2007/created_at statuses_count3390/statuses_count status created_atTue Apr 07 22:52:51 + 2009/created_at /status /user This is significantly smaller than the data returned by [*users/show*]. To prevent misuse of the new API the following could be enforced: 1. A maximum limit on number of users that can be queried in one request 2. Rate limiting based on number of users requested. For example, if (N) users' details were requested in one call, count it as (N/2) requests. This will provide incentive for using the new API as well as dettering misuse. [1] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/738e9157cf03adc7 [2] http://twinkler.in cheers, -- Harshad RJ http://hrj.wikidot.com
[twitter-dev] Re: [twitter-api-announce] Draft of List API documentation
Hey Marcel, Another 2 methods I'd like to see added to the list api - a way to get the id's of all current members (all 500), and a way to get the id's of all current subscribers - cursor based with as many per 'page' as possible. Cheers, Tim. On Fri, Oct 16, 2009 at 8:04 PM, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. You may notice this API is a bit of a departure from the rest of the API. It's a bit more, errr, REST than the rest. First off, here's the current payload for a list: ?xml version=1.0 encoding=UTF-8? list id1416/id nametall people/name full_name@noradio/tall-people/full_name slugtall-people/slug subscriber_count0/subscriber_count member_count3/member_count uri/noradio/tall-people/uri modepublic/mode user id3191321/id nameMarcel Molina/name screen_namenoradio/screen_name locationSan Francisco, CA/location descriptionEngineer at Twitter on the @twitterapi team, obsessed with rock climbing amp; running. In a past life I was a member of the Rails Core team./description profile_image_url http://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_normal.jpg /profile_image_url urlhttp://project.ioni.st/url protectedfalse/protected followers_count40059/followers_count profile_background_color9AE4E8/profile_background_color profile_text_color33/profile_text_color profile_link_color0084B4/profile_link_color profile_sidebar_fill_colorDDFFCC/profile_sidebar_fill_color profile_sidebar_border_colorBDDCAD/profile_sidebar_border_color friends_count354/friends_count created_atMon Apr 02 07:47:28 + 2007/created_at favourites_count131/favourites_count utc_offset-28800/utc_offset time_zonePacific Time (US amp; Canada)/time_zone profile_background_image_url http://a1.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg /profile_background_image_url profile_background_tiletrue/profile_background_tile statuses_count3472/statuses_count notificationsfalse/notifications geo_enabledtrue/geo_enabled verifiedfalse/verified followingfalse/following /user /list === Lists === POST '/:user/lists.:format' Creates a new list for the authenticated user. Parameters: * name: the name of the list. (required) * mode: whether your list is public of private. Values can be 'public' or 'private'. Public by default if not specified. (optional) Usage notes: :user in the url should be the screen name of the user making the request to create the list Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=tall peoplemode=private http://twitter.com/noradio/lists.xml POST/PUT '/:user/lists/:list_slug.:format' Updates the specified list. Takes the same parameters as the create resource at POST '/:user/lists.:format' (:name and :mode). Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=giantsmode=public http://twitter.com/noradio/lists/tall-people.xml GET '/:user/lists.:format' Lists your lists. Supported format: xml, json e.g. curl -u USERNAME:PASSWORD http://twitter.com/noradio/lists.xml GET '/:user/lists/memberships.:format' List the lists the specified user has been added to. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD http://twitter.com/noradio/lists/memberships.xml DELETE '/:user/lists/:list_slug.:format' Delete the specified list owned by the authenticated user. Parameters: * list_slug: the slug of the list you want to delete. (required) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -X DELETE http://twitter.com/noradio/lists/tall-people.xml GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specified list. Parameters: * list_slug: the slug of the list you want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD http://twitter.com/noradio/lists/tall-people/statuses.xml GET '/:users/lists/:list_slug.:format' Show a specific list you can use the new resource. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD http://twitter.com/noradio/lists/tall-people.xml === List members === POST '/:user/:list_slug/members.:format' Add a member to a list. Parameters: * id: the id of the user you want to add as a member to the list. (required) Usage notes: The :list_slug portion of the request path should be the slug of the list you want to add a member to. Supported formats: xml, json e.g.
[twitter-dev] Re: linespaces / whitespace being removed: bug or feature?
Bump. On 20/10/2009, at 3:54 PM, TjL luo...@gmail.com wrote: http://twitter.com/status/show/5008681027.xml| was entered with newlines between the words. It does not show the newlines. http://twitter.com/status/show/4999223282.xml shows that this was working just a few hours ago. Both were entered on the web. Is this a bug or an intended change?
[twitter-dev] Re: Draft of List API documentation
I'll +1 the requests for using the list id instead of the slug (and user id instead of screen name), and for a bulk add feature - I've already asked for a bulk remove feature... Tim. On Sun, Oct 18, 2009 at 5:34 PM, Beier beier...@gmail.com wrote: I'm just wondering why can't we use list 'id' to call API functions such as update, delete, timelines? I found out that list_slug can change when you update list name. This will give 3rd party apps lots of headaches. For example, right now my app has group features and I'm planning to migrate it to list. But if a user changes the list name on twitter.com or another app, then I'll have no idea and the list url I stored in database won't be valid anymore. On Oct 16, 12:04 am, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. You may notice this API is a bit of a departure from the rest of the API. It's a bit more, errr, REST than the rest. First off, here's the current payload for a list: ?xml version=1.0 encoding=UTF-8? list id1416/id nametall people/name full_name@noradio/tall-people/full_name slugtall-people/slug subscriber_count0/subscriber_count member_count3/member_count uri/noradio/tall-people/uri modepublic/mode user id3191321/id nameMarcel Molina/name screen_namenoradio/screen_name locationSan Francisco, CA/location descriptionEngineer at Twitter on the @twitterapi team, obsessed with rock climbing amp; running. In a past life I was a member of the Rails Core team./description profile_image_url http://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no.. ./profile_image_url urlhttp://project.ioni.st/url protectedfalse/protected followers_count40059/followers_count profile_background_color9AE4E8/profile_background_color profile_text_color33/profile_text_color profile_link_color0084B4/profile_link_color profile_sidebar_fill_colorDDFFCC/profile_sidebar_fill_color profile_sidebar_border_colorBDDCAD/profile_sidebar_border_color friends_count354/friends_count created_atMon Apr 02 07:47:28 + 2007/created_at favourites_count131/favourites_count utc_offset-28800/utc_offset time_zonePacific Time (US amp; Canada)/time_zone profile_background_image_url http://a1.twimg.com/profile_background_images/18156348/jessica_tiled... ./profile_background_image_url profile_background_tiletrue/profile_background_tile statuses_count3472/statuses_count notificationsfalse/notifications geo_enabledtrue/geo_enabled verifiedfalse/verified followingfalse/following /user /list === Lists === POST '/:user/lists.:format' Creates a new list for the authenticated user. Parameters: * name: the name of the list. (required) * mode: whether your list is public of private. Values can be 'public' or 'private'. Public by default if not specified. (optional) Usage notes: :user in the url should be the screen name of the user making the request to create the list Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=tall peoplemode=private http://twitter.com/noradio/lists.xml POST/PUT '/:user/lists/:list_slug.:format' Updates the specified list. Takes the same parameters as the create resource at POST '/:user/lists.:format' (:name and :mode). Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=giantsmode=public http://twitter.com/noradio/lists/tall-people.xml GET '/:user/lists.:format' Lists your lists. Supported format: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml GET '/:user/lists/memberships.:format' List the lists the specified user has been added to. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp:// twitter.com/noradio/lists/memberships.xml DELETE '/:user/lists/:list_slug.:format' Delete the specified list owned by the authenticated user. Parameters: * list_slug: the slug of the list you want to delete. (required) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -X DELETEhttp:// twitter.com/noradio/lists/tall-people.xml GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specified list. Parameters: * list_slug: the slug of the list you want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u
[twitter-dev] Re: New cursor methods are way too slow
FYI, My backend cares. On Fri, Oct 16, 2009 at 2:07 PM, jmathai jmat...@gmail.com wrote: I'm curious why you're using followers/ids and then users/show for each id? I tried using that and using statuses/followers and found that the total times were in the same ballpark. statuses/followers requires far fewer api calls if you're interested in user objects. FYI, I do want to add and say I agree that either method is EXTREMELY inefficient. Regardless what the argument against pages and for cursors are...the current implementation is painful from an end user perspective. Our backend doesn't really care, but our users don't like to wait 10-30 minutes for a web page to gather a social graph. I wish instead of a cursor I could get a snapshot id, # of pages and a page parameter. I don't know how it's implemented, but the ability to deterministically parallelize the calls - is such a benefit to the end user. Pages let me do that. On Oct 15, 9:17 am, Michael Steuer mste...@gmail.com wrote: That's great!! I'm currently using the suggested method (get IDs, then do users/show for each of them) and it's horrendously slow and cumbersome. It'd be great if you could get a 100 user objects at the time, based on 100 ids you provide.. On 10/14/09 7:30 PM, Chad Etzel c...@twitter.com wrote: I agree. I'm lobbying the team for something like this. -Chad On Wed, Oct 14, 2009 at 10:21 PM, Josh Roesslein jroessl...@gmail.com wrote: Yeah we really need a way to bulk request user payloads by giving a list of IDs. On Wed, Oct 14, 2009 at 9:19 PM, Tim Haines tmhai...@gmail.com wrote: Are you suggesting I should retrieve the 2k users 1 at a time from users/show once I have the ids? I'd essentially like to do this, but 100 at a time. I know I can get the 7000 ids in 2 calls (1 even without the cursors) - but I actually want the whole user objects.. Tim. On Oct 15, 2:56 pm, Chad Etzel c...@twitter.com wrote: If you are pulling down the entire social graph, why not use the social graph calls which would deliver all 7000 ids in 2 calls? You can also parallelize this process by looping through different users on each thread instead of using each thread to grab a different page/cursor of the same user. Regarding the code issue you submitted, if you have the users cached locally, you could use the social graph methods to determine the missing/new 2k users pretty quickly using the social graph methods and comparing ids. -Chad On Wed, Oct 14, 2009 at 9:50 PM, Tim Haines tmhai...@gmail.com wrote: Hi Chad, Statuses/followers. I've just timed another attempt - it took 25 minutes to retrieve 17957 followers with statuses/followers. Is there anything I can elaborate on in the filed issue to make it clearer? Tim. On Oct 15, 2:42 pm, Chad Etzel c...@twitter.com wrote: Hi Tim, You said Retrieving 7000 followers just took 20 minutes for me. Can you explain what you meant by that? Are you using the friends/ids, followers/ids methods or the statuses/friends, statuses/followers methods? -Chad On Wed, Oct 14, 2009 at 8:12 PM, Tim Haines tmhai...@gmail.com wrote: Hi'ya, I'm migrating my code to use cursors at the moment. It's frustrating that calls need to be synchronous rather than how paged calls could be asynchronous. Retrieving 7000 followers just took 20 minutes for me. I filed an issue that proposes a solution here: http://code.google.com/p/twitter-api/issues/detail?id=1078 If you retrieve friends or followers, please take a look and give it a star if it's important to you. If anyone can suggest a work around for this, I'd be happy to hear it. Cheers, Tim. -- Josh
[twitter-dev] Re: Issues I came across migrating to cursors
I'm migrating my code now. I just pulled down 7000 users. If I get a bad response to a call I'll retry it up to 5 times. It took 20 mins and 1 hour, which is going to be troublesome. Tim. On Oct 7, 6:59 pm, jmathai jmat...@gmail.com wrote: So a user comes to the site and I need to build their social graph. I have two options. 1) Use followers/ids and get ids of all their followers 5,000 at a time 2) Use statuses/followers and get profiles of all followers 100 at a time Ids alone don't really do me much good. So option 2 is more efficient for me (unless there's a batch user fetch api I'm unaware of). That being said, if a user has 10,000 followers (not uncommon) then I have to make 100 API calls to fetch profiles for all the followers. Not a big deal. Except, Twitter gives me random errors. Sometimes it's a 502 and other times a 400. I'm not confident that I won't randomly receive a different 4xx or 5xx response. I tried to put code in place so that on 5xx responses that I would *continue* and retry the request. That's when I got a 400 response. I have yet to fetch someone's entire graph using a sample account with 13,000 followers. Has anyone successfully migrated tocursorsand consistently pulled down a large (10k) graph?
[twitter-dev] New cursor methods are way too slow
Hi'ya, I'm migrating my code to use cursors at the moment. It's frustrating that calls need to be synchronous rather than how paged calls could be asynchronous. Retrieving 7000 followers just took 20 minutes for me. I filed an issue that proposes a solution here: http://code.google.com/p/twitter-api/issues/detail?id=1078 If you retrieve friends or followers, please take a look and give it a star if it's important to you. If anyone can suggest a work around for this, I'd be happy to hear it. Cheers, Tim.
[twitter-dev] Re: Issues I came across migrating to cursors
No - I pulled down the 7000 followers using the cursor calls - not just the ids. Tim. On Oct 15, 1:48 pm, Michael Steuer mste...@gmail.com wrote: So now that you pulled down 7000 IDs, are you making 7000 user/show calls to get the rest of the details? How's that working out? On 10/14/09 5:03 PM, Tim Haines tmhai...@gmail.com wrote: I'm migrating my code now. I just pulled down 7000 users. If I get a bad response to a call I'll retry it up to 5 times. It took 20 mins and 1 hour, which is going to be troublesome. Tim. On Oct 7, 6:59 pm, jmathai jmat...@gmail.com wrote: So a user comes to the site and I need to build their social graph. I have two options. 1) Use followers/ids and get ids of all their followers 5,000 at a time 2) Use statuses/followers and get profiles of all followers 100 at a time Ids alone don't really do me much good. So option 2 is more efficient for me (unless there's a batch user fetch api I'm unaware of). That being said, if a user has 10,000 followers (not uncommon) then I have to make 100 API calls to fetch profiles for all the followers. Not a big deal. Except, Twitter gives me random errors. Sometimes it's a 502 and other times a 400. I'm not confident that I won't randomly receive a different 4xx or 5xx response. I tried to put code in place so that on 5xx responses that I would *continue* and retry the request. That's when I got a 400 response. I have yet to fetch someone's entire graph using a sample account with 13,000 followers. Has anyone successfully migrated tocursorsand consistently pulled down a large (10k) graph?
[twitter-dev] Re: New cursor methods are way too slow
Hi Chad, Statuses/followers. I've just timed another attempt - it took 25 minutes to retrieve 17957 followers with statuses/followers. Is there anything I can elaborate on in the filed issue to make it clearer? Tim. On Oct 15, 2:42 pm, Chad Etzel c...@twitter.com wrote: Hi Tim, You said Retrieving 7000 followers just took 20 minutes for me. Can you explain what you meant by that? Are you using the friends/ids, followers/ids methods or the statuses/friends, statuses/followers methods? -Chad On Wed, Oct 14, 2009 at 8:12 PM, Tim Haines tmhai...@gmail.com wrote: Hi'ya, I'm migrating my code to use cursors at the moment. It's frustrating that calls need to be synchronous rather than how paged calls could be asynchronous. Retrieving 7000 followers just took 20 minutes for me. I filed an issue that proposes a solution here: http://code.google.com/p/twitter-api/issues/detail?id=1078 If you retrieve friends or followers, please take a look and give it a star if it's important to you. If anyone can suggest a work around for this, I'd be happy to hear it. Cheers, Tim.
[twitter-dev] Re: New cursor methods are way too slow
Are you suggesting I should retrieve the 2k users 1 at a time from users/show once I have the ids? I'd essentially like to do this, but 100 at a time. I know I can get the 7000 ids in 2 calls (1 even without the cursors) - but I actually want the whole user objects.. Tim. On Oct 15, 2:56 pm, Chad Etzel c...@twitter.com wrote: If you are pulling down the entire social graph, why not use the social graph calls which would deliver all 7000 ids in 2 calls? You can also parallelize this process by looping through different users on each thread instead of using each thread to grab a different page/cursor of the same user. Regarding the code issue you submitted, if you have the users cached locally, you could use the social graph methods to determine the missing/new 2k users pretty quickly using the social graph methods and comparing ids. -Chad On Wed, Oct 14, 2009 at 9:50 PM, Tim Haines tmhai...@gmail.com wrote: Hi Chad, Statuses/followers. I've just timed another attempt - it took 25 minutes to retrieve 17957 followers with statuses/followers. Is there anything I can elaborate on in the filed issue to make it clearer? Tim. On Oct 15, 2:42 pm, Chad Etzel c...@twitter.com wrote: Hi Tim, You said Retrieving 7000 followers just took 20 minutes for me. Can you explain what you meant by that? Are you using the friends/ids, followers/ids methods or the statuses/friends, statuses/followers methods? -Chad On Wed, Oct 14, 2009 at 8:12 PM, Tim Haines tmhai...@gmail.com wrote: Hi'ya, I'm migrating my code to use cursors at the moment. It's frustrating that calls need to be synchronous rather than how paged calls could be asynchronous. Retrieving 7000 followers just took 20 minutes for me. I filed an issue that proposes a solution here: http://code.google.com/p/twitter-api/issues/detail?id=1078 If you retrieve friends or followers, please take a look and give it a star if it's important to you. If anyone can suggest a work around for this, I'd be happy to hear it. Cheers, Tim.
[twitter-dev] Re: New cursor methods are way too slow
Thanks Chad. On Oct 15, 3:30 pm, Chad Etzel c...@twitter.com wrote: I agree. I'm lobbying the team for something like this. -Chad On Wed, Oct 14, 2009 at 10:21 PM, Josh Roesslein jroessl...@gmail.com wrote: Yeah we really need a way to bulk request user payloads by giving a list of IDs. On Wed, Oct 14, 2009 at 9:19 PM, Tim Haines tmhai...@gmail.com wrote: Are you suggesting I should retrieve the 2k users 1 at a time from users/show once I have the ids? I'd essentially like to do this, but 100 at a time. I know I can get the 7000 ids in 2 calls (1 even without the cursors) - but I actually want the whole user objects.. Tim. On Oct 15, 2:56 pm, Chad Etzel c...@twitter.com wrote: If you are pulling down the entire social graph, why not use the social graph calls which would deliver all 7000 ids in 2 calls? You can also parallelize this process by looping through different users on each thread instead of using each thread to grab a different page/cursor of the same user. Regarding the code issue you submitted, if you have the users cached locally, you could use the social graph methods to determine the missing/new 2k users pretty quickly using the social graph methods and comparing ids. -Chad On Wed, Oct 14, 2009 at 9:50 PM, Tim Haines tmhai...@gmail.com wrote: Hi Chad, Statuses/followers. I've just timed another attempt - it took 25 minutes to retrieve 17957 followers with statuses/followers. Is there anything I can elaborate on in the filed issue to make it clearer? Tim. On Oct 15, 2:42 pm, Chad Etzel c...@twitter.com wrote: Hi Tim, You said Retrieving 7000 followers just took 20 minutes for me. Can you explain what you meant by that? Are you using the friends/ids, followers/ids methods or the statuses/friends, statuses/followers methods? -Chad On Wed, Oct 14, 2009 at 8:12 PM, Tim Haines tmhai...@gmail.com wrote: Hi'ya, I'm migrating my code to use cursors at the moment. It's frustrating that calls need to be synchronous rather than how paged calls could be asynchronous. Retrieving 7000 followers just took 20 minutes for me. I filed an issue that proposes a solution here: http://code.google.com/p/twitter-api/issues/detail?id=1078 If you retrieve friends or followers, please take a look and give it a star if it's important to you. If anyone can suggest a work around for this, I'd be happy to hear it. Cheers, Tim. -- Josh
[twitter-dev] Re: Twitter, Please Explain How Cursors Work
On Wed, Oct 7, 2009 at 7:58 AM, jmathai jmat...@gmail.com wrote: I'd be willing to sacrifice some accuracy for speed since I'm not doing anything like auto-unfollow. From a sample set of 150k calls to the api the average latency I have (from the west coast) is .85 seconds. Grabbing a follower list serially, 100 at a time is painful. I much preferred what I was doing before (total # / 100 - fire off that many calls in parallel). If I dropped a few followers in the process, that was ok because it's so much faster and I don't need my copy of the social graph to be 100% accurate. I'm in the same boat - and filed this recently: http://code.google.com/p/twitter-api/issues/detail?id=1078colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
[twitter-dev] Re: Incorrect Status Count for one Person
I'm seeing something similar with the favourites call. Am about to start another thread on it. On Aug 26, 12:35 pm, markdmia ford.m...@principal.com wrote: I'm calling the Statuses Friends API with: https://twitter.com/statuses/friends.xml and the information coming back is correct for everyone but one user. Her last status information is stuck at Aug 22. She has added many statuses since then through the website but her status count remains fixed at 3212. Her current status count (viewed through the website) is 3266 and her last status (as of now) was around 6:00pm August 25th. This happened before and then it appeared to update correctly for awhile but now it is stuck again. Any ideas why?? Thanks!
[twitter-dev] Incorrect Status Count
Hi there, I think there's been some problems with status counts recently - specifically some being too high. I'm calling the favourites method a lot, and updating cached user profiles from the favourited tweet's author info. To see if the user profile is fresher than what I already have cached, I'm comparing the status count field - accepting that I'll be inaccurate if someone deletes a lot of tweets and their status count goes down. However, what I've found right now is that sometime my own status count was reported as being about 20 higher than what it is right now (on website and with a user call) - and I certainly haven't deleted 20 tweets recently. Has there been a bug with status counts recently, or is there are reason they are sometimes higher than what the website reports? I think this is true with many users - but I've used myself as the test case as I know I haven't deleted that many tweets. Over time I have, but not within the last month. Cheers, Tim.
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
I'm so happy gmail has a star feature, that deserved one. Tim. On Wed, Aug 12, 2009 at 7:28 AM, Dewald Pretoriusdpr...@gmail.com wrote: I have a spare bazooka in my basement. Let me know. I can FedEx it to you. Dewald On Aug 11, 4:23 pm, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Working or not work - is it lib dependent?
Hey guys, I'm not sure if it would be useful or not - but some 3rd party apps are unaffected, and some are. For me, I can get 60 - 100 requests out before the API stops responding for an hour or so. (I've not measured the hour - it might be a bit shorter or longer). The 60 - 100 calls are made with a whitelisted account (but not IP) using John Nunemaker's twitter gem (newest version) over standard auth. After things stop working, I can't do a curl request from the same server. I can do curl requests from other servers using the same account though. But if I do 60 - 100 requests from the other server, the API stops responding to that server too. If others are interested in seeing if there's some kind of pattern here, please post how you're making requests to the API. I'd be especially interested in hearing from people that aren't having problems. Tim.
[twitter-dev] Re: Status Update: 8/9 12:51 AM PDT
Thanks Chad - message appreciated. I would have missed an update to the third most recent post.. On Aug 9, 7:53 pm, Chad Etzel c...@twitter.com wrote: Hi all, While it is not strictly API related, I figured I would tell you an update has been made to:http://status.twitter.com/post/157979213/restoring-api-and-sms ...stating that the ability to update via SMS should now be restored. Hopefully this will show you that Ops is making positive progress in the situation and reassure everyone that we're working on it. -Chad
