[twitter-dev] Re: Twitter user picture sizes
I'm still seeing this problem, any ETA on it being fixed?
[twitter-dev] API auto refresh question
I am trying to pull a hashtag feed into by page at http://governorblagojevich.com/blagojevich/. Currently you have to click on the link to tget the page to refresh. How do I automate that to load it when the page loads and refresh it every 30 seconds or so? Thanks in advance. Lennie -- Office: 847-548-4562 Mobile: 847-302-3985 Twitter: http://twitter.com/ljarratt Facebook: http://www.facebook.com/people/Lennie_Jarratt/1182350486 The necessity of the times, more than ever, calls for our utmost circumspection, deliberation, fortitude, and perseverance. - Samuel Adams
[twitter-dev] Basic Twitter / OAuth questions (.NET)
Hi, I've looked through the FAQ, archives and other websites, and haven't found anything that has helped on this, so apologies if I've just missed it! I'm building an application which needs to be able to set a user's status automatically, without that user needing to log in and approve it every time. I'm using a variation on the code at: http://www.voiceoftech.com/swhitley/?p=681 , and it's working - to an extent. A user can visit a page on my app http://www.mytwitterapp.com/twitter.aspx, be redirected to Twitter to approve the app, then be sent back to my app, to the page which now has the form: http://www.mytwitterapp.com/twitter.aspx?oauth_token=EQ8Mi7T2Xqi6y5Ka0d38AyyTG6dL7hFO5wdf2Bp9IDI I can then use that token to get the token secret and interact with Twitter (primarily setting a status update). However, if I try to use that token again, I get a (401) Unauthorized error. I thought that the oauth_token that gets returned from http://twitter.com/oauth/authorize was a token that I could store, and use to repeatedly access Twitter when needed. It seems that what I'm actually getting back is an Access Token. So, my questions are: 1. Does what I've written above make sense? 2. Is there a token I can store, and use to repeatedly access Twitter - and if so, how can I get that value? 3. Am I barking up the wrong tree entirely? 4. Anything else you think might be of help!! Many thanks in advance, Richard.
[twitter-dev] Sign in with Twitter added to EpiTwitter (PHP/OAuth)
Did a quick write up on using PHP to sign in to Twitter. Working Example: http://www.jaisenmathai.com/sign_in_with_twitter/ Blog Post: http://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-in-with-twitter-with-oauth/ Code/Documentation: http://wiki.github.com/jmathai/epicode/epitwitter
[twitter-dev] Re: API auto refresh question
2 options: 1) Write some javascript that will poll the search API and then dynamically update the page with new results. 2) Use something like http://tweetgrid.com/widget/ which is available to do exactly this sort of thing (disclaimer: I wrote this). It's a drop-in widget that auto-refreshes and is completely style-izable to your heart's content. -Chad On Thu, Apr 30, 2009 at 10:29 PM, Lennie Jarratt ljarr...@gmail.com wrote: I am trying to pull a hashtag feed into by page at http://governorblagojevich.com/blagojevich/. Currently you have to click on the link to tget the page to refresh. How do I automate that to load it when the page loads and refresh it every 30 seconds or so? Thanks in advance. Lennie -- Office: 847-548-4562 Mobile: 847-302-3985 Twitter: http://twitter.com/ljarratt Facebook: http://www.facebook.com/people/Lennie_Jarratt/1182350486 The necessity of the times, more than ever, calls for our utmost circumspection, deliberation, fortitude, and perseverance. - Samuel Adams
[twitter-dev] Re: Basic Twitter / OAuth questions (.NET)
To get the access token you need to call /oauth/access_token. That'll give you back tokens you can save and reuse. This is a good flow diagram: http://oauth.net/core/diagram.png On May 1, 4:46 am, Richard L richard.lockw...@gmail.com wrote: Hi, I've looked through the FAQ, archives and other websites, and haven't found anything that has helped on this, so apologies if I've just missed it! I'm building an application which needs to be able to set a user's status automatically, without that user needing to log in and approve it every time. I'm using a variation on the code at:http://www.voiceoftech.com/swhitley/?p=681 , and it's working - to an extent. A user can visit a page on my apphttp://www.mytwitterapp.com/twitter.aspx, be redirected to Twitter to approve the app, then be sent back to my app, to the page which now has the form:http://www.mytwitterapp.com/twitter.aspx?oauth_token=EQ8Mi7T2Xqi6y5Ka... I can then use that token to get the token secret and interact with Twitter (primarily setting a status update). However, if I try to use that token again, I get a (401) Unauthorized error. I thought that the oauth_token that gets returned fromhttp://twitter.com/oauth/authorizewas a token that I could store, and use to repeatedly access Twitter when needed. It seems that what I'm actually getting back is an Access Token. So, my questions are: 1. Does what I've written above make sense? 2. Is there a token I can store, and use to repeatedly access Twitter - and if so, how can I get that value? 3. Am I barking up the wrong tree entirely? 4. Anything else you think might be of help!! Many thanks in advance, Richard.
[twitter-dev] Searching with since_id and max_id
Hi all, I've noticed an increasing number of search API questions whose root cause has been the fact that since_id and max_id do not work together. I dug into our code and found the reason for this and it turns out to provide a pretty solid performance gain. I started to look at ways around this and there are none that I can implement at the moment. I did launch a few small changes yesterday to make this easier to spot: 1. The next_url (rel=next element in Atom results) should never contain since_id. This was working correctly in Atom results, but JSON was incorrectly including it. That erroneous since_id has been removed. 2. In both Atom and JSON we should warn you if we do something unexpected. If you search with since_id and there are more than one page of results you'll now get a warning (warning in JSON, twitter:warning in Atom) telling you since_id was removed for pagination. Everything is functionally the same, I've just added a warning to let you know when things like this happen. The main issue here is that since you cannot paginate with since_id you cannot set since_id and then paginate until there are no results. You need to search with since_id and then paginate if needed (via next_page or rel=next) until you reach a status = since_id. Thanks; — Matt Sanford / @mzsanford Twitter Dev
[twitter-dev] Re: OAuth and Classic ASP
Hi Robert, I'm also looking into this once I get my .NET version problems sorted out - will let you know how I get on! All the best, Richard. On May 1, 4:36 pm, Robert robertdd...@gmail.com wrote: I am looking for some example code that I can use with a Classic ASP legacy app. I am looking for a way to use oAuth with Classic ASP. Any help would be appreciated. Thanks in advance.
[twitter-dev] Wildcards in Search API
Is there a wildcard for search terms through the API? The 140char limit on the URL is playing havoc with something I'm trying to do and being able to shorten my search query using wildcards would help massively! I've searched the group and can't find an answer to this - although I suspect the lack of information gives me the answer I need...
[twitter-dev] Re: Wildcards in Search API
I'll let Matt chime in with the official answer, but I'm pretty sure it's no :( Also, substring matching/searches don't work either. -Chad On Fri, May 1, 2009 at 11:55 AM, hill79 hil...@googlemail.com wrote: Is there a wildcard for search terms through the API? The 140char limit on the URL is playing havoc with something I'm trying to do and being able to shorten my search query using wildcards would help massively! I've searched the group and can't find an answer to this - although I suspect the lack of information gives me the answer I need...
[twitter-dev] Re: Wildcards in Search API
Hi there, Nope, sorry to say we do not support wild cards. We've discussed it in the past internally but there is no good way to make it work fast enough to be useful based on our current system. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 1, 2009, at 8:55 AM, hill79 wrote: Is there a wildcard for search terms through the API? The 140char limit on the URL is playing havoc with something I'm trying to do and being able to shorten my search query using wildcards would help massively! I've searched the group and can't find an answer to this - although I suspect the lack of information gives me the answer I need...
[twitter-dev] Re: Wildcards in Search API
Insanely quick replies - thanks :) On May 1, 4:58 pm, Matt Sanford m...@twitter.com wrote: Hi there, Nope, sorry to say we do not support wild cards. We've discussed it in the past internally but there is no good way to make it work fast enough to be useful based on our current system. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 1, 2009, at 8:55 AM, hill79 wrote: Is there a wildcard for search terms through the API? The 140char limit on the URL is playing havoc with something I'm trying to do and being able to shorten my search query using wildcards would help massively! I've searched the group and can't find an answer to this - although I suspect the lack of information gives me the answer I need...
[twitter-dev] Re: Clarifications on IP Address Whitelisting
Thanks, Doug. What about IPv6 Whitelisting? I haven't tried it, yet, but curious if it works. -- Patrick Burrows http://www.CleverHumans.com On Wed, Apr 29, 2009 at 1:32 PM, Doug Williams d...@twitter.com wrote: Patrick, Yes. Each whitelisted IP address is allowed 2 requests per hour. I will clarify this point in the documentation. Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Wed, Apr 29, 2009 at 7:43 AM, P Burrows pburr...@gmail.com wrote: (s/b 100,000 total, not 120,000, my maths was broke.) -- Patrick Burrows http://www.CleverHumans.com On Wed, Apr 29, 2009 at 10:31 AM, P Burrows pburr...@gmail.com wrote: I apologize if this question has already been answered in the archives. I've followed this list for a couple days and hadn't seen this specific question come up. My application has been white listed. In doing so, I specified a set of 5 IP addresses from which traffic from my application may come. TFM states [1]: we offer whitelisting which will raise an account or IP address' rate limit to 2 requests per hour. My understanding is that this means each of my 5 IP Addresses can make 20,000 unique API requests per hour (for a total of 120,000 API requests / hr as long as I write some sort of IP Address load balancing code.) But I have not seen that actually spelled out in so many words. Is my assumption correct? (my app is nowhere near that limit, but I am working on some capacity planning numbers.) If my assumption is correct, is there a further limit on the number of unique addresses my Application can have whitelisted? Also, is whitelisting limited to IPv4? I have not yet tried it with any IPv6 addresses. [1] http://apiwiki.twitter.com/Rate-limiting?SearchFor=white+listsp=1 -- Patrick Burrows http://www.CleverHumans.com
[twitter-dev] Re: Clarifications on IP Address Whitelisting
Currently only whitelisting IPv4 addresses. Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Fri, May 1, 2009 at 9:16 AM, P Burrows pburr...@gmail.com wrote: Thanks, Doug. What about IPv6 Whitelisting? I haven't tried it, yet, but curious if it works. -- Patrick Burrows http://www.CleverHumans.com On Wed, Apr 29, 2009 at 1:32 PM, Doug Williams d...@twitter.com wrote: Patrick, Yes. Each whitelisted IP address is allowed 2 requests per hour. I will clarify this point in the documentation. Thanks, Doug Doug Williams | Platform Support | Twitter, Inc. 539 Bryant St. Suite 402, San Francisco, CA 94107 http://twitter.com/dougw On Wed, Apr 29, 2009 at 7:43 AM, P Burrows pburr...@gmail.com wrote: (s/b 100,000 total, not 120,000, my maths was broke.) -- Patrick Burrows http://www.CleverHumans.com On Wed, Apr 29, 2009 at 10:31 AM, P Burrows pburr...@gmail.com wrote: I apologize if this question has already been answered in the archives. I've followed this list for a couple days and hadn't seen this specific question come up. My application has been white listed. In doing so, I specified a set of 5 IP addresses from which traffic from my application may come. TFM states [1]: we offer whitelisting which will raise an account or IP address' rate limit to 2 requests per hour. My understanding is that this means each of my 5 IP Addresses can make 20,000 unique API requests per hour (for a total of 120,000 API requests / hr as long as I write some sort of IP Address load balancing code.) But I have not seen that actually spelled out in so many words. Is my assumption correct? (my app is nowhere near that limit, but I am working on some capacity planning numbers.) If my assumption is correct, is there a further limit on the number of unique addresses my Application can have whitelisted? Also, is whitelisting limited to IPv4? I have not yet tried it with any IPv6 addresses. [1] http://apiwiki.twitter.com/Rate-limiting?SearchFor=white+listsp=1 -- Patrick Burrows http://www.CleverHumans.com
[twitter-dev] Re: Sign in with Twitter added to EpiTwitter (PHP/OAuth)
Adding this to the wiki. Thanks for sharing! Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Fri, May 1, 2009 at 12:54 AM, jmathai jmat...@gmail.com wrote: Did a quick write up on using PHP to sign in to Twitter. Working Example: http://www.jaisenmathai.com/sign_in_with_twitter/ Blog Post: http://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-in-with-twitter-with-oauth/ Code/Documentationhttp://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-in-with-twitter-with-oauth/%0ACode/Documentation: http://wiki.github.com/jmathai/epicode/epitwitter
[twitter-dev] Re: Twitter user picture sizes
I've updated issue 497's status [1]. The avatar upload functionality sits within the core Twitter.com application. The results of this feature (avatars and images) are made available by the API. The image upload logic is currently being rewritten by a member of the core team. Unfortunately we do not have a definite time when this fix will ship. 1. http://code.google.com/p/twitter-api/issues/detail?id=497 Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Thu, Apr 30, 2009 at 7:08 PM, caseyw ap0s...@gmail.com wrote: I'm still seeing this problem, any ETA on it being fixed?
[twitter-dev] Re: Searching with since_id and max_id
Matt, this is exactly what I was getting ready to ask a question about. I hope I can implement the correct procedure with your information. Thank you. I do have a question though. If I paginate using next_page, is the next page only relevant to my search query? Meaning, if new posts find there way into the stream that meet my criteria, and I am asking for page two, will I only get items that were originally on page two from my original search? Or will page two now contain items that were originally on page one before. Not sure how the API handles this. Thanks for any clarification. --Thom On Fri, May 1, 2009 at 9:38 AM, Matt Sanford m...@twitter.com wrote: Hi all, I've noticed an increasing number of search API questions whose root cause has been the fact that since_id and max_id do not work together. I dug into our code and found the reason for this and it turns out to provide a pretty solid performance gain. I started to look at ways around this and there are none that I can implement at the moment. I did launch a few small changes yesterday to make this easier to spot: 1. The next_url (rel=next element in Atom results) should never contain since_id. This was working correctly in Atom results, but JSON was incorrectly including it. That erroneous since_id has been removed. 2. In both Atom and JSON we should warn you if we do something unexpected. If you search with since_id and there are more than one page of results you'll now get a warning (warning in JSON, twitter:warning in Atom) telling you since_id was removed for pagination. Everything is functionally the same, I've just added a warning to let you know when things like this happen. The main issue here is that since you cannot paginate with since_id you cannot set since_id and then paginate until there are no results. You need to search with since_id and then paginate if needed (via next_page or rel=next) until you reach a status = since_id. Thanks; — Matt Sanford / @mzsanford Twitter Dev
[twitter-dev] Re: Searching with since_id and max_id
Hi Thom, This is generally referred to as the 'moving window problem', and our next_page URL handles it. This is covered by using the max_id parameter so we are paginating from a fixed point and new matches don't throw off the pagination. To find matching tweets after your original page=1 query you need to re-query again from the beginning … and we include a refresh_url element (or rel=refresh in Atom) for reference. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 1, 2009, at 12:47 PM, Thom Allen wrote: Matt, this is exactly what I was getting ready to ask a question about. I hope I can implement the correct procedure with your information. Thank you. I do have a question though. If I paginate using next_page, is the next page only relevant to my search query? Meaning, if new posts find there way into the stream that meet my criteria, and I am asking for page two, will I only get items that were originally on page two from my original search? Or will page two now contain items that were originally on page one before. Not sure how the API handles this. Thanks for any clarification. --Thom On Fri, May 1, 2009 at 9:38 AM, Matt Sanford m...@twitter.com wrote: Hi all, I've noticed an increasing number of search API questions whose root cause has been the fact that since_id and max_id do not work together. I dug into our code and found the reason for this and it turns out to provide a pretty solid performance gain. I started to look at ways around this and there are none that I can implement at the moment. I did launch a few small changes yesterday to make this easier to spot: 1. The next_url (rel=next element in Atom results) should never contain since_id. This was working correctly in Atom results, but JSON was incorrectly including it. That erroneous since_id has been removed. 2. In both Atom and JSON we should warn you if we do something unexpected. If you search with since_id and there are more than one page of results you'll now get a warning (warning in JSON, twitter:warning in Atom) telling you since_id was removed for pagination. Everything is functionally the same, I've just added a warning to let you know when things like this happen. The main issue here is that since you cannot paginate with since_id you cannot set since_id and then paginate until there are no results. You need to search with since_id and then paginate if needed (via next_page or rel=next) until you reach a status = since_id. Thanks; — Matt Sanford / @mzsanford Twitter Dev
[twitter-dev] Re: Passing Parameters to Callback in OAuth
Thanks Matt. I'll try to handle it in my session for now. BTW, I think I've finally got Perl working - will be doing a post and transferring over to the wiki as soon as I feel comfortable with it. Jesse On Fri, May 1, 2009 at 3:12 PM, Matt Sanford m...@twitter.com wrote: Hi Jesse, This was available with the oauth_callback parameter but it had to be removed for security reasons. I'm currently working with the OAuth group to finalize a way to bring oauth_callback back. I have some working code based on the current discussion but we're still hashing some things out before it will be ready. Hopefully we'll be able to bring it back soon. I'll post and update to the list once I have something ready. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 1, 2009, at 2:09 PM, Jesse Stay wrote: Forgive my OAuth n00bness, but I was curious if there was a way to pass parameters that will in return get passed back to my callback URL in OAuth. For instance, I want to pass the parameters, and then when Twitter redirects back to my callback URL I want it to also pass the additional parameters so I can do different things with the same callback URL depending on what I'm trying to do with OAuth at the time. Is this possible? And how? Thanks, @Jesse
[twitter-dev] Passing Parameters to Callback in OAuth
Forgive my OAuth n00bness, but I was curious if there was a way to pass parameters that will in return get passed back to my callback URL in OAuth. For instance, I want to pass the parameters, and then when Twitter redirects back to my callback URL I want it to also pass the additional parameters so I can do different things with the same callback URL depending on what I'm trying to do with OAuth at the time. Is this possible? And how? Thanks, @Jesse
[twitter-dev] Re: Passing Parameters to Callback in OAuth
Hi Jesse, This was available with the oauth_callback parameter but it had to be removed for security reasons. I'm currently working with the OAuth group to finalize a way to bring oauth_callback back. I have some working code based on the current discussion but we're still hashing some things out before it will be ready. Hopefully we'll be able to bring it back soon. I'll post and update to the list once I have something ready. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 1, 2009, at 2:09 PM, Jesse Stay wrote: Forgive my OAuth n00bness, but I was curious if there was a way to pass parameters that will in return get passed back to my callback URL in OAuth. For instance, I want to pass the parameters, and then when Twitter redirects back to my callback URL I want it to also pass the additional parameters so I can do different things with the same callback URL depending on what I'm trying to do with OAuth at the time. Is this possible? And how? Thanks, @Jesse
