[twitter-dev] Re: friends_timeline and following
This: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/bba8bbd5176fbb24/4a9cb5d5780da976?hl=enlnk=gstq=following+hwee+boon#4a9cb5d5780da976 and http://code.google.com/p/twitter-api/issues/detail?id=157. Supposed to be fixed? (I haven't verified. I stopped relying on it). On Apr 4, 2:54 am, Doug Williams d...@twitter.com wrote: I vaguely remember something, too, but my queries through the archives and issues list were fruitless. If this is replicatable, then we should open an issue. I'd be curious if it's still an issue once the big-users-everywhere change from April 1 propagates fully. @SuNcO: can you confirm you can recreate this at will? If so, can you open a new issue? Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Fri, Apr 3, 2009 at 11:50 AM, Chad Etzel jazzyc...@gmail.com wrote: I could swear that this topic has been discussed recently and that there was an issue for it, but I'm not finding anything... google is not so good at searching code snippets. -chad On Fri, Apr 3, 2009 at 2:46 PM, Abraham Williams 4bra...@gmail.com wrote: Do so searches on the issue tracker and if you don't find anything open an issue:http://code.google.com/p/twitter-api/issues/list On Fri, Apr 3, 2009 at 12:59, SuNcO sunco...@hotmail.com wrote: Nop, is not new. When that happend yesterday, i check via web and i appear on his following list (and he on my following list, else how can i see that update) Going to check now again (at night) On 3 abr, 00:20, Abraham Williams 4bra...@gmail.com wrote: Is it a user you recently started following? I may be a caching issue and the real value has not propagated yet. On Fri, Apr 3, 2009 at 01:19, SuNcO sunco...@hotmail.com wrote: Post before but after 30 minutes i can't see the msg, so i post again --- Im new on developing a twitter app. The first thing that i use is : http://twitter.com/statuses/friends_timeline.xml It returns me 20 msgs in xml format One of those msgs have followingfalse/following But.. i follow that user and that user is following me. What happend ? -- Abraham Williams | Hacker |http://abrah.am @poseurtech |http://the.hackerconundrum.com Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States -- Abraham Williams | Hacker |http://abrah.am @poseurtech |http://the.hackerconundrum.com Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from New York, NY, United States
[twitter-dev] Re: Extended user information element contains status/ element, too. is it expected?
Issues submitted. - Document: Extended user information contains status element http://code.google.com/p/twitter-api/issues/detail?id=479 - Document: form of the return value of the Search API http://code.google.com/p/twitter-api/issues/detail?id=480 Thanks. On 4月9日, 午前2:54, Doug Williams d...@twitter.com wrote: I'm working on that now, as well. Doug Williams Twitter API Supporthttp://twitter.com/dougw 2009/4/8 Yusuke yus...@mac.com Thanks. Please also document the official form of the return value of the Search API. Cheers, Yusuke On 4月9日, 午前1:35, Doug Williams d...@twitter.com wrote: The doc is out of sync. The user object should contain the status element. I'll get that fixed. Doug Williams Twitter API Supporthttp://twitter.com/dougw 2009/4/8 Yusuke yus...@mac.com It is documented that Basic user information element contains status element. So *Extended* user information element supposed to contain status element, too. But it's not documented. I'm developing Twitter4J - a Java wrapper for the API and need to ensure that. Thanks in advance, Yusuke On 4月9日, 午前12:23, Chad Etzel jazzyc...@gmail.com wrote: Not sure if it is expected or not (or if the doc is out of sync), but I would say having the last status included w/ the user object is very handy. -Chad On Wed, Apr 8, 2009 at 11:20 AM, Yusuke yus...@mac.com wrote: Hi, According to the REST API Doc, an Extended user information element doesn't contain a status/ element. But actually the API returns a user element with one status element. Is it a doc bug? Here is the trace log grabbed just several minutes ago. -- [Thu Apr 09 00:12:41 JST 2009]GEThttp:// twitter.com/account/verify_credentials.xml [Thu Apr 09 00:12:41 JST 2009]Response code: 200 [Thu Apr 09 00:12:41 JST 2009]Response: ?xml version=1.0 encoding=UTF-8? user id6358482/id nametwit4j/name screen_nametwit4j/screen_name locationlocation:0.5515412761891139/location description/description profile_image_urlhttp://static.twitter.com/images/ default_profile_normal.png/profile_image_url url/url protectedfalse/protected followers_count3/followers_count profile_background_color9ae4e8/profile_background_color profile_text_color00/profile_text_color profile_link_colorff/profile_link_color profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color profile_sidebar_border_color87bc44/profile_sidebar_border_color friends_count2/friends_count created_atSun May 27 09:52:09 + 2007/created_at favourites_count0/favourites_count utc_offset-32400/utc_offset time_zoneAlaska/time_zone profile_background_image_urlhttp://static.twitter.com/images/ themes/theme1/bg.gif/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count620/statuses_count notificationsfalse/notifications followingfalse/following status created_atMon Apr 06 16:34:02 + 2009/created_at id1463787270/id text4/7:id1/text sourcelt;a href=http://yusuke.homeip.net/ twitter4j/gt;Twitter4Jlt;/agt;/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/in_reply_to_user_id favoritedfalse/favorited in_reply_to_screen_name/in_reply_to_screen_name /status /user -- Cheers, Yusuke
[twitter-dev] count parameter need to be documented
Hi, AFAIK, count parameter is technically supported with several methods and it used to be documented. But now it's documented only with statuses/friends_timeline. According to the recent activities on the issue list, it seems to be still officially supported other than friends_timeline. - direct_messages http://code.google.com/p/twitter-api/issues/detail?id=115 - replies (mentions) http://code.google.com/p/twitter-api/issues/detail?id=235 Do you guys have any plan to document it soon? I confirmed that following methods support count parameter: - user_timeline Not yet documented. max is unknown. - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 - direct_messages/sent.xml Not yet documented. max is 100. issue#115 - statuses/mentions.xml Not yet documented. max is unknown. - statuses/repliess.xml Not yet documented. max is unknown. Thanks in advance, Yusuke
[twitter-dev] Re: count parameter need to be documented
Hi, I found that actually it is inconsistently documented. - user_timeline Not yet documented. max is unknown. It is documented here, http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline But not here, http://apiwiki.twitter.com/REST+API+Documentation#statuses/usertimeline - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 Documented here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages But not here: http://apiwiki.twitter.com/REST+API+Documentation#directmessages - direct_messages/sent.xml Not yet documented. max is 100. issue#115 Not yet documented: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages sent # the URL looks to be wrong. should be http://twitter.com/direct_messages/sent.format http://apiwiki.twitter.com/REST+API+Documentation#directmessages/sent - statuses/mentions.xml Not yet documented. max is unknown. Documented here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-mentions But not here: http://apiwiki.twitter.com/REST+API+Documentation#statuses/mentions Thanks, Yusuke On 4月19日, 午後11:55, Yusuke yus...@mac.com wrote: Hi, AFAIK, count parameter is technically supported with several methods and it used to be documented. But now it's documented only with statuses/friends_timeline. According to the recent activities on the issue list, it seems to be still officially supported other than friends_timeline. - direct_messageshttp://code.google.com/p/twitter-api/issues/detail?id=115 - replies (mentions)http://code.google.com/p/twitter-api/issues/detail?id=235 Do you guys have any plan to document it soon? I confirmed that following methods support count parameter: - user_timeline Not yet documented. max is unknown. - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 - direct_messages/sent.xml Not yet documented. max is 100. issue#115 - statuses/mentions.xml Not yet documented. max is unknown. - statuses/repliess.xml Not yet documented. max is unknown. Thanks in advance, Yusuke
[twitter-dev] Re: count parameter need to be documented
Yusuke, The REST API Documentation page is being phased out and is being replaced by the much simpler http://apiwiki.twitter.com/Twitter-API-Documentation (which links to all of the correct Twitter-REST-API-Method pages). Doug, perhaps you should remove the contents of the older page and link it to the newer one, to prevent confusion with future API changes? -Chris Thomson 2009/4/19 Yusuke yus...@mac.com Hi, I found that actually it is inconsistently documented. - user_timeline Not yet documented. max is unknown. It is documented here, http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline But not here, http://apiwiki.twitter.com/REST+API+Documentation#statuses/usertimeline - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 Documented here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages But not here: http://apiwiki.twitter.com/REST+API+Documentation#directmessages - direct_messages/sent.xml Not yet documented. max is 100. issue#115 Not yet documented: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages sent # the URL looks to be wrong. should be http://twitter.com/direct_messages/sent.format http://apiwiki.twitter.com/REST+API+Documentation#directmessages/sent - statuses/mentions.xml Not yet documented. max is unknown. Documented here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-mentions But not here: http://apiwiki.twitter.com/REST+API+Documentation#statuses/mentions Thanks, Yusuke On 4月19日, 午後11:55, Yusuke yus...@mac.com wrote: Hi, AFAIK, count parameter is technically supported with several methods and it used to be documented. But now it's documented only with statuses/friends_timeline. According to the recent activities on the issue list, it seems to be still officially supported other than friends_timeline. - direct_messageshttp:// code.google.com/p/twitter-api/issues/detail?id=115 - replies (mentions) http://code.google.com/p/twitter-api/issues/detail?id=235 Do you guys have any plan to document it soon? I confirmed that following methods support count parameter: - user_timeline Not yet documented. max is unknown. - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 - direct_messages/sent.xml Not yet documented. max is 100. issue#115 - statuses/mentions.xml Not yet documented. max is unknown. - statuses/repliess.xml Not yet documented. max is unknown. Thanks in advance, Yusuke
[twitter-dev] Re: count parameter need to be documented
Thanks for the clarification! -- Yusuke Yamamoto yus...@mac.com On 2009/04/20, at 0:55, Chris Thomson wrote: Yusuke, The REST API Documentation page is being phased out and is being replaced by the much simpler http://apiwiki.twitter.com/Twitter-API-Documentation (which links to all of the correct Twitter-REST-API-Method pages). Doug, perhaps you should remove the contents of the older page and link it to the newer one, to prevent confusion with future API changes? -Chris Thomson 2009/4/19 Yusuke yus...@mac.com Hi, I found that actually it is inconsistently documented. - user_timeline Not yet documented. max is unknown. It is documented here, http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline But not here, http://apiwiki.twitter.com/REST+API+Documentation#statuses/ usertimeline - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 Documented here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages But not here: http://apiwiki.twitter.com/REST+API+Documentation#directmessages - direct_messages/sent.xml Not yet documented. max is 100. issue#115 Not yet documented: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A- direct_messages sent # the URL looks to be wrong. should be http://twitter.com/direct_messages/sent.format http://apiwiki.twitter.com/REST+API+Documentation#directmessages/sent - statuses/mentions.xml Not yet documented. max is unknown. Documented here: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses- mentions But not here: http://apiwiki.twitter.com/REST+API+Documentation#statuses/mentions Thanks, Yusuke On 4月19日, 午後11:55, Yusuke yus...@mac.com wrote: Hi, AFAIK, count parameter is technically supported with several methods and it used to be documented. But now it's documented only with statuses/friends_timeline. According to the recent activities on the issue list, it seems to be still officially supported other than friends_timeline. - direct_messageshttp://code.google.com/p/twitter-api/issues/detail?id=115 - replies (mentions)http://code.google.com/p/twitter-api/issues/detail?id=235 Do you guys have any plan to document it soon? I confirmed that following methods support count parameter: - user_timeline Not yet documented. max is unknown. - friends_timeline Documented. max is 200. - direct_messages.xml Not yet documented. max is 100. issue#115 - direct_messages/sent.xml Not yet documented. max is 100. issue#115 - statuses/mentions.xml Not yet documented. max is unknown. - statuses/repliess.xml Not yet documented. max is unknown. Thanks in advance, Yusuke
[twitter-dev] Re: Status Element
Thanks. I looked through the structure again, and it looks like the library I was using had a bug. I fixed that, and I am getting the right results. On Apr 18, 12:56 pm, Chad Etzel jazzyc...@gmail.com wrote: Example output (i.e. the raw xml or json you are receiving) would be helpful. -Chad On Sat, Apr 18, 2009 at 3:26 PM, Joseph northwest...@gmail.com wrote: I am trying to process the Status Element, but followers_count is always coming back empty. All other fields (user.id, user.name, etc.) are OK. Any ideas? this is in response to an API call to get public_timeline (which returns the Status Element).
[twitter-dev] Re: Sign in with Twitter
Any idea when authenticate url will work again? On Apr 17, 4:31 pm, Matt Sanford m...@twitter.com wrote: Hi all, This behavior (i.e. which token is returned) is likely to change soon. Once again, stay tuned for updates. — Matt On Apr 17, 2009, at 01:02 AM, Abraham Williams wrote: The oauth_token returned from oauth/authenticate is the key from the users access tokens. as long as you store the access tokens you can match the returned oauth_token with what is in your database. On Fri, Apr 17, 2009 at 01:35, John Kristian jmkrist...@gmail.com wrote: I'm having trouble using /oauth/authenticate, too. After authenticating, Twitter redirects back to my consumer with a different oauth_token than the one I sent to initiate authentication. Twitter APIs don't accept either token. Sending the original request token to /oauth/access_token elicits HTTP 401 with an XML error Invalid / expired Token. Sending the second callback token elicits HTTP 500 Internal Server Error with an HTML body entitled Twitter / Error. When either token is used as an access token, Twitter responds with 401. The original request token elicits an XML error Invalid / expired Token; the second token elicits Failed to validate oauth signature or token. For signing I used the token secret associated with the original request token. The user has already given permission to this consumer. Help? On Apr 16, 12:25 pm, Dossy Shiobara do...@panoptic.com wrote: I just tried out the oauth/authenticate - I supplied a RequestToken and it redirected back to my callback URL with an AccessToken ... but, what's the token secret for this AccessToken? I only know the secret for the RequestToken I sent it ... Is the token secret the same for the AccessToken I get back? -- Abraham Williams |http://the.hackerconundrum.com Hacker |http://abrah.am|http://twitter.com/abraham Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Problem with Social Graph API
Hi, My profile is crictwits. When I invoke the friends/ids social graph API for my profile, I'm getting wrong results. The total count seems to be right, but the list isn't. For example, I'm following user shinils (id is 775881), but this user's id is not present in the list returned by http://twitter.com/friends/ids.xml?id=crictwits You can verify that I'm following this user by this call: http://twitter.com/friendships/exists.xml?user_a=crictwitsuser_b=shinils Many other friends are also missing in the list returned by the social graph API. Any clues? Regards, Karthik
[twitter-dev] Re: friends_timeline and following
Thank yo for your answer. Unfortunately, it doesn't seem to be fixed. I didn't check the other values returned by the statuses/followers mehod, but the following one is definitely not reliable (receiving INT or NULL values for roughly half of followers tested). :( Arnaud. On Apr 19, 12:16 pm, Hwee-Boon Yar hweeb...@gmail.com wrote: This:http://groups.google.com/group/twitter-development-talk/browse_thread... andhttp://code.google.com/p/twitter-api/issues/detail?id=157. Supposed to be fixed? (I haven't verified. I stopped relying on it). On Apr 4, 2:54 am, Doug Williams d...@twitter.com wrote: I vaguely remember something, too, but my queries through the archives and issues list were fruitless. If this is replicatable, then we should open an issue. I'd be curious if it's still an issue once the big-users-everywhere change from April 1 propagates fully. @SuNcO: can you confirm you can recreate this at will? If so, can you open a new issue? Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Fri, Apr 3, 2009 at 11:50 AM, Chad Etzel jazzyc...@gmail.com wrote: I could swear that this topic has been discussed recently and that there was an issue for it, but I'm not finding anything... google is not so good at searching code snippets. -chad On Fri, Apr 3, 2009 at 2:46 PM, Abraham Williams 4bra...@gmail.com wrote: Do so searches on the issue tracker and if you don't find anything open an issue:http://code.google.com/p/twitter-api/issues/list On Fri, Apr 3, 2009 at 12:59, SuNcO sunco...@hotmail.com wrote: Nop, is not new. When that happend yesterday, i check via web and i appear on his following list (and he on my following list, else how can i see that update) Going to check now again (at night) On 3 abr, 00:20, Abraham Williams 4bra...@gmail.com wrote: Is it a user you recently started following? I may be a caching issue and the real value has not propagated yet. On Fri, Apr 3, 2009 at 01:19, SuNcO sunco...@hotmail.com wrote: Post before but after 30 minutes i can't see the msg, so i post again --- Im new on developing a twitter app. The first thing that i use is : http://twitter.com/statuses/friends_timeline.xml It returns me 20 msgs in xml format One of those msgs have followingfalse/following But.. i follow that user and that user is following me. What happend ? -- Abraham Williams | Hacker |http://abrah.am @poseurtech |http://the.hackerconundrum.com Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States -- Abraham Williams | Hacker |http://abrah.am @poseurtech |http://the.hackerconundrum.com Web608 | Community Evangelist |http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from New York, NY, United States
[twitter-dev] Re: What does following in user information do?
Hi Matt, And thank you for the update. Unfortunately, it still doesn't seem to be fixed. I still receive a lot of incorrect following values (INT and NULL instead of BOOL) using the statuses/followers method. All the best, Arnaud. On Mar 27, 5:18 pm, Matt Sanford m...@twitter.com wrote: Hi there, This is a known issue [1] that I have been working on for some time. I have a fix ready to be deployed next week so hopefully this will start working correctly. Every API user wants and deserves the correct data and the cache should work correctly to keep load off the databases and still return you the correct results. The fix for this bug is a long time coming because we wanted to be sure it would fix the issue, perform well, and be resistant to breaking again in the future. Sorry for the long delay. Thanks; — Matt Sanford [1] -http://code.google.com/p/twitter-api/issues/detail?id=157 On Mar 26, 2009, at 05:15 PM, krwhite wrote: I can report that it's definitely broken in XML. The XML output I see shows a randomfollowingresult, which suggests to me that the entire result set is a cache from something else. If I may suggest a fix to twitter, how about an extra parameter for 'show_the_right_results' as a boolean? The command would only be slow and uncached for those who would rather have the correctfollowing information. In the future the parameter can just be ignored when it's faster with proper caching. This command is only sent when the user wants extended user information, so it's probably issued the least out of all of them I have implemented. I would assume that's a similar case for other clients. It would be pretty rough on the server as well to use the brute force method of getting ALL followers before displaying follow/unfollow, so I don't see many options right now aside from having multiple, confusing buttons.
[twitter-dev] Re: url as an input
Hi, Thanks for your replies. I tried with following url formats separately, all are properly url encoded. 1. Plain URL 2. TinyURL 3. Bitly UR But those 3 behaves differently for same URL. For URL A TinyURL has results, For B Bitly has results, Plain URL also have some results. Finally I passed all three combined using OR operator... That gave me total results little in little bit high volume.. Still even that composit search produces very less than on-site URL for the same result.. That s the issue.. On Apr 19, 1:29 am, Stuart stut...@gmail.com wrote: 2009/4/18 ParsePlz parseplz.a...@gmail.com: Actually what I meant, Say I did a search on URL at backtweets.com and gave me 256 results. But when I search the same url via their API using a program it gives 26 results ... That is why I am being confused on that.. Am I not in correct track or their API gives lesser output than their own onsite search ... Backtweets.com resolve redirecting URLs (tinyurl.com, bit.ly, etc) so that when you search it you're searching final URLs. The search API is searching the content of tweets and does not resolve the URLs. That's why they're different. -Stuart --http://stut.net/projects/twitter/
[twitter-dev] oAUTH - can it be done without interaction with a core browser?
Hello, I am trying to determine the best way or interacting with oAUTH. The application I am converting to oAUTH is written in VBScript tied around a screen reader object model providing for a rich UI experience. Can oAUTH be done so that I can: 1. Get all of the required items from the user outside of Twitter's interface? 2. Authenticate (like with basic auth of some type using XML posts)? 3. Be able to post back to get the token information. Here is the basic problem. I don't have programmatic access to either IE or Firefox (I can't embed the browser control) to be able to get information back. Any ideas are greatly appreciated. I sincerely hope that if this can not be done that basic auth will not go away. Jeff __ Information from ESET Smart Security, version of virus signature database 4019 (20090418) __ The message was checked by ESET Smart Security. http://www.eset.com
[twitter-dev] auto-reply?
Hey, im starting on a new project and was wandering if anyone can help? The project consists of twittering to the user (through @) and then having the user automatically reply to that user (again through @) with a message that someone has sent to it. scenario: the twitter user orange has the following messages sent to them (through @): -...@orange 1 -...@orange 2 -...@orange 3 -...@orange 4 -...@orange 5 then, when someone else sends an @ message to orange, orange would automaically reply to that user with a randomly selected previous @ message (1 or 2 or 3 etc...). any ideas/help? anything is appreciated. -bruce
[twitter-dev] Update on product category
I have no experience with Twitter. Before asking anything this is what I would like to accomplish: That a twitter member would be able to follow a product category updates in an ad site and only in that category. So the site's robot would post to twitter any new ad in that category using the the API. There are more than two thousand categories. Now the question: Is there a way to create different kinds of posts for a single user (the site's bot) that can be followed individually? Or must I create more than two thousand users? If this use is against any Twitter policy please excuse me as I have no experience with it. Regards, Clodoaldo
[twitter-dev] Re: Update on product category
On Sun, Apr 19, 2009 at 1:14 PM, Clodoaldo Pinto Neto clodoaldo.pi...@gmail.com wrote: Now the question: Is there a way to create different kinds of posts for a single user (the site's bot) that can be followed individually? Or must I create more than two thousand users? If this use is against any Twitter policy please excuse me as I have no experience with it. I think you'll find that Twitter has said repeatedly that this is not an appropriate reason to create lots of accounts, though they'll make exceptions if there's a very good reason. Seems to me that you might be able to accomplish your goal with hash tags, but that means that the followers would not follow them in the usual way, but would subscribe to a service that filtered by hash tag. If hash tags are going to survive and prosper, it seems that clients would do well to allow them to serve as filters (only show me tweets from user X with tags [a, b, c] or never show me tweets from user X with tags [a, b, d]). That sort of thing. Nick
[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?
On Sun, Apr 19, 2009 at 14:37, Jeff Bishop jeff.bis...@gmail.com wrote: 1. Get all of the required items from the user outside of Twitter's interface? 2. Authenticate (like with basic auth of some type using XML posts)? 3. Be able to post back to get the token information. I'm not completely sure what you want, but you could do something like this: - Obtain a request token and secret. - Start up a browser and send the user to http://twitter.com/oauth/authorize - Display a button that says something like click here when you're done - When the user clicks that button, assume that you're authorized with Twitter, and make a request to obtain the access token. - If that's not the case, repeat the process. The point is that you don't really need any information back through the callback other than the fact that the user has completed the authorization process. But that can be accomplished simply by having the user click a button. If you are able to register URI schemes in the operating system that will launch your app, there is a different way of doing this. Suppose you've registered mycoolapp:// with the operating system. Then you can supply an oauth_callback parameter to http://twitter.com/oauth/authorize that looks something like this: mycoolapp://twitter-authorize-complete After successful authorization, Twitter will then redirect to something like mycoolapp://twitter-authorize-complete?oauth_token=xxxscreen_name=guanuser_id=1234other_params=values That way your app will automatically be launched after authorization and you can call access_token at that point. Guan
[twitter-dev] TimeLine of 3~4 users
Hello suppose i'm following 100 users , how can i get the twittes only from 3 or 4 users ??? I meant using the api , so that the page will show the selected users status only .
[twitter-dev] Re: TimeLine of 3~4 users
Use http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timelinefor the 3 or 4 users. On Sun, Apr 19, 2009 at 16:06, ranacse05 ranacs...@gmail.com wrote: Hello suppose i'm following 100 users , how can i get the twittes only from 3 or 4 users ??? I meant using the api , so that the page will show the selected users status only . -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] authenticating
Hello everyone..
I am using commons httpclient to authenticate twitter through REST.
however, i haven't successfully authenticate using the below code: can
someone advise me what to fill in under AuthScope? and is my
GetMethod parameter correct?
HttpClient client = new HttpClient();
client.getState().setCredentials(
new AuthScope(www.twitter.com, 443, null),
new UsernamePasswordCredentials(userid, password)
);
GetMethod get = new GetMethod(https://www.twitter.com;);
get.setDoAuthentication( true );
try {
int status = client.executeMethod( get );
System.out.println(status + \n +
get.getResponseBodyAsString());
} catch (HttpException e1) {
e1.printStackTrace();
} catch (IOException e1) {
e1.printStackTrace();
} finally {
get.releaseConnection();
}
thanks and regards
Bryan
[twitter-dev] Re: Read and store Twitter responses
My skills are rather limited, but I was thinking PHP and MySQL. I was thinking about hiring it out, but putting together the process flow to help the programmer and also help me find the correct programmer. On Apr 16, 10:52 am, Nick Arnett nick.arn...@gmail.com wrote: On Wed, Apr 15, 2009 at 6:30 PM, CWitt wittma...@gmail.com wrote: I've looked through the discussion, what I do understand is that it is acceptable to store Twitter search results in my own database. What I am wondering is how to extract this information and actually store it in my database. Broad question... what language(s) do you code in? What databases are you familiar with? What is the web platform you are using? Nick
[twitter-dev] Re: TimeLine of 3~4 users
Hi Raquibul, I know what you are asking and it is not possible. Basically, if I may guess, you want to make a group of 3 people you follow and be able to make a call to their stream collated. You can not do this with an API method, however there are plenty of tools like magpie rss that can grab 3 feeds and parse them into one feed, to achieve what you are looking for. On Sun, Apr 19, 2009 at 9:40 PM, Raquibul Islam ranacs...@gmail.com wrote: i saw this before . How can i call with 3 users name together ? Abraham Williams wrote: Use http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline for the 3 or 4 users. On Sun, Apr 19, 2009 at 16:06, ranacse05 ranacs...@gmail.com mailto:ranacs...@gmail.com wrote: Hello suppose i'm following 100 users , how can i get the twittes only from 3 or 4 users ??? I meant using the api , so that the page will show the selected users status only . -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States -- Regards Rana homepage: http://ranacse05.wordpress.com Bangla job site: http://jobs.mukto.org -- Peter M. Denton www.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c
[twitter-dev] Re: API Disconnections Timeouts
I get it in particular on some of the really big Twitter accounts. It would be really nice to have a solution to this. All I can tell them is Twitter's broken - I hate doing that. Jesse On Sun, Apr 19, 2009 at 7:31 PM, Dossy Shiobara do...@panoptic.com wrote: On 4/19/09 8:32 PM, LeeS wrote: Lately, I've been getting a lot of both immediate disconnections or long timeouts, when trying to issue API calls. This is from a whitelisted Twitter account so rate limiting isn't the issue. I reported this last week in my Twitter API returning truncated XML responses[1] thread. [1] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/aee5785a56c3b56d/e86e49041a57e658 Everyone who's seeing this issue, please chime in - this way, the Twitter Ops folks can see how many third-party app. developers are being affected by this. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?
Jeff, We are still thinking internally about how we want to get around the browser for OAuth token requests. Although, at this time we don't have a particular implementation to share. Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Apr 19, 2009 at 9:41 PM, Jeff Bishop jeff.bis...@gmail.com wrote: Doug, I think if the user could log in to Twitter from a link and then be redirected to a place where the code could be shown to paste into the desktop application then that would work fine. Heck, you could even put a copy to clipboard button on that page so that the user could paste it in. Is this something planned or does it already exist? Jeff - Original Message - *From:* Doug Williams d...@twitter.com *To:* twitter-development-talk@googlegroups.com *Sent:* Sunday, April 19, 2009 9:22 PM *Subject:* [twitter-dev] Re: oAUTH - can it be done without interaction with a core browser? The call to http://twitter.com/oauth/authorize (or the Sign in with Twitter equivalent http://twitter.com/oauth/authenticate) requires a browser to render the HTML necessary for the user prompt. This is a limitation we recognize with the current beta release of the OAuth implementation. Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Apr 19, 2009 at 1:37 PM, Guan Yang g...@yang.dk wrote: On Sun, Apr 19, 2009 at 14:37, Jeff Bishop jeff.bis...@gmail.com wrote: 1. Get all of the required items from the user outside of Twitter's interface? 2. Authenticate (like with basic auth of some type using XML posts)? 3. Be able to post back to get the token information. I'm not completely sure what you want, but you could do something like this: - Obtain a request token and secret. - Start up a browser and send the user to http://twitter.com/oauth/authorize - Display a button that says something like click here when you're done - When the user clicks that button, assume that you're authorized with Twitter, and make a request to obtain the access token. - If that's not the case, repeat the process. The point is that you don't really need any information back through the callback other than the fact that the user has completed the authorization process. But that can be accomplished simply by having the user click a button. If you are able to register URI schemes in the operating system that will launch your app, there is a different way of doing this. Suppose you've registered mycoolapp:// with the operating system. Then you can supply an oauth_callback parameter to http://twitter.com/oauth/authorize that looks something like this: mycoolapp://twitter-authorize-complete After successful authorization, Twitter will then redirect to something like mycoolapp://twitter-authorize-complete?oauth_token=xxxscreen_name=guanuser_id=1234other_params=values That way your app will automatically be launched after authorization and you can call access_token at that point. Guan
[twitter-dev] Re: About statuses/friends_timeline
For performance reasons, we cache each status object and construct the timeline from these cached objects at request-time. Therefore, complete user objects are returned with each status in a timeline. If you have a project that is bandwidth constrained, you should set up a proxy that strips unnecessary fields before forwarding the data to the edge device. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 12:13 PM, Vitus vitusm...@gmail.com wrote: Hi2all! I've found, that http://twitter.com/statuses/friends_timeline.xml response with XML document, where info about user is repeated for every status. I think, it's so uneffective by traffic volume reason! How can I get friend's statuses without full info about the author? Thanks!
[twitter-dev] Re: Test Account Procedures
We do not have any notion of a test account. Developers occasionally create development accounts to keep personal or application accounts clear of noise from development and debugging efforts. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 10:40 PM, Greg greg_os...@sbilabs.com wrote: Hi Alex, I was wondering if you have a provision/process for obtaining Test Accounts and Data. I want to try to avoid creating test accounts. Thanks, Greg.
[twitter-dev] Re: About statuses/friends_timeline
Ok, Doug, thank you for reply! On 20 апр, 11:37, Doug Williams d...@twitter.com wrote: For performance reasons, we cache each status object and construct the timeline from these cached objects at request-time. Therefore, complete user objects are returned with each status in a timeline. If you have a project that is bandwidth constrained, you should set up a proxy that strips unnecessary fields before forwarding the data to the edge device. Doug Williams Twitter API Supporthttp://twitter.com/dougw On Sat, Apr 18, 2009 at 12:13 PM, Vitus vitusm...@gmail.com wrote: Hi2all! I've found, thathttp://twitter.com/statuses/friends_timeline.xml response with XML document, where info about user is repeated for every status. I think, it's so uneffective by traffic volume reason! How can I get friend's statuses without full info about the author? Thanks!
