[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
I have the sample problem too, can't post update with Chinese.. On Apr 13, 1:56 am, Guan g...@yang.dk wrote: On Apr 12, 8:08 am, Cmdr J0hn kazuhiro.is...@gmail.com wrote: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string: POSThttp%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 And a body is: status=%E3%81%82 Any suggestion anyone? I have exactly the same problem. I have checked with the OAuth signing guide athttp://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html, which even considers the case of non-English parameters that lead to multibyte characters, and their signature matches mine. I think this is a bug in the way Twitter verifies signatures when multibyte characters are present, and I've filed a bug report with them. Guan
[twitter-dev] Re: StalkDaily worm - it's really spreading :)
I'm sure you're aware of it, but Mikeyy's back. http://twitter.com/davemorinand http://twitter.com/eldon. You guys are escaping all HTML but links, right? @Jesse On Sat, Apr 11, 2009 at 8:24 PM, Alex Payne a...@twitter.com wrote: We've been on it for some time. It's actually not really spreading, and hasn't been for hours. Lots of people are talking about it, but the actual attack vector is closed. On Sat, Apr 11, 2009 at 19:05, Dossy Shiobara do...@panoptic.com wrote: I don't know if the Twitter folks are doing anything about it, but the StalkDaily worm is propagating fast. Better remove the user bio from Twitter profile pages and scrub the database ASAP ... -- 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) -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Do any of the libraries implement a method for returning statuses_count?
Ok. So then, in Python, which library do I need to inmport to parse the returned XML? I have simplejson (needed it for python-twitter) so maybe that would be easier? On Apr 13, 1:56 am, Peter Denton petermden...@gmail.com wrote: I dont know which specific libraries, but its a very common part of the API. For example, if you look at:http://twitter.com/users/show/khyron4eva.xml you will get xml back and are able to extract: $status_count = $xml - statuses_count; On Sun, Apr 12, 2009 at 12:57 PM, Khyron khyron4...@gmail.com wrote: If so, which one? If not, what is the best way to extract this piece of info? I'm a beginning programmer here, but I need this bit to accomplish my goal. -- You can choose your friends, you can choose the deals. - Equity Private AlphaGuy -http://alphaguy.blogspot.com On Twitter - @khyron4eva -- Peter M. Dentonwww.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter -http://tinyurl.com/bopu6c
[twitter-dev] Re: StalkDaily worm - it's really spreading :)
I'm sure you're aware of it, http://status.twitter.com/post/95693986/update-on-worm -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Philosophy will clip an angel's wings. -- John Keats ---
[twitter-dev] Please add us as well
Twitter username: accuwiz Name: CJ Singh Company: Accuwiz Technologies Website: www.accuwiz.com Relevant technologies: PHP, MySQL, AJAX
[twitter-dev] Length of OAuth tokens and secrets
Hi, A quick question: is there a maximum length on OAuth tokens and token secrets? Because so far I've found that request tokens and secrets vary in length, and I'm going to be storing some access tokens in a database and would like to know how large to make my character fields. Thanks a lot, Regards, Zack
[twitter-dev] Re: autenticating user using OAuth
As far as I know this is not an issue. Users only have to accept the first time they use an application; on subsequent authorization requests, Twitter will redirect them to your app straight away. On Apr 12, 6:08 pm, Hameedullah Khan hameed.u.k...@gmail.com wrote: Hello Twitterers, I have been building my application and everything is working fine, just I am stuck on one thing. What is the correct way to authenticate user when they come back to my site for using my application, I want to authenticate them and using Oauth, but if I Request a toaken and send them to authorization URL they have to click on the Accept button, this is okay for the first time, but if they will have to do that everytime they login to my application this will not be good. May be I am missing something, so if someone can guide me I would really appreciate it. Thanks, Hameedullah Khan.
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
Same problem here. I can't post update too, with cyrillic characters.
[twitter-dev] Re: Do any of the libraries implement a method for returning statuses_count?
On Mon, Apr 13, 2009 at 2:00 AM, Khyron khyron4...@gmail.com wrote:
Ok.
So then, in Python, which library do I need to inmport to parse the
returned
XML? I have simplejson (needed it for python-twitter) so maybe that
would
be easier?
Yes. If you decode the content you get from a status request, like this:
data = simplejson.loads(content)
The number of statuses you have retrieved will be the length of the
resulting object -- len(data)
However, you'll need to page through the results (make additional http
requests) to get more than 200 statuses. You can concatenate the received
content before parsing it. That would look like the following, in a loop:
if response.status == 200:
if
response['content-type'].startswith('application/json'):
try:
data = json.loads(content)
except:
print json decode failed: %s % (content)
return False
if 'next_page' in data:
next_page = data['next_page']
if 'results' in data:
data = data['results']
if not all:
return data
elif len(data) and i self.max_pages:
concat_content += (data)
[twitter-dev] Re: Limit for following new people (per hour)?
Hi there, There is more information on follow limits at http://help.twitter.com/forums/10713/entries/14959 Thanks; — Matt Sanford / @mzsanford On Apr 12, 2009, at 07:07 PM, Nick Arnett wrote: I believe there is a limit of 2000 until 2000 people are following you, then it increases. Nick On 4/12/09, Madu7 mw...@web.de wrote: I am on the whitelist for the Twitter API and use the friendships/ create method to follow new people. But now I cannot follow a user any more. So is there a limit which controls how many users you can follow (per hour/day...)? I hope you can help me. Thanks in advance!
[twitter-dev] Re: Length of OAuth tokens and secrets
Hi there, The maximum length is 50 characters for both the token and the secret. Thanks; — Matt Sanford / @mzsanford On Apr 12, 2009, at 11:55 PM, disturb...@googlemail.com wrote: Hi, A quick question: is there a maximum length on OAuth tokens and token secrets? Because so far I've found that request tokens and secrets vary in length, and I'm going to be storing some access tokens in a database and would like to know how large to make my character fields. Thanks a lot, Regards, Zack
[twitter-dev] Re: Do any of the libraries implement a method for returning statuses_count?
On Mon, Apr 13, 2009 at 7:43 AM, Nick Arnett nick.arn...@gmail.com wrote:
Ack chrome sent the reply before I was ready... trying to fix the white
space to make it proper Python, I hit tab and return, which sent the
message!
Anyway, you wouldn't need the lines that have to do with next_page or
results, those are for other kinds of requests. The idea is to increment a
page (page=1)parameter in your request URL in the loop, continuing until
you get no data (or a result code other than 200), which indicates that
you've gotten all the statuses Twitter is storing.
Let me try again to show example code here... There's some stuff here that
lets me other url parameters, which you might not need. self.http is an
instance of httplib2.Http(), self. max_pages is a variable for an upper
limit on the number of pages I get and it sets self.last_status_id to the id
of the last status it received. There's some simple error handling and
retries when the error seems to be something temporary.
I haven't tested this code, but I adapted it from something that is working
fairly reliably. The white space is screwed up
i = 0
concat_content = []
url_parameters = [count=200]
trys = 0
paged = True
page_url = http://twitter.com/statuses/user_timeline/%s.json; %
(twitter_id)
while 1:
i += 1
params = .join(url_parameters)
if paged:
if len(params):
page_url = url + ?%spage=%s % (params, i)
else:
page_url = url + ?page=%s % (i)
elif len(params):
page_url = url + ?%s % (params)
else:
page_url = url
response, content = self.http.request(page_url, method)
if response.status == 200:
if response['content-type'].startswith('application/json'):
try:
data = json.loads(content)
except:
print json decode failed: %s % (content)
return False
if len(data) and i self.max_pages:
concat_content += (data)
else:
self.last_status_id = concat_content[-1]['id']
return concat_content
if response.status in (500, 520, 503):
time.sleep(10)
trys += 1
if trys = 3:
print %s failed with internal errors % (status_type)
return False
else:
print %s failed: %s; Reason %s % (status_type, twitter_id,
response.reason)
return False
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
Hi all, Anyone having the problem please add a comment to the Google Code issue [1]. Please include the following if possible: 1. What language, library and version are you using? » For Example: Ruby oauth gem v0.2.7, or PHP oauth-php r50 2. What application is this for? » For Example: http://twitter.com/oauth_clients/details/104 3. This is the hardest one but hopefully a few people can provide it: What was the string passed into the signature method, and what was the resulting signature? » For Example: Input was 'POSThttp…status=%E3%81%82' (please don't abbreviate it, this is what I'll use to compare) and the signature was '123454tfsdfY346rdfvs' » Side note: %E3%81%82 is the correct URL encoding of あ [2], Julio was thinking of HTML encoding. We updated our OAuth gem because it incorrectly handled non-ascii characters and either this new version has a bug (possible) or the bug in the old version also exists in other libraries (also possible, since many of these are based on the same example code). At this point I'm trying to figure out which one matches the spec and then we can make it work from there. Thanks; — Matt Sanford [1] - http://code.google.com/p/twitter-api/issues/detail?id=433 [2] - http://www.fileformat.info/info/unicode/char/3042/index.htm On Apr 13, 2009, at 06:05 AM, minimoo...@gmail.com wrote: Same problem here. I can't post update too, with cyrillic characters.
[twitter-dev] Re: Messages with accented characters get truncated
Hi John, The correct URL encoding of é is %C3%A9 and not %E9. Checkout the UTF-8 section at [1]. The é character is my nemesis as a character encoding weenie. The Windows default character encoding (Windows-1252) uses %E9 but in Unicode it is %C3%A9. Since é is such a common character it's very common for it to point out encoding issues. Try putting %C3%A9 in the URL or check out this blog post [2] on InternetCanonicalizeUrl and UTF-8. Thanks; — Matt Sanford [1] - http://www.fileformat.info/info/unicode/char/00e9/index.htm [2] - http://dalelane.co.uk/blog/?p=311 On Apr 11, 2009, at 12:15 AM, John wrote: I use a Windows function called InternetCanonicalizeUrl to encode status messages before posting them to Twitter. It encodes é as %E9. So for example, café mocha turns to caf%E9%20mocha. When I post this as a status update to Twitter, it shows up as caféocha. The m is dropped for some reason. Is this a known issue? Thanks.
[twitter-dev] Oauth and Twitter for login.
Hi, I have just started to implement oAuth for http://www.twollo.com, and when registering my app for oAuth I noticed: Use Twitter for login: Yes, use Twitter for login Does your application intend to use Twitter for authentication? This is excellent news, for reasons I have mentioned in previous emails, however, unless I have missed something, is there anything I need to do to use this functionality? Or is it just the normal oAuth workflow - I am hoping that it is similar to the way I implement oauth support on http://oauth.twe2.com/ Paul.
[twitter-dev] Re: Oauth and Twitter for login.
Hi Paul, This was mentioned in one of the change log notices last week. Well, I mentioned that we're half-deployed. I'm awaiting a few more pieces before there is an official announcement. Stay Tuned; — Matt Sanford On Apr 13, 2009, at 08:40 AM, Paul Kinlan wrote: Hi, I have just started to implement oAuth for http://www.twollo.com, and when registering my app for oAuth I noticed: Use Twitter for login: Yes, use Twitter for login Does your application intend to use Twitter for authentication? This is excellent news, for reasons I have mentioned in previous emails, however, unless I have missed something, is there anything I need to do to use this functionality? Or is it just the normal oAuth workflow - I am hoping that it is similar to the way I implement oauth support on http://oauth.twe2.com/ Paul.
[twitter-dev] Is there a way to tell if a tweet has been favorited (regardless of user)?
I am playing with favorites and am trying to determine if a given tweet has been favorited by anyone at all. That is, given this tweet: https://twitter.com/epc/status/1500168995 which I’ve favorited with another account (@artificllc), is there a way to determine that it's been favorited, either by the author of the tweet (@epc) or by any other authenticated user? My checks with the API seem to indicate that @artificllc will get favoritedtrue/favorited when retrieving that tweet, but @epc and any other id will receive favoritedfalse/favorited. The API seems geared to showing what tweets a given user has marked as favorites, but there doesn't appear to be a way to see which of a user's tweets have been marked as favorites by others. Should I open an issue? -- -ed costello @epc
[twitter-dev] Re: Oauth and Twitter for login.
Hi Matt, Yeah I saw the change log, but thought that the presence in the UI was the other half of the deployment. Sorry about that, I am pretty eager :) Ah well, I look forward to seeing the solution so I can put it into both twollo and twe2 :) Cheers, Paul 2009/4/13 Matt Sanford m...@twitter.com Hi Paul, This was mentioned in one of the change log notices last week. Well, I mentioned that we're half-deployed. I'm awaiting a few more pieces before there is an official announcement. Stay Tuned; — Matt Sanford On Apr 13, 2009, at 08:40 AM, Paul Kinlan wrote: Hi, I have just started to implement oAuth for http://www.twollo.com, and when registering my app for oAuth I noticed: Use Twitter for login: Yes, use Twitter for login Does your application intend to use Twitter for authentication? This is excellent news, for reasons I have mentioned in previous emails, however, unless I have missed something, is there anything I need to do to use this functionality? Or is it just the normal oAuth workflow - I am hoping that it is similar to the way I implement oauth support on http://oauth.twe2.com/ Paul.
[twitter-dev] OAuth Failed to validate oauth signature and token if application already authorized
Hello, Recently, I have noticed that if I attempt to do a request token / access token exchange, i.e. a new application OAuth workflow, I always fail with Failed to validate oauth signature and token from Twitter if the application has already been successfully authorized in a previous workflow. If I revoke the application and try again, it works fine. Now I understand the motive for that, to avoid unnecessary load of having apps that perform the OAuth exchange on every user session, but this was not how it was working before. Did I miss an API announcement? My app persists the token, so for me this isn't the end of the world. First I'd like to know if this is expected behavior. I can faithfully reproduce the scenario of no access, gain access, try to gain access again and fail, revoke access and try again to succeed. My expectation is the OAuth process works even if the user has already granted access to the user. Anyone experiencing this right now?
[twitter-dev] Re: counting rate limits against an oauth consumer
The behavior of a whitelisted IP address is what you are requesting. Whitelisted IP addresses making calls on behalf of a user will use the IP address' rate limit, not the users. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 11, 2009 at 10:21 PM, Julio Biason julio.bia...@gmail.comwrote: Hey, I'm guessing it would allow some abuse. Someone would start requesting application IDs like crazy and spam the hell of the system. Once he blow up one application ID, it would just switch to another one. Although some sort of list-of-applications-sorted-by-requests would allow a user to easily see the applications that are not behaving nicely. On Sun, Apr 12, 2009 at 1:16 PM, cpatil cpa...@gmail.com wrote: Hi, Is there a reason why the rate limit is not applied to an oauth consumer (the application) instead of the authenticating user? It would prevent an offending application to use up the limits of a user and allow other applications continue to be able to service the user. thx/c -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] New Ruby Twitter API Library: Grackle
Hi all, Just wanted to let everyone know that I've released a new Ruby Twitter API library called Grackle. It's at http://github.com/hayesdavis/grackle It works with both the search and REST APIs and supports both basic and OAuth authentication. The main thing that sets it apart is that it's designed to be resilient in the face of changes to the API. Everything's dynamic, so new API methods, changes to parameters or modifications to returned data don't require changes to the library itself. That has been quite helpful in my projects (and others that use it as well) as the guys move forward very quickly with new API functionality. Would it be possible to have it included among the available libraries on the wiki? Please let me know if you have any feedback, suggestions for improvement, etc. Thanks. Hayes Davis @hayesdavis
[twitter-dev] Re: Limit for following new people (per hour)?
OK, thank you. Does the limit exist even if you are on the whitelist? But that's the general limit. I wonder if there's a limit per hour. For example: You are allowed to create 50 friendships per 60 minutes time period. If you reach the limit after 30 minutes, you have to wait for 30 minutes to create the next ones. Is there such a limit? On 13 Apr., 04:07, Nick Arnett nick.arn...@gmail.com wrote: I believe there is a limit of 2000 until 2000 people are following you, then it increases. Nick On 4/12/09, Madu7 mw...@web.de wrote: I am on the whitelist for the Twitter API and use the friendships/ create method to follow new people. But now I cannot follow a user any more. So is there a limit which controls how many users you can follow (per hour/day...)? I hope you can help me. Thanks in advance!
[twitter-dev] Re: Using OAuth or API can u monitor Tweets have 3rd party app react
The API is stateless and requires polling. We do not offer any sort of trigger or push based alerts. Therefore, your application will either have to use the Search API or REST API to monitor a search term or account, respectively, then act on it accordingly. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 11, 2009 at 8:08 PM, rpsfan rps...@gmail.com wrote: Hi Im wondering if our users whom have given us their Twitter name either via OAuth or API would be able to Twitter a command or even a word and when they do have it call to our app to take action? If this can not be done then could we monitor our users Twitter account every four hours to see if they have stated this action and if so then we would take action? Is there a limit to how many hits an app can hit Twitter a day? If the above was not clear here is an example Im Joe and Im on Twitter and this new thing a mo bob service. Joe is selling a couch in Murfreesboro, TN and Tweets Im selling a couch. The word sell is what would trigger this thing a mo bob 3rd party app and the app would search the web (craigslist and other sites) to find buyers and send joe an email listing those buyers. Thanks
[twitter-dev] Re: New Ruby Twitter API Library: Grackle
Thanks Hayes! Added to the libraries page. Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 9:19 AM, Hayes Davis ha...@appozite.com wrote: Hi all, Just wanted to let everyone know that I've released a new Ruby Twitter API library called Grackle. It's at http://github.com/hayesdavis/grackle It works with both the search and REST APIs and supports both basic and OAuth authentication. The main thing that sets it apart is that it's designed to be resilient in the face of changes to the API. Everything's dynamic, so new API methods, changes to parameters or modifications to returned data don't require changes to the library itself. That has been quite helpful in my projects (and others that use it as well) as the guys move forward very quickly with new API functionality. Would it be possible to have it included among the available libraries on the wiki? Please let me know if you have any feedback, suggestions for improvement, etc. Thanks. Hayes Davis @hayesdavis
[twitter-dev] Re: New Ruby Twitter API Library: Grackle
Thanks, Hayes. Added to http://apiwiki.twitter.com/Libraries On Mon, Apr 13, 2009 at 09:19, Hayes Davis ha...@appozite.com wrote: Hi all, Just wanted to let everyone know that I've released a new Ruby Twitter API library called Grackle. It's at http://github.com/hayesdavis/grackle It works with both the search and REST APIs and supports both basic and OAuth authentication. The main thing that sets it apart is that it's designed to be resilient in the face of changes to the API. Everything's dynamic, so new API methods, changes to parameters or modifications to returned data don't require changes to the library itself. That has been quite helpful in my projects (and others that use it as well) as the guys move forward very quickly with new API functionality. Would it be possible to have it included among the available libraries on the wiki? Please let me know if you have any feedback, suggestions for improvement, etc. Thanks. Hayes Davis @hayesdavis -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: Limit for following new people (per hour)?
On Mon, Apr 13, 2009 at 7:15 AM, Madu7 mw...@web.de wrote: OK, thank you. Does the limit exist even if you are on the whitelist? But that's the general limit. I wonder if there's a limit per hour. For example: You are allowed to create 50 friendships per 60 minutes time period. If you reach the limit after 30 minutes, you have to wait for 30 minutes to create the next ones. Is there such a limit? The new page Matt cited will tell you all the answers... great to have that available! 100 API calls per hour (unless you are white-listed) is the constraint for the situation you described, unless you hit the 2,000 limit and don't have 2,000 followers. In that case, you have to wait no more than 1 hour to execute the next successful API call. If you are white-listed, the limit is 20,000 an hour, but that is moot for most of us and 2,000 becomes the practical constraint. If you aren't white-listed and have only one client hitting the API, it should be easy to figure out when you'll be able to make requests again. With multiple clients contributing to the limit, I never could figure out a way they could independently estimate when the limit would expire, but I stopped trying when my app was white-listed. Nick
[twitter-dev] Re: Limit for following new people (per hour)?
Please refer to the link Matt included to understand the following limit policy. Whitelisting allows access to more API calls. It does not affect follower limits. The follower limits are in place to promote healthy following behavior. Twitter wants users to follow people they are interested in. High levels of churn in the users that you are following are indicative of possible spam usage and will be flagged. It is a waste of time to develop tools to allow users to mass follow users serially. It is easy to detect and will lead to a suspended account. Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 7:15 AM, Madu7 mw...@web.de wrote: OK, thank you. Does the limit exist even if you are on the whitelist? But that's the general limit. I wonder if there's a limit per hour. For example: You are allowed to create 50 friendships per 60 minutes time period. If you reach the limit after 30 minutes, you have to wait for 30 minutes to create the next ones. Is there such a limit? On 13 Apr., 04:07, Nick Arnett nick.arn...@gmail.com wrote: I believe there is a limit of 2000 until 2000 people are following you, then it increases. Nick On 4/12/09, Madu7 mw...@web.de wrote: I am on the whitelist for the Twitter API and use the friendships/ create method to follow new people. But now I cannot follow a user any more. So is there a limit which controls how many users you can follow (per hour/day...)? I hope you can help me. Thanks in advance!
[twitter-dev] Re: Is there a way to tell if a tweet has been favorited (regardless of user)?
Ed, I'd love to see some apps crop up that display favorite content in interested ways. Can you create an issue? Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 8:50 AM, e.p.c. epcoste...@gmail.com wrote: I am playing with favorites and am trying to determine if a given tweet has been favorited by anyone at all. That is, given this tweet: https://twitter.com/epc/status/1500168995 which I’ve favorited with another account (@artificllc), is there a way to determine that it's been favorited, either by the author of the tweet (@epc) or by any other authenticated user? My checks with the API seem to indicate that @artificllc will get favoritedtrue/favorited when retrieving that tweet, but @epc and any other id will receive favoritedfalse/favorited. The API seems geared to showing what tweets a given user has marked as favorites, but there doesn't appear to be a way to see which of a user's tweets have been marked as favorites by others. Should I open an issue? -- -ed costello @epc
[twitter-dev] Re: Is there a way to tell if a tweet has been favorited (regardless of user)?
On Mon, Apr 13, 2009 at 10:50 AM, e.p.c. epcoste...@gmail.com wrote: I am playing with favorites and am trying to determine if a given tweet has been favorited by anyone at all. Yeah, the API could be a more helpful in that regard. Here are some services I've seen related to this subject if you want to check them out. http://favrd.textism.com/ http://favotter.matope.com/en/ http://twitfave.com/ (and I think they recently said they are offering an API) -damon -- http://twitter.com/damon
[twitter-dev] Re: Search queries not working
Yes. Queries are limited to 140 characters. Basha Shaik wrote: Hi, Is there any Length Limit in the query I pass in search API? Regards, Mahaboob Basha Shaik www.netelixir.com http://www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 10:27 AM, Basha Shaik basha.neteli...@gmail.com mailto:basha.neteli...@gmail.com wrote: Hi Chad, No duplicates are there with this. Thank You Regards, Mahaboob Basha Shaik www.netelixir.com http://www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 7:29 AM, Basha Shaik basha.neteli...@gmail.com mailto:basha.neteli...@gmail.com wrote: Hi chad, Thank you. I was trying for a query which has only 55 tweets and i have kept 100 as rpp . so i was not getting next_page. when i decreased rpp to 20 and tried i got now. thank you very much. i Will check if any Duplicates occur with these and let you know. Regards, Mahaboob Basha Shaik www.netelixir.com http://www.netelixir.com Making Search Work On Sat, Apr 4, 2009 at 7:06 AM, Chad Etzel jazzyc...@gmail.com mailto:jazzyc...@gmail.com wrote: next_page -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
[twitter-dev] Re: autenticating user using OAuth
On Mon, Apr 13, 2009 at 2:59 AM, Zachary Voase disturb...@googlemail.com wrote: As far as I know this is not an issue. Users only have to accept the first time they use an application; on subsequent authorization requests, Twitter will redirect them to your app straight away. This is not correct (at least not right now). I think twitter is working on something that will act this way, but as of this minute you go through the Accept/Deny step every time you authenticate with an app. This would explain the behavior that Hameedullah is seeing. -Chad
[twitter-dev] Re: autenticating user using OAuth
Where are you storing the secret upon authorization? Is it going into persistent storage (such as a database) for future use? Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 11:07 AM, Hameedullah Khan hameed.u.k...@gmail.comwrote: On Apr 13, 11:59 am, Zachary Voase disturb...@googlemail.com wrote: As far as I know this is not an issue. Users only have to accept the first time they use an application; on subsequent authorization requests, Twitter will redirect them to your app straight away. Strange, I always get that Accept/Deny Page. I am wondering what I am missing. Here is what I am doing: 1. request a token from twitter. 2. Redirect user to authorization url with the token requested in 1 3. once the user returns from twitter, get the access token (or secret) from twitter based on token requested in 1. 4. use the secret for further api requests to twitter. Thanks, Hameedullah Khan
[twitter-dev] Re: autenticating user using OAuth
On Apr 13, 11:59 am, Zachary Voase disturb...@googlemail.com wrote: As far as I know this is not an issue. Users only have to accept the first time they use an application; on subsequent authorization requests, Twitter will redirect them to your app straight away. Strange, I always get that Accept/Deny Page. I am wondering what I am missing. Here is what I am doing: 1. request a token from twitter. 2. Redirect user to authorization url with the token requested in 1 3. once the user returns from twitter, get the access token (or secret) from twitter based on token requested in 1. 4. use the secret for further api requests to twitter. Thanks, Hameedullah Khan
[twitter-dev] Re: autenticating user using OAuth
Hi Hameedullah, It is currently the case that you will get the Accept/Deny page every time. We're working on a redirect like Zachary mentioned and hope to have it out by the end of the week. Thanks; — Matt Sanford / @mzsanford On Apr 13, 2009, at 11:07 AM, Hameedullah Khan wrote: On Apr 13, 11:59 am, Zachary Voase disturb...@googlemail.com wrote: As far as I know this is not an issue. Users only have to accept the first time they use an application; on subsequent authorization requests, Twitter will redirect them to your app straight away. Strange, I always get that Accept/Deny Page. I am wondering what I am missing. Here is what I am doing: 1. request a token from twitter. 2. Redirect user to authorization url with the token requested in 1 3. once the user returns from twitter, get the access token (or secret) from twitter based on token requested in 1. 4. use the secret for further api requests to twitter. Thanks, Hameedullah Khan
[twitter-dev] Re: Is there a way to tell if a tweet has been favorited (regardless of user)?
On Mon, Apr 13, 2009 at 1:41 PM, Doug Williams d...@twitter.com wrote: Ed, I'd love to see some apps crop up that display favorite content in interested ways. Can you create an issue? I’ve opened issue 459: http://code.google.com/p/twitter-api/issues/detail?id=459#c0 -- -ed costello
[twitter-dev] Re: autenticating user using OAuth
Store the access token and access token secret in a database with all of the other info concerning a user, then request it when they log in and maybe store it in cookies or something. - Original Message - From: Hameedullah Khan hameed.u.k...@gmail.com To: Twitter Development Talk twitter-development-talk@googlegroups.com Sent: Sunday, April 12, 2009 12:08 PM Subject: [twitter-dev] autenticating user using OAuth Hello Twitterers, I have been building my application and everything is working fine, just I am stuck on one thing. What is the correct way to authenticate user when they come back to my site for using my application, I want to authenticate them and using Oauth, but if I Request a toaken and send them to authorization URL they have to click on the Accept button, this is okay for the first time, but if they will have to do that everytime they login to my application this will not be good. May be I am missing something, so if someone can guide me I would really appreciate it. Thanks, Hameedullah Khan.
[twitter-dev] Request for documentation review
Coderz, I am refactoring the API documentation [1] to make it friendlier on the eyes and easier on new developers. Please give it a once over and reply with any of errors, addition requests, or suggestions. We will be using these new docs officially in a few days (linked from the apiwiki.twitter.com) once any glaring omissions and/or errors are addressed. My goal is to make the documentation more robust and example laden to help new developers get going without needing help. Suggestions and critism along those lines is welcome. A final plea for help: If you have some spare time and examples to borrow from, please send a...@twitter.com any code/instructions that I can then paste into method body to help new devs get started. Basic Hello World! style usage examples for each method would go a long way to curbing new developer problems. Be sure to include a link to any libraries your example is using. Working full length example code hosted on github would be preferred. 1. http://apiwiki.twitter.com/Twitter-API-Documentation Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: [twitter-api-announce] A note on our API change policy
Another point. If you are fundamentally agile, you should have stories and iterations. What if you posted current breaking change stories at the start of the iteration before you started them. Assuming a 1 or 2 week iteration, we get time to comment, and you won't have to hold code back. JD On Sat, Apr 11, 2009 at 1:19 PM, Abraham Williams 4bra...@gmail.com wrote: If versioning is used how long should versions be supported? A week? A month? Lets just say a month for now. If Twitter pushes out changes every 2 days it is possible that there would be 15 versions running at any given time. This is an extreme example but something to think about. On Sat, Apr 11, 2009 at 13:56, Alex Payne a...@twitter.com wrote: Right now, every new machine we get goes immediately into production. Once we have enough machines that we can get ahead of that capacity planning, I think a beta.api.twitter.com is a great idea. And/or versioning. On Sat, Apr 11, 2009 at 11:00, Yu-Shan Fung ambivale...@gmail.com wrote: I second Jesse's suggestion. Having a staging server to test out API changes would help smooth out transitions (though people needs to be careful about what change they make as presumably this will run against prod database). That way your internal developers can directly push code ready for release immediately to staging instead of waiting 5 days. It'll probably also help sanity internally at Twitter. Who knows, with developers hitting the staging API before it goes out, we might even help catch a bug or two once in a while before it goes out :-) Yu-Shan On Sat, Apr 11, 2009 at 2:21 AM, Jesse Stay jesses...@gmail.com wrote: Doug, can you guys do what Facebook is doing, and release it on a beta server somewhere beforehand so we can test it on our apps before you actually release it to the public? A public staging server of some sort. That will keep these surprises from happening, and we can start working out alerts to have in place when things might break our code that go on that beta server. Best of all, it won't ever affect the end user. Keep the releases on that server, then the releases out to the public on a timed release schedule. It might take a little longer to get out to the public, but you'll have a much happier developer base and in turn a much happier end user by doing so. That would be my number one suggestion. Do you guys do any tracking of Twitter itself for developers complaining about the API? I would also think you could gain some insight from that as well. @Jesse On Fri, Apr 10, 2009 at 12:04 PM, Doug Williams d...@twitter.com wrote: Twitter's development model is pragmatically agile where features enter the code base right alongside bug fixes. You can see this in our changelog [1]. What is not clear from the log is that most of the code is written just days before. April 8th's rapid deprecation of the since parameter/If-Modified-Since header (and to a lesser extent, the removal of undocumented HTTP POST access to accounts/verify_credentials) [5] caught a number of developers off guard. The criticism of this hasty change on the impact to hackers and businesses alike was both valid and appropriate. The results from last month's survey [6] lead us to believe that the use of this parameter was minimal and that it was safe to capture performance gains through the deprecation. In hindsight, our sample size was statistically insignificant because we made a mistake. It is apparent we need to make a change towards transparency. Openness demands we give developers a clear line of communication when changes are made that will break current functionality. While these changes are rare, they do happen. As a result of this week's conversation, we will give a minimum of 5 business days notice before we ship code that removes currently documented functionality. Two notable exceptions are critical security and performance fixes. Five days may seem short notice but it is a compromise from our standard. There are two major concerns we must consider when shelving code that is ready for deploy: 1) We do not write unnecessary code. Code only exists in the deploy pipeline for a feature or defect fix that is ready to go out the door. We view deployable code as an asset that should be handling requests as quickly as possible. 2) Un-merged code adds complexity. The Twitter code base is constantly moving. Deploying code requires merging with the master branch which grows in complexity as an undeployed branch sits idle. We currently use the changelog [1], @twitterapi [2], The API Announce List [3], and the Dev Group [4] to inform developers of changes in hopes that features will get used, and deprecations will be honored. I'd suggest any developer with a long-running application to subscribe to the low noise, only signal, API
[twitter-dev] Combination of search operators returns 404
This query contains two documented search operators, and it bombs with a 404 if they're called together, but works if called separately. Previous unit tests allowed multiple operators. Is 404 the correct response for no results? It returns as HTML. http://search.twitter.com/search.json?q=twitter until:2009-01-04 filter:links
[twitter-dev] Re: Freelance Twitter API Dev directory?
Alex, If you could please add my details to the list of Twitter API Developers: Name: Rahul Jhaveri Twitter: http://twitter.com/contd Website: http://www.twittercontd.com Email: i...@twittercontd.com Many thanks, Rahul On Apr 8, 10:05 pm, peterhough em...@peterhough.co.uk wrote: Alex, If you could please add my details to the list of Twitter API Developers: Name: Peter Hough Twitter:http://twitter.com/peterhough Website:http://www.peterhough.co.uk Email:http://scr.im/peterhough Portfolio:http://twitrand.com Many thanks, Pete On Feb 23, 7:33 pm, Alex Payne a...@twitter.com wrote: There isn't one that I'm aware of, but if people would like to post their contact info in this thread (Twitter username, URL, email, whatever) I'm happy to collect them on the API Wiki. On Sat, Feb 21, 2009 at 18:00, Chad Etzel jazzyc...@gmail.com wrote: Hi All, I have been getting a few requests here and there for twitter API development work. I cannot take on any such projects at the moment, but I always feel bad for leaving them in the lurch. Is there a list or directory anywhere of Twitter API developers that work freelance that I can send to them when this happens? I'm happy to forward on such requests. -Chad -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Geocoding posts
How does Twitter GeoCode tweets OTHER than the users location (if at all)? I'd like to include short urls for geolocation, but want to understand how Twitter uses them. Thanks.
[twitter-dev] Re: [twitter-api-announce] A note on our API change policy
We're not strictly an Agile shop, actually, but thanks. On Mon, Apr 13, 2009 at 18:16, James Deville james.devi...@gmail.com wrote: Another point. If you are fundamentally agile, you should have stories and iterations. What if you posted current breaking change stories at the start of the iteration before you started them. Assuming a 1 or 2 week iteration, we get time to comment, and you won't have to hold code back. JD On Sat, Apr 11, 2009 at 1:19 PM, Abraham Williams 4bra...@gmail.com wrote: If versioning is used how long should versions be supported? A week? A month? Lets just say a month for now. If Twitter pushes out changes every 2 days it is possible that there would be 15 versions running at any given time. This is an extreme example but something to think about. On Sat, Apr 11, 2009 at 13:56, Alex Payne a...@twitter.com wrote: Right now, every new machine we get goes immediately into production. Once we have enough machines that we can get ahead of that capacity planning, I think a beta.api.twitter.com is a great idea. And/or versioning. On Sat, Apr 11, 2009 at 11:00, Yu-Shan Fung ambivale...@gmail.com wrote: I second Jesse's suggestion. Having a staging server to test out API changes would help smooth out transitions (though people needs to be careful about what change they make as presumably this will run against prod database). That way your internal developers can directly push code ready for release immediately to staging instead of waiting 5 days. It'll probably also help sanity internally at Twitter. Who knows, with developers hitting the staging API before it goes out, we might even help catch a bug or two once in a while before it goes out :-) Yu-Shan On Sat, Apr 11, 2009 at 2:21 AM, Jesse Stay jesses...@gmail.com wrote: Doug, can you guys do what Facebook is doing, and release it on a beta server somewhere beforehand so we can test it on our apps before you actually release it to the public? A public staging server of some sort. That will keep these surprises from happening, and we can start working out alerts to have in place when things might break our code that go on that beta server. Best of all, it won't ever affect the end user. Keep the releases on that server, then the releases out to the public on a timed release schedule. It might take a little longer to get out to the public, but you'll have a much happier developer base and in turn a much happier end user by doing so. That would be my number one suggestion. Do you guys do any tracking of Twitter itself for developers complaining about the API? I would also think you could gain some insight from that as well. @Jesse On Fri, Apr 10, 2009 at 12:04 PM, Doug Williams d...@twitter.com wrote: Twitter's development model is pragmatically agile where features enter the code base right alongside bug fixes. You can see this in our changelog [1]. What is not clear from the log is that most of the code is written just days before. April 8th's rapid deprecation of the since parameter/If-Modified-Since header (and to a lesser extent, the removal of undocumented HTTP POST access to accounts/verify_credentials) [5] caught a number of developers off guard. The criticism of this hasty change on the impact to hackers and businesses alike was both valid and appropriate. The results from last month's survey [6] lead us to believe that the use of this parameter was minimal and that it was safe to capture performance gains through the deprecation. In hindsight, our sample size was statistically insignificant because we made a mistake. It is apparent we need to make a change towards transparency. Openness demands we give developers a clear line of communication when changes are made that will break current functionality. While these changes are rare, they do happen. As a result of this week's conversation, we will give a minimum of 5 business days notice before we ship code that removes currently documented functionality. Two notable exceptions are critical security and performance fixes. Five days may seem short notice but it is a compromise from our standard. There are two major concerns we must consider when shelving code that is ready for deploy: 1) We do not write unnecessary code. Code only exists in the deploy pipeline for a feature or defect fix that is ready to go out the door. We view deployable code as an asset that should be handling requests as quickly as possible. 2) Un-merged code adds complexity. The Twitter code base is constantly moving. Deploying code requires merging with the master branch which grows in complexity as an undeployed branch sits idle. We currently use the changelog [1], @twitterapi [2], The API Announce List [3], and the Dev Group [4] to inform developers of changes in
[twitter-dev] Re: public_timeline, invalid profile_image?
Alex - seems to still be an issue. Any updates on when we might see a fix? On Mar 30, 12:49 pm, Alex Payne a...@twitter.com wrote: We're on this. Thanks for the reports. On Sun, Mar 29, 2009 at 18:27, Gary Zhao garyz...@gmail.com wrote: I'm seeing it too. 2009/3/29 Günter Grodotzki guen...@grodotzki.ph since some days I am always getting: http://static.twitter.com/images/default_profile_normal.png as profile-image from the user via public-timeline (Data-mining-feed). I checked the announcement-google-group + twitter.com/twitterapi (subscribed to feed anyway ;) ) but could not see any change. The site affected:www.geoheartbeat.com -- Gary http://twitter.com/garyzhao -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
