[twitter-dev] Is it possible to get my friends' messages that have been retweeted by others?
Hello. I am just developing a simple application for analysis of tweet messages. But I cannot find a method that I want in Twitter API. Twitter statuses/retweets_of_me API returns my messages that have been retweeted by others. Like statuses/retweets_of_me API, is there any method or way that returns my friends' messages that have beed retweeted by others? I wonder if you can help me. Thanks for your reading. -- 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] How to know RT messages?
Hellow, guys.. I have a question about twitter messages. I want to know number of RT messages of other person. Can I get it using Twitter API or other ways? If you have some idea, please help me. Thanks all. -- 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] Twitter is over capacity. when I try to delete an application
When I try to delete an application
from http://dev.twitter.com/apps/edit/#{app's id} I get the fail whale. This
error has occurred since Saturday night, it's not a show stopper for me,
just wanted to point it out. Is there a better place to file bug reports
than to this mailing list?
Aaron Lee
--
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] Search API not returning tweet
I'm trying to understand why this query doesn't return a tweet : http://search.twitter.com/search.json?q=%23tea%20from:jamesb%20from:frankieroberto%20from:andrewpendrick%20from:monkeyhelpr%20from:topfife But this one does : http://search.twitter.com/search.json?q=%23tea%20from:jamesb%20from:frankieroberto%20from:andrewpendrick%20from:monkeyhelpr%20from:urbanwide The only difference seems to be changing the from:topfife account to from:urbanwide, the returned tweet is from the monkeyhelpr account, so changing the final from:account shouldn't make a difference as far as I'm aware. -- 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] Re: Draft of List API documentation
Seconding... In our app, whenever someone enters a screen name they want to add to a list, we have to do two API calls, to first get the id before adding the user to the list. Lee On Tue, Nov 3, 2009 at 11:38 PM, Damon Clinkscales sca...@pobox.com wrote: On Fri, Oct 16, 2009 at 1: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. Marcel, It would be nice if we could pass in either the user_id or the screen_name, wherever you are currently requiring a Twitter user id. This would be consistent with the rest of the REST API (and quite useful, saving an extra call). Thanks, -damon -- http://twitter.com/damon
[twitter-dev] Re: Does Rate Limiting Apply to Users or Clients?
If i have 2 accounts abc and efg, then i use a httpclient (java) as a client to get the friend's status from a web application (which use the Twitter4j), then how do this rate limiting for these 2 accounts abc and efg? each account has 150 requests? The how about the web applicaiton only have 150 requests can be sent? Thanks' Lee On Jul 7, 9:16 am, Abraham Williams 4bra...@gmail.com wrote: Each account has 150 requests / hr. If that that account is being used from several clients all of the hits will count against the 150. Abraham On Mon, Jul 6, 2009 at 19:54, devstudent andrey...@gmail.com wrote: If a person uses 2 clients. Can each client make 150 requests / hr, or does the 150 limit apply to both clients? -- Abraham Williams | Community Evangelist |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Is the rate limiting on IP or User a/c
Hi All, I would like to ask, the default rate limit for calls to the REST API is 150 requests per hour, is the rate limiting on IP (client) or on User A/C? I have a web application to get the friend's status. I didn't a testing to on this web application, using an A/C ABC to keep on getting the friend's status. It ran about 70++ time to got the result successfully, after that twitter returned exceed rate limiting. Then i tried to use another A/C DEF to continue to get the friend's status, but twitter returned exceed rate limiting. Guys, do you have any idea on this rate limiting is on IP or A/C? Thanks and Regards,
[twitter-dev] Re: Larger Users Not Returning Follower Data
I'll share are a few other wrinkles I've observed in the paged friends / followers API responses: - There are often more (sometime many more) pages than you'd expect based on the follower/friend counts listed in the profile - Pages in the middle of a long series of output pages usually but not always return 5000 elements - The only reliable way to determine the end of available output pages is to keep asking until an empty JSON response [] is returned - Friends / follow pages occasionally contain some duplicate entries from one page to another On the positive side, the paged output methods are *far* more reliable for high friend/follow lists than the old ones, when the list is long. The old methods were more convenient but only worked a small fraction of the time when the list was very long. I have test data for britneyspears from a few days ago, at that time the profile said 1,644,227, which would imply around 328 pages. There were actually 356 pages, containing 1,772,771 entries. I just looked at the profile page now and it says 1,745,417, which would still suggest 349 pages of data, less than what is actually there. And several of the pages return less than 5000 entries, so you can't assume that an unfilled page represents the end of the data. On Jun 8, 6:19 pm, Jesse Stay jesses...@gmail.com wrote: Doug, et. al., here's the problem(s) I'm running into. By forcing me to use paging for followers/ids and friends/ids, for someone like BritneySpears I now have to make over 350 requests to get through all her followers. Now I'm having huge rate limit issues because of that, not to mention how long it takes to get through the entire list. Would it be possible to set a number to specify how many user ids are returned per page so I don't have to make so many requests? In addition, I'm finding the pages aren't returning consistent data. Some are returning less than 5,000 results, and some aren't even returning data that should. So even with Paging I'm still unable to get through all of @britneyspears' followers. Any suggestions? @Jesse On Thu, Jun 4, 2009 at 12:26 AM, Doug Williams d...@twitter.com wrote: I've heard that list sizes greater than 150K-200K start to return timeouts at higher rates. Although I'd enjoy hearing first-hand experiences and recommendations. Thanks, Doug On Wed, Jun 3, 2009 at 9:19 PM, Jesse Stay jesses...@gmail.com wrote: In my case specifically it's the Social Graph methods. I didn't realize you had paging available now. Is there some logic as to when I should expect to page and when I can just rely on the full result? Jesse On Wed, Jun 3, 2009 at 9:56 PM, Doug Williams d...@twitter.com wrote: What methods in particular are you referring to? The social graph methods now support paging so retrieving all of that data is now possible, where it used to throw 502s. It does however require a bit of application logic to assume when paging is necessary (e.g. large follower counts). Additionally, we are making changes to the databases which cause latency that result in periodic 502s. We are not able to give definitive ETAs on these fixes due to priorities that change as unforeseeable critical needs arise. More specificity would be beneficial. Do you have a replaceable bug, problem, or suggestion that you would like to discuss? Thanks, Doug On Wed, Jun 3, 2009 at 7:22 PM, Jesse Stay jesses...@gmail.com wrote: I was discussing this with Iain, and have also talked about it with Damon, so I know I'm not alone in this. I am having huge issues retrieving follower and friend data for the larger users (1 million+ followers), most of the time returning 502 Bad Gateway errors. I know there are a few of these users getting really frustrated about our apps not being able to retrieve data for them. Is there a plan to fix this? Is the API team aware of this? Any ETA by chance? Thanks, @Jesse
[twitter-dev] iPhone Help
Is there another way to view friend's timeline without https://username:passw...@twitter.com/statuses/friends_timeline.xml;? For some reason, the iPod Touch/iPhone won't recognize the URL when I try it out. I can still retrieve the Public timeline though because there isn't the username:passw...@twitter.com username%3apassw...@twitter.com thing. Thanks!
[twitter-dev] Re: stream follow request not working
The (sampled) streaming API is good for collecting representative aggregate statistics on the public timeline, or full data on limited subsets. If you already know what keywords you're looking for, you can use the search API to find all mentions, but if you want to identify clusters of emerging topics, having a representative sample is almost as good as the full data in many cases. That gives you something to go back and run through the search API. If there wasn't enough traffic for it to show up in the sample, it probably isn't an emerging topic, and if you already know what topic keyword you're looking for, it will usually show up promptly in the search API. On May 21, 10:44 am, developerinlondon ebilliona...@gmail.com wrote: Ah I see, makes sense. Thanks. This API being Streaming means I can constantly stay connected to it without risking being banned. Correct? Would be useful to stay connected to the Spritzer call. Although I am confused what practical use it would be if I am getting a small portion as its a small percentage, meaning I may lose out on certain keywords if I am keeping an eye on them? On May 21, 2:12 pm, John Kalucki jkalu...@gmail.com wrote: The Streaming API /follow resource does not create new followings. Instead, it filters the stream of all public statuses created by a list of users. Perhaps the nomenclature is confusing. You probably observed a time period when the given small list of users did not update their status. The newlines are keep-alive probes. -John Kalucki Services, Twitter Inc. On May 21, 4:22 am, developerinlondon ebilliona...@gmail.com wrote: I tried using the stream API call documented here:http://apiwiki.twitter.com/Streaming-API-Documentation#Connecting At the bottom there is the following example - Example: Create a file called 'following' that contains, exactly and excluding the quotation marks: follow=12 13 15 16 20 87. Execute: curl -d @followinghttp://stream.twitter.com/follow.json- uAnyTwitterUser:Password.You will receive JSON updates from Jack Biz, Crystal, Ev, Krissy, but not from Jeremy, as he's a private user. I tried running it exactly as described. But my Curl just keeps throwing blank lines at me and I checked the user didnt get any new followings. Would be great to know. thanks, -developerinlondon
[twitter-dev] Re: Search API returns HTTP 406 Not Acceptable
Never mind. I figured out the problems was I switched queries to .xml instead of .json, and XML isn't one of the choices for the search API. On Apr 21, 12:43 pm, hjl hojohn@gmail.com wrote: I'm doing some testing this morning with the search API, which was working for a while but now is returning HTTP 406 Not Acceptable. Is this a symptom of the search API rate limiting? I ran a few queries with curl by hand, then ran a loop to see how far back the results pages go. The search API docs says rate limited requests should see 503 Service Unavailable, was wondering if it changed. I'll try it again in an hour or so and see if the search API starts responding again. But would still like to know if the response code for search rate limiting has changed.
Re: @oauth_now
Can we just open a support ticket somewhere (like on Google Code) and have everyone post the votes for OAuth to that rather than flooding the discussion lists please? (Yeah I know I'm just adding to it). On Jan 6, 3:37 pm, Nicole Simon nee...@gmail.com wrote: I thought some of you might be interested:http://pleasetwitterimplementoauthnow.com/ Please follow the user @oauth_now http://twitter.com/oauth_now to show your support for a better, more secure Twitter! Once you follow @oauth_nowhttp://twitter.com/oauth_nowyou will get exactly two direct messages from the user @oauth_now http://twitter.com/oauth_now. One message asks you to retweet this message http://tinyurl.com/safertwitter and the second message will be sent out once Twitter finally has implemented OAuth for every Twitter user. Nicole --http://twitter.com/NicoleSimon//http://mit140zeichen.de/http://crueltobekind.org//http://beissholz.de skype: nicole.simon / mailto:nee...@gmail.com phone: +49 451 899 75 03 / mobile: +49 179 499 7076
Search API screen return 404
Hello All, I'm searching for all the replies from a specified ID (1103044621) but the page is returning a 404. However if I change the since_id (up or down) everything works fine. The name I search for does not matter. If you change mrmlk to anything else I still get a 404. 404: http://search.twitter.com/search.atom?lang=enq=+to%3Amrmlksince_id=1103044621 Works fine: http://search.twitter.com/search.atom?lang=enq=+to%3Amrmlksince_id=1103044620 http://search.twitter.com/search.atom?lang=enq=+to%3Amrmlksince_id=1103044622 Any idea what is going on, and why post 1103044621 is special. Thanks Mike
Re: Status updates ignored, even though statuses not identical?
Just to clarify, here is an example of the request we are sending and
the json that's returned:
REQUEST
http://twitter.com/statuses/update.json?status=%40sixuntilme%2C+you+were+nominated+by+%40jakerutter+for+a+%23personal+Shorty+Award+http%3A%2F%2Fbit.ly%2FLAIv
STATUS CODE
200
RETURNED
data={in_reply_to_user_id:11676742,truncated:false,text:@HughBriss,
you were nominated by @AgingBackwards (and 5 others) for a #design
Shorty Award http:\/\/bit.ly\/SMcZ,user:{description:The best
short content creators on twitter in
2008,url:http:\/\/shortyawards.com,name:Shorty
Awards,protected:false,profile_image_url:http:\/\/s3.amazonaws.com\/twitter_production\/profile_images\/66792558\/logo_normal.png,screen_name:shortyawards,followers_count:750,location:,id:17663756},in_reply_to_screen_name:HughBriss,favorited:false,created_at:Thu
Dec 11 16:20:11 +
2008,in_reply_to_status_id:1051493141,id:1051503605,source:web}
In the JSON, the 'text' field is a status from 2 hours ago. It
completely ignored the update.
