[twitter-dev] Re: User Search
no one knows what's wrong ? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Error: Operation could not be completed. (HTTP error 404.)
Hello I am getting this Error: Operation could not be completed. (HTTP error 404.) when using the /status/show.xml api. My url is like this- https://api.twitter.com/statuses/show/268146346.xml Can anybody pliz help me. Thanking you in advance. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: OAuth without read or write access
yes it would, I think people are more worried about the ability to write than read. You could just put up a message saying this is only being used for sign in and we will not read your stream. On Mar 20, 9:06 pm, Tom Gibara m...@tomgibara.com wrote: Searching for sign in with twitter pointed me to: http://dev.twitter.com/pages/sign_in_with_twitter which I've already read. My understanding is that my application must be registered to use OAuth, and that the access type it requires (read/write) is determined by that registration. Doesn't this mean that, at a minimum, the user will be informed that my application may read their tweets and account details? This won't be the case, and I don't want to give users that impression. Tom. On 20 March 2011 17:05, Ninjamonk dar...@stuartmedia.co.uk wrote: search for sign in with twitter and you should be ok. All you need to do is let them login with oauth and you will get those details. On Mar 20, 3:29 pm, tomgibara m...@tomgibara.com wrote: I'm developing an application in which I want to allow users to authenticate themselves with their twitter account. I need nothing more back from the authentication API than an ID that identifies the user; I don't want any access to any other account details or their tweets etc. In other words, I don't want read access. Is this possible? It seems not, because the application registration page offers only read or read/write. If this is the case, are there any plans to support an authenticate only option for applications? I did search this group for related threads but only found this post, which had no replies: http://groups.google.com/group/twitter-development-talk/browse_thread... -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Error: Operation could not be completed. (HTTP error 404.)
could u please describe your issue in detailed.. On Mon, Mar 21, 2011 at 3:50 PM, sangeeta katsange...@gmail.com wrote: Hello I am getting this Error: Operation could not be completed. (HTTP error 404.) when using the /status/show.xml api. My url is like this- https://api.twitter.com/statuses/show/268146346.xml Can anybody pliz help me. Thanking you in advance. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: OAuth without read or write access
Thanks for the confirmation. I guess I'll have to rely on informing the user as you suggest. It looks like a gap in the API to me, there must be plenty of websites out there that might want to confirm a user's identity with their twitter account, without wanting access to their tweets. Tom. On 21 March 2011 10:38, Ninjamonk dar...@stuartmedia.co.uk wrote: yes it would, I think people are more worried about the ability to write than read. You could just put up a message saying this is only being used for sign in and we will not read your stream. On Mar 20, 9:06 pm, Tom Gibara m...@tomgibara.com wrote: Searching for sign in with twitter pointed me to: http://dev.twitter.com/pages/sign_in_with_twitter which I've already read. My understanding is that my application must be registered to use OAuth, and that the access type it requires (read/write) is determined by that registration. Doesn't this mean that, at a minimum, the user will be informed that my application may read their tweets and account details? This won't be the case, and I don't want to give users that impression. Tom. On 20 March 2011 17:05, Ninjamonk dar...@stuartmedia.co.uk wrote: search for sign in with twitter and you should be ok. All you need to do is let them login with oauth and you will get those details. On Mar 20, 3:29 pm, tomgibara m...@tomgibara.com wrote: I'm developing an application in which I want to allow users to authenticate themselves with their twitter account. I need nothing more back from the authentication API than an ID that identifies the user; I don't want any access to any other account details or their tweets etc. In other words, I don't want read access. Is this possible? It seems not, because the application registration page offers only read or read/write. If this is the case, are there any plans to support an authenticate only option for applications? I did search this group for related threads but only found this post, which had no replies: http://groups.google.com/group/twitter-development-talk/browse_thread... -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] trends available in Malaysia?
Twitter supports topics trending only for 41 locations. list of locations available @ http://apiwiki.twitter.com/w/page/22554752/Twitter-REST-API-Method:-trends-available On Sun, Mar 13, 2011 at 9:45 PM, Jimmy Au ji...@mesixty.com wrote: The following lat long is in Malaysia but the return result is not in malaysia. I am wondering this service available in malaysia? http://api.twitter.com/1/trends/available.json?lat=3.144491long=101.711404 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Topics trending nearby!
I'm using http://api.twitter.com/1/trends/available.json to get the nearest
topic trending area, and getting the list of topics trending.
Now I need at least 1-2 tweets for each topic ?
How do get it ?
Do I need to call 10 API's 1 for each topic ?
Thank you.
-dev
On Tue, Feb 1, 2011 at 2:57 AM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Hi dev.at.twitter,
Yes, Local Trends are only available by one of the 42 currently supported
WOEIDs (including Worldwide/WOEID==1).
However, the GET http://api.twitter.com/1/trends/available.json method
will take a lat and long parameter set to return supported WOEIDs for a
location (see the end of this message for a brief summary on WOEIDs we have
trends for now).
Finally, the trends/:woeid call is meant to tell you what the current
trends are, not to provide the actual tweets that make up that trend. Each
trend in the array will have a name, a URL pointing to the
search.twitter.com WEB UI (which can easily be munged into a Search API
URL), and the actual query criteria that is considered part of the trend.
For finding WOEIDs for lat/longs that aren't necessarily reflected in
Trending Topics, look here: http://developer.yahoo.com/geo/geoplanet/
Summary on current local trends areas:
[
{
label:Ireland,
woeid:23424803
},
{
label:United Kingdom,
woeid:23424975
},
{
label:Mexico,
woeid:23424900
},
{
label:Boston,
woeid:2367105
},
{
label:Washington,
woeid:2514815
},
{
label:Miami,
woeid:2450022
},
{
label:Su00e3o Paulo,
woeid:455827
},
{
label:Baltimore,
woeid:2358820
},
{
label:India,
woeid:23424848
},
{
label:Worldwide,
woeid:1
},
{
label:Colombia,
woeid:23424787
},
{
label:Italy,
woeid:23424853
},
{
label:Detroit,
woeid:2391585
},
{
label:Argentina,
woeid:23424747
},
{
label:Netherlands,
woeid:23424909
},
{
label:New York,
woeid:2459115
},
{
label:Australia,
woeid:23424748
},
{
label:United States,
woeid:23424977
},
{
label:San Antonio,
woeid:2487796
},
{
label:France,
woeid:23424819
},
{
label:Chile,
woeid:23424782
},
{
label:Minneapolis,
woeid:2452078
},
{
label:Philadelphia,
woeid:2471217
},
{
label:Chicago,
woeid:2379574
},
{
label:Brazil,
woeid:23424768
},
{
label:Houston,
woeid:2424766
},
{
label:San Francisco,
woeid:2487956
},
{
label:Los Angeles,
woeid:2442047
},
{
label:Venezuela,
woeid:23424982
},
{
label:Canada,
woeid:23424775
},
{
label:Spain,
woeid:23424950
},
{
label:Sydney,
woeid:1105779
},
{
label:Singapore,
woeid:23424948
},
{
label:Atlanta,
woeid:2357024
},
{
label:Indonesia,
woeid:23424846
},
{
label:Germany,
woeid:23424829
},
{
label:Dallas-Ft. Worth,
woeid:2388929
},
{
label:Rio de Janeiro,
woeid:455825
},
{
label:London,
woeid:44418
},
{
label:Toronto,
woeid:4118
},
{
label:Turkey,
woeid:23424969
},
{
label:Seattle,
woeid:2490383
}
]
On Mon, Jan 31, 2011 at 9:21 AM, twitter dev dev.at.twit...@gmail.comwrote:
Hi Guys,
I've few questions on topics trending nearby,
1. Trends are based on WOEID. Can we get the twitter trends based on
lat/long geo-coords ?
2. If 1 is not possible then, what is the best way to get the accurate
WOEID for a lat/long geo-coords ?
3. I tried http://api.twitter.com/version/trends/:woeid.format , which
gives only the topic name and a link to that page. How do I get some
more info from this call ?
I'm stuck here now, guys help is much appreciated.
Thank you all,
-dev.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
[twitter-dev] Re: Error: Operation could not be completed. (HTTP error 404.)
Hello, Actually i tried with https://api.twitter.com/1/statuses/show/268146346.xml where 268146346 is one of my friend id even then i am getting the same 404 error(operation could not be completed) Pliz help me.. On Mar 21, 3:40 pm, Georgooty varghese georgo...@gmail.com wrote: could u please describe your issue in detailed.. On Mon, Mar 21, 2011 at 3:50 PM, sangeeta katsange...@gmail.com wrote: Hello I am getting this Error: Operation could not be completed. (HTTP error 404.) when using the /status/show.xml api. My url is like this- https://api.twitter.com/statuses/show/268146346.xml Can anybody pliz help me. Thanking you in advance. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: 401 unauthorized
Yup, totally stopped working for me as well and my scenario is the same as Joe's too. Any status updates on this issue? On Sun, Mar 20, 2011 at 2:09 PM, akiyoshi rafael.fuk...@gmail.com wrote: Well it stopped working for me as well. My scenario was the same as Joe Mayo's till yesterday. On 20 mar, 13:21, Ninjamonk dar...@stuartmedia.co.uk wrote: well it's stopped working completely now even if I pause. Can someone from twitter let us know the progress of this bug? On Mar 20, 3:28 pm, Joe Mayo mayos...@gmail.com wrote: I'm seeing the same problem with 401's during authentication. I have an app that has worked flawlessly (with no code changes) for months that is now receiving 401's. I'm also have multiple support issues on users experiencing intermittent 401 errors. For some apps, every authentication request results in a 401, but it seems to happen every other authentication for others. Joe On Mar 20, 9:10 am, Ninjamonk dar...@stuartmedia.co.uk wrote: I am still getting this issue and I think it's time related at twitters end. steps: 1. go to twitter and let user auth app 2. on return use verifier and token to ask twitter for the tokens and get a 401 Now if I pause step 2 before asking twitter for the tokens for 10 seconds it works fine. This code has worked for over 6 months and now I am getting this issue all of a sudden. I would look at my code but there are a lot of people getting the same issue. Cheers Darren On Mar 19, 6:05 pm, Matt Harris thematthar...@twitter.com wrote: Hi Trevor, Could you share the request and response you are sending so we can investigate. Remember to obscure user and consumer secrets. Thanks, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Sat, Mar 19, 2011 at 5:47 AM, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk-Hidequoted text - - Show quoted text -- Ocultar texto das mensagens anteriores - - Mostrar texto das mensagens anteriores - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Error: Operation could not be completed. (HTTP error 404.)
2011/3/21 sangeeta katsange...@gmail.com: Hello, Actually i tried with https://api.twitter.com/1/statuses/show/268146346.xml where 268146346 is one of my friend id even then i am getting the same 404 error(operation could not be completed) Pliz help me.. Hi, statuses/show? I can't find that API method in the docs. Do you mean? https://api.twitter.com/1/users/show/268146346.xml Cheers Christian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Error: Operation could not be completed. (HTTP error 404.)
This api is in tweet resources On Mar 21, 5:23 pm, CWorster cwors...@schlimmer.com wrote: 2011/3/21 sangeeta katsange...@gmail.com: Hello, Actually i tried with https://api.twitter.com/1/statuses/show/268146346.xml where 268146346 is one of my friend id even then i am getting the same 404 error(operation could not be completed) Pliz help me.. Hi, statuses/show? I can't find that API method in the docs. Do you mean?https://api.twitter.com/1/users/show/268146346.xml Cheers Christian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Search API rate limit change?
Taylor, Yeah this was definitely NOT good.In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, Zaver -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] changing 'Via' and using HTTPS
Dear Twitter Development Group, I have the following queries: 1. How can i change the via option. E.g. Want to use via 'x' operator 2. Is it possible to have an image (of 'x' operator) along with via 'x' operator message 3. Is it possible to use HTTPS rather than going for HTTP Regrads, Suresh sureshkumar1...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Need to integrate Twitter Authentication in my web application
Hi I am having a web application in .net (3.5) and SQL Server. I need to add twitter authentication in my application in which, user is authenticated at twitter with his username and password, and if authenticated, i will be able to get email, firstname and lastname of that twitter user. I have implemented facebook and google authentication (openId) in my web application Regards Manish -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401 unauthorized
I'm getting this same behaviour on http://ivebeen.to If I wait about 30 seconds before trying to convert the request token to an access token, it all works fine. This happens on both my local machine and on the deployed website - two distinct machines in different locations, timezones, etc. Both machines use network updated time from time.windows.com and I've manually triggered each of them to make sure their time is up to date. On Mar 21, 10:56 pm, Trevor Dean trevord...@gmail.com wrote: Yup, totally stopped working for me as well and my scenario is the same as Joe's too. Any status updates on this issue? On Sun, Mar 20, 2011 at 2:09 PM, akiyoshi rafael.fuk...@gmail.com wrote: Well it stopped working for me as well. My scenario was the same as Joe Mayo's till yesterday. On 20 mar, 13:21, Ninjamonk dar...@stuartmedia.co.uk wrote: well it's stopped working completely now even if I pause. Can someone from twitter let us know the progress of this bug? On Mar 20, 3:28 pm, Joe Mayo mayos...@gmail.com wrote: I'm seeing the same problem with 401's during authentication. I have an app that has worked flawlessly (with no code changes) for months that is now receiving 401's. I'm also have multiple support issues on users experiencing intermittent 401 errors. For some apps, every authentication request results in a 401, but it seems to happen every other authentication for others. Joe On Mar 20, 9:10 am, Ninjamonk dar...@stuartmedia.co.uk wrote: I am still getting this issue and I think it's time related at twitters end. steps: 1. go to twitter and let user auth app 2. on return use verifier and token to ask twitter for the tokens and get a 401 Now if I pause step 2 before asking twitter for the tokens for 10 seconds it works fine. This code has worked for over 6 months and now I am getting this issue all of a sudden. I would look at my code but there are a lot of people getting the same issue. Cheers Darren On Mar 19, 6:05 pm, Matt Harris thematthar...@twitter.com wrote: Hi Trevor, Could you share the request and response you are sending so we can investigate. Remember to obscure user and consumer secrets. Thanks, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Sat, Mar 19, 2011 at 5:47 AM, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk-Hidequotedtext - - Show quoted text -- Ocultar texto das mensagens anteriores - - Mostrar texto das mensagens anteriores - -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk- Hide quoted text - - Show quoted text - -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Custom URL Schemes on iphone with OAuth
After sending the user to safari to authorize, i get sent to mobile.twitter.com as opposed to my custom url scheme (something like myapp://). prior to authorizing, I did receive oauth_callback_confirmed=true. I've tried using a normal link like http://www.teamliquid.net, which works fine. Is there something I am missing? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401 unauthorized
Please go and star this issue: http://code.google.com/p/twitter-api/issues/detail?id=2118 On Mar 19, 11:47 pm, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Error: Operation could not be completed. (HTTP error 404.)
2011/3/21 sangeeta katsange...@gmail.com: This api is in tweet resources Of course, thanks. The parameter must be an ID of a status, not an users ID. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: 401 unauthorized
Thanks everyone for the detailed information in these reports; they'll help a lot while we track down the issue. Will update this thread when we know more. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 6:03 AM, Tatham Oddie tat...@oddie.com.au wrote: Please go and star this issue: http://code.google.com/p/twitter-api/issues/detail?id=2118 On Mar 19, 11:47 pm, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Error: Operation could not be completed. (HTTP error 404.)
Thankyou very much On Mar 21, 6:22 pm, CWorster cwors...@schlimmer.com wrote: 2011/3/21 sangeeta katsange...@gmail.com: This api is in tweet resources Of course, thanks. The parameter must be an ID of a status, not an users ID. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] In search of an honest developer who might be able to help me manifest my ideas
But would prefer to speak via direct email rather than in a forum. Basically, I would like to create an application that adds RPG elements (leveling up, accomplishments, avatar-personalization) to the twitter experience. An example, hopefully enough to form the idea in the readers head. User opens the app, fills out twitter info, and then sees an egg. With his/her first tweet a baby bird (sticking with twitter's theme) breaks free of the egg. After acquiring your first follower you are allowed to leave the nest. Later in game, if user is retweeted by justin bieber at some point while he/she is playing the game, his/her bird avatar can now be customized with justin bieber hair. If he/she gets x number of followers, her baby bird evolves into a more mature and cooler looking (customizable?) bird. Lots of possibilities. Hate justin bieber? I am not a fan either, but this app would target the largest audience possible. Please email at cwil...@umich.edu if you think you can help. Or if you can point me to someone who might be able to help i would also greatly appreciate it. Best - Chase -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: 401 unauthorized
If you're experiencing this issue, can you please provide these additional details: * are the OAuth URLs you are using http or https? * do your OAuth URLs contain the api subdomain? (you really should be if you aren't) * what OAuth library (if any) are you using to sign your requests? * If you're observing the response HTTP headers on failed requests, what server time is presented in the Date HTTP header? What is your OAuth timestamp? Thanks! @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 6:24 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks everyone for the detailed information in these reports; they'll help a lot while we track down the issue. Will update this thread when we know more. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 6:03 AM, Tatham Oddie tat...@oddie.com.au wrote: Please go and star this issue: http://code.google.com/p/twitter-api/issues/detail?id=2118 On Mar 19, 11:47 pm, Trevor Dean trevord...@gmail.com wrote: Is anyone else experiencing any 401 errors all of a sudden? I was doing some testing this morning and was logging in fine using twitter and then 10 min later I started getting 401 unauthorized errors. Thanks, Trevor -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
RE: [twitter-dev] Re: 401 unauthorized
Hi Taylor, I’m using the TweetSharphttp://tweetsharp.codeplex.com/ library. Here are my requests… Getting the request token works: UTC now: 21/03/2011 2:15:44 PM https://api.twitter.com/oauth/request_token GET /oauth/request_token HTTP/1.1 Authorization: OAuth oauth_callback=...,oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300716944,oauth_version=1.0 User-Agent: TweetSharp Host: api.twitter.com Connection: Keep-Alive 200 OK X-Transaction: 1300716948-77667-49892 X-Runtime: 0.00938 Pragma: no-cache X-Revision: DEV Content-Length: 144 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: text/html; charset=utf-8 Date: Mon, 21 Mar 2011 14:15:48 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT ETag: 00fdd191cfa579128843a85a7a58be9f Last-Modified: Mon, 21 Mar 2011 14:15:48 GMT Set-Cookie: k=124.169.147.184; path=/; expires=Mon, 28-Mar-11 14:15:48 GMT; domain=.twitter.com,guest_id=...; path=/; expires=Wed, 20 Apr 2011 14:15:48 GMT,admobuu=...; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan 2038 03:14:07 GMT,_twitter_sess=...; domain=.twitter.com; path=/; HttpOnly Server: hi Vary: Accept-Encoding Keep-Alive: timeout=15, max=100 Connection: Keep-Alive oauth_token=...oauth_token_secret=...oauth_callback_confirmed=true Getting the access token straight away fails with 401: UTC now: 21/03/2011 2:15:46 PM https://api.twitter.com/oauth/access_token POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300716946,oauth_token=...,oauth_verifier=...,oauth_version=1.0 Content-Type: application/x-www-form-urlencoded User-Agent: TweetSharp Host: api.twitter.com Content-Length: 0 401 Unauthorized X-Transaction: 1300716950-90707-10498 X-Runtime: 0.00684 Pragma: no-cache X-Revision: DEV Content-Length: 1 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: text/html; charset=utf-8 Date: Mon, 21 Mar 2011 14:15:50 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT Last-Modified: Mon, 21 Mar 2011 14:15:50 GMT Set-Cookie: k=124.169.147.184; path=/; expires=Mon, 28-Mar-11 14:15:50 GMT; domain=.twitter.com,guest_id=...; path=/; expires=Wed, 20 Apr 2011 14:15:50 GMT,admobuu=...; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan 2038 03:14:07 GMT,_twitter_sess=...; domain=.twitter.com; path=/; HttpOnly Server: hi Vary: Accept-Encoding Trying the same request again 10 minutes later works (only oauth_timestamp changed): UTC now: 21/03/2011 2:25:42 PM https://api.twitter.com/oauth/access_token POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300717542,oauth_token=...,oauth_verifier=...,oauth_version=1.0 Content-Type: application/x-www-form-urlencoded User-Agent: TweetSharp Host: api.twitter.com Content-Length: 0 Connection: Keep-Alive 200 OK X-Transaction: 1300717546-72934-39621 X-Runtime: 0.03056 Pragma: no-cache X-Revision: DEV Content-Length: 163 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Content-Type: text/html; charset=utf-8 Date: Mon, 21 Mar 2011 14:25:46 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT ETag: 9ac6161371b0ee90ef8f6db5322287df Last-Modified: Mon, 21 Mar 2011 14:25:46 GMT Set-Cookie: k=124.169.147.184.1300717546945450; path=/; expires=Mon, 28-Mar-11 14:25:46 GMT; domain=.twitter.com,guest_id=130071754695116305; path=/; expires=Wed, 20 Apr 2011 14:25:46 GMT,admobuu=989196f7fa5728c90e815cc8f97cd56a; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan 2038 03:14:07 GMT,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCMitztguAToHaWQiJTk4NDllMmVhZTM1OTJk%250ANzQ0MGFlMWM2YzQ1ZTU2MDg4IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--dad7912a647454357cfa6f0d07804b5c4b5d6ae4; domain=.twitter.com; path=/; HttpOnly Server: hi Vary: Accept-Encoding Keep-Alive: timeout=15, max=100 Connection: Keep-Alive oauth_token=...oauth_token_secret=...user_id=14051560screen_name=tathamoddie I’m noting that the time offset here is only about 4 seconds, however it certainly takes longer than that to work. You can see this for yourself trying to sign in to http://ivebeen.to -- Tatham Oddie au mob: +61 414 275 989, us cell: +1 213 280 3556, skype: tathamoddie If you’re printing this email, you’re doing it wrong. This is a computer, not a typewriter. From: Taylor Singletary [mailto:taylorsinglet...@twitter.com] Sent: Tuesday, 22 March 2011 1:05 AM To: twitter-development-talk@googlegroups.com Cc: Tatham Oddie Subject: Re: [twitter-dev] Re: 401 unauthorized If you're experiencing this issue, can you please provide these additional details: * are the OAuth URLs you are using http or https? * do your OAuth URLs contain the api subdomain? (you really should be if you aren't) * what OAuth library
[twitter-dev] Re: Search API rate limit change?
By adjusting the rate limits to reduce the stress on your search api without notice you have significantly increased the stress level on our end :P Seriously, advanced notice of the situation would have been welcome. In particular what created lots of confusion on our end is that even after pausing for the specified retry_after delay we would immediately get repeated 420s at which point we started to assume our IPs were banned (which also contributed to increase the stress level). Colin On Mar 21, 9:12 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Taylor, Yeah this was definitely NOT good. In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, Zaver -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401 unauthorized
Ok, here's what I've got so far in my development machine:
All requests to: https://api.twitter.com/oauth/
I'm using Twitterizer OAuth library.
All testing was done trying to authenticate the same user.
Request Token - Access Token response headers:
Local Machine Time: 21/03/2011 - 11:24 a.m (-3 São Paulo, Brazil)
{Status: 401 Unauthorized
X-Transaction: 1300717410-27747-18545
X-Runtime: 0.00612
Pragma: no-cache
X-Revision: DEV
Content-Length: 1
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Content-Type: text/html; charset=utf-8
Date: Mon, 21 Mar 2011 14:23:30 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Last-Modified: Mon, 21 Mar 2011 14:23:30 GMT
Set-Cookie: k=186.204.24.164.1300717410112809; path=/; expires=Mon, 28-
Mar-11 14:23:30 GMT; domain=.twitter.com,guest_id=130071741011897398;
path=/; expires=Wed, 20 Apr 2011 14:23:30
GMT,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCEeXzNguAToHaWQiJWY0YWJkOTg5MzA5N2Jk
%250ANmU2MjRlN2Q4OTY4ZDVlOGE3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--5f19c3e4b79f1e24195a532adf988bc5764dc878;
domain=.twitter.com; path=/; HttpOnly
Server: hi
Vary: Accept-Encoding
}
Local Machine Time: 21/03/2011 - 11:26 a.m (-3 São Paulo, Brazil)
{Status: 401 Unauthorized
X-Transaction: 1300717553-71682-48532
X-Runtime: 0.00788
Pragma: no-cache
X-Revision: DEV
Content-Length: 1
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Content-Type: text/html; charset=utf-8
Date: Mon, 21 Mar 2011 14:25:54 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Last-Modified: Mon, 21 Mar 2011 14:25:53 GMT
Set-Cookie: k=186.204.24.164.1300717553990342; path=/; expires=Mon, 28-
Mar-11 14:25:53 GMT; domain=.twitter.com,guest_id=130071755399831650;
path=/; expires=Wed, 20 Apr 2011 14:25:53
GMT,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCE
%252FJztguAToHaWQiJWMwNjU4N2ZjMzU1Zjkw
%250AOTYxNzZiODcyNjRhNjU1YTIxIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--475d60acc3baee4151254364e9ffddb0ed8a4e76;
domain=.twitter.com; path=/; HttpOnly
Server: hi
Vary: Accept-Encoding
}
Successful response:
Achieved by waiting some seconds between requesting and reading the
response when getting the RequestToken.
Local Machine Time: 21/03/2011 - 11:49 a.m (-3 São Paulo, Brazil)
{Status: 200 OK
X-Transaction: 1300718905-61910-2260
X-Runtime: 0.02514
Pragma: no-cache
X-Revision: DEV
Content-Length: 170
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Content-Type: text/html; charset=utf-8
Date: Mon, 21 Mar 2011 14:48:25 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
ETag: 82276158764a17db3bb7fd96d46eb377
Last-Modified: Mon, 21 Mar 2011 14:48:25 GMT
Set-Cookie: k=186.204.24.164.1300718905898781; path=/; expires=Mon, 28-
Mar-11 14:48:25 GMT; domain=.twitter.com,guest_id=130071890590494715;
path=/; expires=Wed, 20 Apr 2011 14:48:25
GMT,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCDBq49guAToHaWQiJWRiMzgxYWFhOTFmMjVl
%250AODI3NDI5NmFjZjI0ZmMyYzgyIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
c2deb47c8c0545588cb18f77aa3516546f350e26; domain=.twitter.com; path=/;
HttpOnly
Server: hi
Vary: Accept-Encoding
}
On Mar 21, 11:30 am, Tatham Oddie tat...@oddie.com.au wrote:
Hi Taylor,
I’m using the TweetSharphttp://tweetsharp.codeplex.com/ library.
Here are my requests…
Getting the request token works:
UTC now: 21/03/2011 2:15:44 PM
https://api.twitter.com/oauth/request_token
GET /oauth/request_token HTTP/1.1
Authorization: OAuth
oauth_callback=...,oauth_consumer_key=...,oauth_nonce=...,oauth_signa
ture=...,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1300716944,
oauth_version=1.0
User-Agent: TweetSharp
Host: api.twitter.com
Connection: Keep-Alive
200 OK
X-Transaction: 1300716948-77667-49892
X-Runtime: 0.00938
Pragma: no-cache
X-Revision: DEV
Content-Length: 144
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Content-Type: text/html; charset=utf-8
Date: Mon, 21 Mar 2011 14:15:48 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
ETag: 00fdd191cfa579128843a85a7a58be9f
Last-Modified: Mon, 21 Mar 2011 14:15:48 GMT
Set-Cookie: k=124.169.147.184; path=/; expires=Mon, 28-Mar-11 14:15:48
GMT; domain=.twitter.com,guest_id=...; path=/; expires=Wed, 20 Apr 2011
14:15:48 GMT,admobuu=...; domain=.m.twitter.com; path=/; expires=Tue, 19 Jan
2038 03:14:07 GMT,_twitter_sess=...; domain=.twitter.com; path=/; HttpOnly
Server: hi
Vary: Accept-Encoding
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
oauth_token=...oauth_token_secret=...oauth_callback_confirmed=true
Getting the access token straight away fails with 401:
UTC now: 21/03/2011 2:15:46 PM
https://api.twitter.com/oauth/access_token
POST /oauth/access_token HTTP/1.1
Authorization: OAuth
oauth_consumer_key=...,oauth_nonce=...,oauth_signature=...,oauth_sign
ature_method=HMAC-SHA1,oauth_timestamp=1300716946,oauth_token=...,oau
[twitter-dev] hyphens at the end of shortned urls
I work for AWeber Communications in Huntingdon Valley PA. We provide email marketing solutions for small to medium sized businesses and have 100,000+ active customers. We utilize the Twitter API to allow a customer to automatically post status updates to their twitter account when they send out a mailing. The urls in the status updates sometimes end with a hyphen. Up until recently, these have been auto-linked correctly by twitter. Recently this changed, and the hyphens at the end of the link are not included in the links I post to the API. For example, http://aweber.com/b/os7- would have linked correctly before, but now links to http://aweber.com/b/os7 instead. Is this a bug or a permanent change at Twitter? Is there a way to explicitly define the links that get picked up, display_url maybe? I see that complete urls and start / end points are included in the entities: urls section of a tweet, but it is not clear if I am able to _submit_ the entities section for my own posts. Any help is appreciated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Search API: Can the geocode param only give me lat/long results?
Hi, I have a pre-question before my question. With the search API's geocode based search, if it falls back on the user's profile information does it use GPS positions in their profile or some location such as 'London'. The problem is that I need much greater precision than that. Thus, if I perform this search: http://search.twitter.com/search.json?geocode=51.53,-0.14,1mi Am I able to get results back that only contain lat/long values of the tweet? The json returned here has basically no values for 'geo'. Thanks S. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] hyphens at the end of shortned urls
Hi there, We'll look into this issue; I'm unsure if the non-linkifying of URLs ending with a dash was intentional or not, but likely was not. To answer your latter question, tweet entities cannot be written to/suggested at time of tweet creation unfortunately. Thanks, Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 8:08 AM, roliver roliv...@gmail.com wrote: I work for AWeber Communications in Huntingdon Valley PA. We provide email marketing solutions for small to medium sized businesses and have 100,000+ active customers. We utilize the Twitter API to allow a customer to automatically post status updates to their twitter account when they send out a mailing. The urls in the status updates sometimes end with a hyphen. Up until recently, these have been auto-linked correctly by twitter. Recently this changed, and the hyphens at the end of the link are not included in the links I post to the API. For example, http://aweber.com/b/os7- would have linked correctly before, but now links to http://aweber.com/b/os7 instead. Is this a bug or a permanent change at Twitter? Is there a way to explicitly define the links that get picked up, display_url maybe? I see that complete urls and start / end points are included in the entities: urls section of a tweet, but it is not clear if I am able to _submit_ the entities section for my own posts. Any help is appreciated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Need to integrate Twitter Authentication in my web application
Hi Manish, As far as I know, the Twitter API does not provide any method to get the user's email, and as far as first and last name you will have to rely on the name field of the user entity. This may or (more likely) may not contain the information you are looking for. You can see a list of the fields contained in a user entity at : http://dev.twitter.com/doc/get/users/lookup Basically, if you need to those data, you are going to have the user for them yourself in your application. hax0rsteve On 21 Mar 2011, at 09:34, Manish Sadhwani wrote: Hi I am having a web application in .net (3.5) and SQL Server. I need to add twitter authentication in my application in which, user is authenticated at twitter with his username and password, and if authenticated, i will be able to get email, firstname and lastname of that twitter user. I have implemented facebook and google authentication (openId) in my web application Regards Manish -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Need to integrate Twitter Authentication in my web application
Sorry, that should have read : you are going to have to ask the user for them yourself in your application. On 21 Mar 2011, at 15:48, hax0rsteve wrote: you are going to have the user for them yourself in your application. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Search API: Can the geocode param only give me lat/long results?
Streaming API will give what you need through locations method. http://dev.twitter.com/pages/streaming_api_methods#locations On Mon, Mar 21, 2011 at 12:22 PM, Stu stuart.batter...@gmail.com wrote: Hi, I have a pre-question before my question. With the search API's geocode based search, if it falls back on the user's profile information does it use GPS positions in their profile or some location such as 'London'. The problem is that I need much greater precision than that. Thus, if I perform this search: http://search.twitter.com/search.json?geocode=51.53,-0.14,1mi Am I able to get results back that only contain lat/long values of the tweet? The json returned here has basically no values for 'geo'. Thanks S. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- 氣 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Search API: Can the geocode param only give me lat/long results?
Hi Augusto, Thanks for your reply. The problem with the Streaming API is that I'd have to have set some database app listening to the stream for the past few years to be able to get all the data (especially for remote locations). I also don't know where my users are going to be, so I don't have the ability to set any bounding boxes... I need something that I can search back in time, rather than set listening.. without knowing in advance where the users will be. Hence the need for the search API... S. On Mar 21, 4:05 pm, Augusto Santos augu...@gemeos.org wrote: Streaming API will give what you need through locations method.http://dev.twitter.com/pages/streaming_api_methods#locations On Mon, Mar 21, 2011 at 12:22 PM, Stu stuart.batter...@gmail.com wrote: Hi, I have a pre-question before my question. With the search API's geocode based search, if it falls back on the user's profile information does it use GPS positions in their profile or some location such as 'London'. The problem is that I need much greater precision than that. Thus, if I perform this search: http://search.twitter.com/search.json?geocode=51.53,-0.14,1mi Am I able to get results back that only contain lat/long values of the tweet? The json returned here has basically no values for 'geo'. Thanks S. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- 氣 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Search API: Can the geocode param only give me lat/long results?
Hi Stu, If you need to use the search API for this, you'll need to tolerate the greedy-matching on the profile location field, by discarding the results uninteresting for your purposes (those tweets with no explicit geotagging). Taylor On Mon, Mar 21, 2011 at 9:15 AM, Stu stuart.batter...@gmail.com wrote: Hi Augusto, Thanks for your reply. The problem with the Streaming API is that I'd have to have set some database app listening to the stream for the past few years to be able to get all the data (especially for remote locations). I also don't know where my users are going to be, so I don't have the ability to set any bounding boxes... I need something that I can search back in time, rather than set listening.. without knowing in advance where the users will be. Hence the need for the search API... S. On Mar 21, 4:05 pm, Augusto Santos augu...@gemeos.org wrote: Streaming API will give what you need through locations method. http://dev.twitter.com/pages/streaming_api_methods#locations On Mon, Mar 21, 2011 at 12:22 PM, Stu stuart.batter...@gmail.com wrote: Hi, I have a pre-question before my question. With the search API's geocode based search, if it falls back on the user's profile information does it use GPS positions in their profile or some location such as 'London'. The problem is that I need much greater precision than that. Thus, if I perform this search: http://search.twitter.com/search.json?geocode=51.53,-0.14,1mi Am I able to get results back that only contain lat/long values of the tweet? The json returned here has basically no values for 'geo'. Thanks S. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- 氣 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] 401 Not Authorized in API OAuth PHP authorization
just a question: for request, the time need to be GMT 0? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] 401 Not Authorized in API OAuth PHP authorization
I'm doing another try.. and this time I trying with Wootterhttp://woorales.com/wootter/ that is a twitter opensource clienthttp://sourceforge.net/projects/wootter/files/ . Then I've downloaded and just change the keys in config.php. In Demo serverhttp://woorales.com/wootter/is right working... but in my server http://maathe.us/wootter/, not. I just don't know why can't get authenticate url through request that is responding with 401 header. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: hyphens at the end of shortned urls
Taylor, Thanks for checking on this. I hate asking, but can you give me a rough ETA on when this might be corrected and if it will apply to already posted updates? Reason I ask is because if it is going to take weeks I'll need to put in a temporary fix on the AWeber side. Thanks again Rodney On Mar 21, 11:26 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi there, We'll look into this issue; I'm unsure if the non-linkifying of URLs ending with a dash was intentional or not, but likely was not. To answer your latter question, tweet entities cannot be written to/suggested at time of tweet creation unfortunately. Thanks, Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 8:08 AM, roliver roliv...@gmail.com wrote: I work for AWeber Communications in Huntingdon Valley PA. We provide email marketing solutions for small to medium sized businesses and have 100,000+ active customers. We utilize the Twitter API to allow a customer to automatically post status updates to their twitter account when they send out a mailing. The urls in the status updates sometimes end with a hyphen. Up until recently, these have been auto-linked correctly by twitter. Recently this changed, and the hyphens at the end of the link are not included in the links I post to the API. For example,http://aweber.com/b/os7-would have linked correctly before, but now links tohttp://aweber.com/b/os7instead. Is this a bug or a permanent change at Twitter? Is there a way to explicitly define the links that get picked up, display_url maybe? I see that complete urls and start / end points are included in the entities: urls section of a tweet, but it is not clear if I am able to _submit_ the entities section for my own posts. Any help is appreciated. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Rate limit HTTP responses
No one ? On 20 Mar 2011, at 17:43, hax0rsteve wrote: Hi all, A question w/r/t HTTP responses when rate limiting is applied, which I'm hoping some kind soul will answer before I start hammering away at the API in careless experimentation : 420 Enhance Your Calm I understand from the docs that when this status code is returned, a Retry-After header will be returned in my http response, does this take the same format as the other rate headers e.g. : X-RateLimit-Limit: 350 X-RateLimit-Remaining: 350 X-RateLimit-Reset: 1277485629 so the Retry-After header will be X-Retry-After: ? Or is it some other format ? Obviously I could find out by jamming a huge number of search requests at the API, but it would be nice to know what to look for beforehand so that I can tell when to stop :) Thank you kindly. hax0rsteve -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Rate limit HTTP responses
Hi there Steve, As you've noticed, Search API rate limiting is applied and handled quite differently from the rest of the REST API. In the case of Search, when everything is operating under typical conditions, a Retry-After HTTP header will be sent to you (not an X-Retry-Header) -- the value of that header will contain an integer indicating the number of seconds to wait until issuing additional search API requests. Taylor On Sun, Mar 20, 2011 at 10:43 AM, hax0rsteve hax0rc...@btinternet.comwrote: Hi all, A question w/r/t HTTP responses when rate limiting is applied, which I'm hoping some kind soul will answer before I start hammering away at the API in careless experimentation : 420 Enhance Your Calm I understand from the docs that when this status code is returned, a Retry-After header will be returned in my http response, does this take the same format as the other rate headers e.g. : X-RateLimit-Limit: 350 X-RateLimit-Remaining: 350 X-RateLimit-Reset: 1277485629 so the Retry-After header will be X-Retry-After: ? Or is it some other format ? Obviously I could find out by jamming a huge number of search requests at the API, but it would be nice to know what to look for beforehand so that I can tell when to stop :) Thank you kindly. hax0rsteve -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Rate limit HTTP responses
Thanks Taylor, that's the info I need :) hax0rsteve On 21 Mar 2011, at 18:57, Taylor Singletary wrote: Hi there Steve, As you've noticed, Search API rate limiting is applied and handled quite differently from the rest of the REST API. In the case of Search, when everything is operating under typical conditions, a Retry-After HTTP header will be sent to you (not an X-Retry-Header) -- the value of that header will contain an integer indicating the number of seconds to wait until issuing additional search API requests. Taylor On Sun, Mar 20, 2011 at 10:43 AM, hax0rsteve hax0rc...@btinternet.com wrote: Hi all, A question w/r/t HTTP responses when rate limiting is applied, which I'm hoping some kind soul will answer before I start hammering away at the API in careless experimentation : 420 Enhance Your Calm I understand from the docs that when this status code is returned, a Retry-After header will be returned in my http response, does this take the same format as the other rate headers e.g. : X-RateLimit-Limit: 350 X-RateLimit-Remaining: 350 X-RateLimit-Reset: 1277485629 so the Retry-After header will be X-Retry-After: ? Or is it some other format ? Obviously I could find out by jamming a huge number of search requests at the API, but it would be nice to know what to look for beforehand so that I can tell when to stop :) Thank you kindly. hax0rsteve -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Requesting increased access levels for Streaming API
Those 350 requests per user per hour - that's just to the REST api, not the search api? Is there any comparable usage for the search api? We have an app that regularly runs a specific searches for users, performs some significant analysis on them, and gives them the results of that analysis. We bumprf into the Search rate limits last week because of the Fukishima tweet-storm, but we expect to reach them again as we scale up (and our service not working whenever something really important happens would invalidate the model). If we are allowed to make 350 search api requests authenticated as each of our users to avoid rate limiting, that would solve the problem. But if that type of behavior wouldn't let us make more search requests, or if it would be abusive to make requests that way, we'll re-architect the data retrieval system. We're trying not to misbehave, but it's difficult to tell how we're allowed to use our users. On Mar 17, 7:10 pm, Scott Wilcox sc...@dor.ky wrote: Yes, 350 requests per user, per hour. On 17 Mar 2011, at 22:46, hank williams wrote: -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: hyphens at the end of shortned urls
Don't have a rough ETA unfortunately; if it's important to you that your links are clickable by default on Twitter.com, then you may want to temporarily adjust your URL's format. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 10:39 AM, roliver roliv...@gmail.com wrote: Taylor, Thanks for checking on this. I hate asking, but can you give me a rough ETA on when this might be corrected and if it will apply to already posted updates? Reason I ask is because if it is going to take weeks I'll need to put in a temporary fix on the AWeber side. Thanks again Rodney On Mar 21, 11:26 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi there, We'll look into this issue; I'm unsure if the non-linkifying of URLs ending with a dash was intentional or not, but likely was not. To answer your latter question, tweet entities cannot be written to/suggested at time of tweet creation unfortunately. Thanks, Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 8:08 AM, roliver roliv...@gmail.com wrote: I work for AWeber Communications in Huntingdon Valley PA. We provide email marketing solutions for small to medium sized businesses and have 100,000+ active customers. We utilize the Twitter API to allow a customer to automatically post status updates to their twitter account when they send out a mailing. The urls in the status updates sometimes end with a hyphen. Up until recently, these have been auto-linked correctly by twitter. Recently this changed, and the hyphens at the end of the link are not included in the links I post to the API. For example,http://aweber.com/b/os7-would have linked correctly before, but now links tohttp://aweber.com/b/os7instead. Is this a bug or a permanent change at Twitter? Is there a way to explicitly define the links that get picked up, display_url maybe? I see that complete urls and start / end points are included in the entities: urls section of a tweet, but it is not clear if I am able to _submit_ the entities section for my own posts. Any help is appreciated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: In search of an honest developer who might be able to help me manifest my ideas
I think it is a great idea. It's just another data visualization on Twitter using 2D animation. I like Justin Bieber as an artist. He has 8M twitter followers. On Mar 21, 6:37 am, Chase Armbrust chase.armbr...@gmail.com wrote: But would prefer to speak via direct email rather than in a forum. Basically, I would like to create an application that adds RPG elements (leveling up, accomplishments, avatar-personalization) to the twitter experience. An example, hopefully enough to form the idea in the readers head. User opens the app, fills out twitter info, and then sees an egg. With his/her first tweet a baby bird (sticking with twitter's theme) breaks free of the egg. After acquiring your first follower you are allowed to leave the nest. Later in game, if user is retweeted by justin bieber at some point while he/she is playing the game, his/her bird avatar can now be customized with justin bieber hair. If he/she gets x number of followers, her baby bird evolves into a more mature and cooler looking (customizable?) bird. Lots of possibilities. Hate justin bieber? I am not a fan either, but this app would target the largest audience possible. Please email at cwil...@umich.edu if you think you can help. Or if you can point me to someone who might be able to help i would also greatly appreciate it. Best - Chase -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: User Search
Hi Arnaud, Did you authenticate your request with OAuth? The API method users/search requires authentication to work. users/show doesn't which is why you may find one worked while the other one didn't. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Mar 21, 2011 at 1:02 AM, arnaud arnaudle...@gmail.com wrote: no one knows what's wrong ? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] trends available in Malaysia?
Hey Jimmy, You can find a list of the available trends locations by calling the API method trends/available. More information on this method can be found on our developer resources site: http://dev.twitter.com/doc/get/trends/available Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Mar 21, 2011 at 4:09 AM, twitter dev dev.at.twit...@gmail.comwrote: Twitter supports topics trending only for 41 locations. list of locations available @ http://apiwiki.twitter.com/w/page/22554752/Twitter-REST-API-Method:-trends-available On Sun, Mar 13, 2011 at 9:45 PM, Jimmy Au ji...@mesixty.com wrote: The following lat long is in Malaysia but the return result is not in malaysia. I am wondering this service available in malaysia? http://api.twitter.com/1/trends/available.json?lat=3.144491long=101.711404 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] changing 'Via' and using HTTPS
Hi Suresh, The text that appears after the 'via' in a Tweet is read from your application details. The name of the application and it's URL are specified when you create an application on: http://dev.twitter.com/apps/new The application source does not support images, only text can be used. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Sun, Mar 20, 2011 at 11:18 PM, Suresh Kumar sureshkumar1...@gmail.comwrote: Dear Twitter Development Group, I have the following queries: 1. How can i change the via option. E.g. Want to use via 'x' operator 2. Is it possible to have an image (of 'x' operator) along with via 'x' operator message 3. Is it possible to use HTTPS rather than going for HTTP Regrads, Suresh sureshkumar1...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Search API rate limit change?
In many cases we are forced to change the rate limits in response to a significant increase in requests, which means it isn't always possible to give advanced notice of rate limit changes. For some of you it sounds like your code that handles rate limiting didn't react appropriately. When receiving a 420 response we recommend you stop making requests and then after the retry-after, slowly build up the number of requests you make. Put another way it isn't a good idea to make requests to the API at the velocity that caused the 420 response before. As always, the rate limits are there to ensure the system is responsive and available to as many users as possible. This means it is necessary to reduce the number of queries you can make without notice. The best place to stay informed about issues like this are posted through @twitterapi and published on the Twitter status blog: http://status.twitter.com/post/3785043723/slow-searches Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Mar 21, 2011 at 7:41 AM, Colin Surprenant colin.surpren...@gmail.com wrote: By adjusting the rate limits to reduce the stress on your search api without notice you have significantly increased the stress level on our end :P Seriously, advanced notice of the situation would have been welcome. In particular what created lots of confusion on our end is that even after pausing for the specified retry_after delay we would immediately get repeated 420s at which point we started to assume our IPs were banned (which also contributed to increase the stress level). Colin On Mar 21, 9:12 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: Taylor, Yeah this was definitely NOT good.In the past, when there is a service disruption, your api group would post something on your status page and tweet about it... Instead, I'm finding out about this from my customers... Did y'all tweet about this or present this somewhere where I could find it? Jeffrey Tweettronics.com On Sun, Mar 20, 2011 at 3:14 PM, Waldron Faulkner waldronfaulk...@gmail.com wrote: Without prior notice, I can understand (circumstances), but without any kind of subsequent announcement?? Means we have to discover issues ourselves, verify that they're Twitter related (and not internal), then search around for existing discussion on the topic. Saves us a lot of time and headaches if Twitter would just announce stuff like this. On Mar 18, 2:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: We're working to reinstate the usual limits on the Search API; due to the impact of the Japanese earthquake and resultant query increase against the Search API, some rates were adjusted to cope better serve queries. Will give everyone an update with the various limits are adjusted. @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Fri, Mar 18, 2011 at 11:39 AM, Hayes Davis ha...@appozite.com wrote: Hi, We're seeing this as well starting at approximately the same time as described. We've backed off on searching but are seeing no reduction in the sporadic limiting. It also appears that the amount of results returned on successful queries is severely limited. Some queries that often have 1500 tweets from the last 5 days are returning far fewer results from only the last day. Could we get an update on this? Hayes On Fri, Mar 18, 2011 at 10:13 AM, Eric e...@telvetto.com wrote: We're also seeing 400s on different boxes across different IP addresses with different queries (so it does not appear to be server or query specific). These began on all boxes at 2 a.m. UTC. We've backed off on both number and rate of queries with no effect. We've also noticed an increase in sporadic fail whales via browser based search (atom and html) from personal accounts, although we haven't attempted to quantify it. On Mar 18, 7:40 am, zaver zave...@hotmail.com wrote: Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, Zaver -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via
[twitter-dev] More interesting behavior with /users/show
XML returns empty response, but JSON response has data: http://api.twitter.com/1/users/show.xml?user_id=55441608 http://api.twitter.com/1/users/show.json?user_id=55441608 http://twitter.com/toadschorusnews Any ideas when this will be working consistently for all user IDs, yet? -- Dossy Shiobara | He realized the fastest way to change do...@panoptic.com | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on. (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] More interesting behavior with /users/show
Just in case folks were wondering, it's still happening for some user IDs for both XML *and* JSON, like: http://api.twitter.com/1/users/show.xml?user_id=39565468 http://api.twitter.com/1/users/show.json?user_id=39565468 Both return blank responses. On 3/21/11 11:18 PM, Dossy Shiobara wrote: XML returns empty response, but JSON response has data: http://api.twitter.com/1/users/show.xml?user_id=55441608 http://api.twitter.com/1/users/show.json?user_id=55441608 http://twitter.com/toadschorusnews Any ideas when this will be working consistently for all user IDs, yet? -- Dossy Shiobara | He realized the fastest way to change do...@panoptic.com | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on. (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
Anything on this? It's been quite some time and user lookup I believe would be used by a lot of apps. -N On 16 March 2011 05:46, Taylor Singletary taylorsinglet...@twitter.comwrote: Still working on it, unfortunately. No ETA for a fix yet. I know it's an aggravating bug for anyone who runs into it. Thanks for being patient. Taylor On Mar 15, 2011, at 5:09 PM, Adrian Petrescu apetr...@gmail.com wrote: Hi Taylor, Not trying to be pushy or anything, but have you guys uncovered anything related to this issue? It's still happening quite regularly for a couple of weeks now. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/dochttp://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- -Nischal twitter: NischalShetty http://twitter.com/nischalshetty facebook: Nischal http://facebook.com/nischal -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
