[twitter-dev] search.rss
Hi, I was using the search.atom command and just happened to try search.rss. I was surprised that this works because I didn't see it documented in the api docs. Is search.rss documented anywhere? Is it safe to use? I noticed two problem with search.rss. 1) When since= is empty the returned rss always contains a twitter:warning element. 2) When near= is not empty (for instance near=NYC) I always get a 406 http error. Thanks, Jonas
[twitter-dev] Re: search.rss
Matt, Okay, I'm switching back to search.atom. However, I still get an "Invalid Parameter" error when since= is not empty. Are all the parameters that are available to the search command also available to the search.atom command? Jonas On May 27, 3:41 pm, Matt Sanford wrote: > Hi Jonas, > > It is not safe to use and will go away at some point. It was > added for questionable reasons and has never been linked to or > documented. Having said that I don't remove it because people have > changed .atom to .rss and started relying on it. Please don't use it > since it has some known bugs and less data than the atom version > (thank you RSS spec for not having a link with a rel attribute). > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > On May 27, 2009, at 12:32 PM, Jonas wrote: > > > > > Hi, > > > I was using the search.atom command and just happened to try > > search.rss. I was surprised that this works because I didn't see it > > documented in the api docs. Is search.rss documented anywhere? Is it > > safe to use? > > > I noticed two problem with search.rss. > > > 1) When since= is empty the returned rss always contains a > > twitter:warning element. > > > 2) When near= is not empty (for instance near=NYC) I always get a 406 > > http error. > > > Thanks, > > Jonas > >
[twitter-dev] Re: search.rss
Hi Matt, I mistakenly wrote "since=" above when I meant to write "near=". The following url should return tweets with 15 miles of nyc, but instead I get invalid parameter. http://search.twitter.com/search.atom?q=&ands=&phrase=&ors=¬s=&tag=&lang=en&from=&to=&ref=&near=nyc&within=15&units=mi&since=&until=&rpp=10 Jonas On May 27, 4:28 pm, Matt Sanford wrote: > Hi Jonas, > > Yes, they are. The since= parameter should not be required, can > you share the URL you're getting the error from? > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > On May 27, 2009, at 1:13 PM, Jonas wrote: > > > > > Matt, > > > Okay, I'm switching back to search.atom. However, I still get an > > "Invalid Parameter" error when since= is not empty. > > > Are all the parameters that are available to the search command also > > available to the search.atom command? > > > Jonas > > > On May 27, 3:41 pm, Matt Sanford wrote: > >> Hi Jonas, > > >> It is not safe to use and will go away at some point. It was > >> added for questionable reasons and has never been linked to or > >> documented. Having said that I don't remove it because people have > >> changed .atom to .rss and started relying on it. Please don't use it > >> since it has some known bugs and less data than the atom version > >> (thank you RSS spec for not having a link with a rel attribute). > > >> Thanks; > >> – Matt Sanford / @mzsanford > >> Twitter Dev > > >> On May 27, 2009, at 12:32 PM, Jonas wrote: > > >>> Hi, > > >>> I was using the search.atom command and just happened to try > >>> search.rss. I was surprised that this works because I didn't see it > >>> documented in the api docs. Is search.rss documented anywhere? > >>> Is it > >>> safe to use? > > >>> I noticed two problem with search.rss. > > >>> 1) When since= is empty the returned rss always contains a > >>> twitter:warning element. > > >>> 2) When near= is not empty (for instance near=NYC) I always get a > >>> 406 > >>> http error. > > >>> Thanks, > >>> Jonas > >
[twitter-dev] since_id and page
I'm confused about how since_id and page should be used. Can they be used together in the same search.atom command? I get different results with search.atom depending upon what order I place the since_id and the page parameters. For example, http://search.twitter.com/search.atom?q=blah&rpp=10&since_id=1967746107&page=1 and http://search.twitter.com/search.atom?q=blah&rpp=10&page=1&since_id=1967746107 What I'd like to do is query pages 1 through 15 with rpp=100 and since_id=. Jonas
[twitter-dev] search is acting strange
When I do: http://search.twitter.com/search.atom?q=blah The most recent tweet is a couple of minutes old. The next time I do it the most recent is an hour old. The next time a half hour old. The next time a minute old, etc, etc.
[twitter-dev] Re: search is acting strange
Matt, It looks like this problem has diminished but not gone away. When I do several consecutive searches, the latest tweet is never more than a few minutes out of sync. I guess there will always be some small amount of time that the twitter servers will be out of sync. I'm just wondering if there will be any more improvement, or if this is the best it will be. Thanks, Jonas On Jun 3, 1:20 pm, Matt Sanford wrote: > Hi there, > > This is a known issue [1] we're working on. Some servers are > behind and we're trying to get them back up to date. Mark the Google > Code issue [1] with a star to get updates … no need to leave comments > in the ticket. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > [1] -http://code.google.com/p/twitter-api/issues/detail?id=646 > > On Jun 3, 2009, at 10:10 AM, Jonas wrote: > > > > > When I do:http://search.twitter.com/search.atom?q=blah > > > The most recent tweet is a couple of minutes old. The next time I do > > it the most recent is an hour old. The next time a half hour old. > > The next time a minute old, etc, etc. > >
[twitter-dev] issue 646
I'm curious why there have been no progress updates regarding issue 646. Can anyone speak to the status of this problem. See http://code.google.com/p/twitter-api/issues/detail?id=646
[twitter-dev] Re: Search API to require HTTP Referrer and/or User Agent
How does one set the http referrer and user agent? On Jun 16, 12:33 pm, Doug Williams wrote: > Hi all, > The Search API will begin to require a valid HTTP Referrer, or at the very > least, a meaningful and unique user agent with each request. Any request not > including this information will be returned a 403 Forbidden response code by > our web server. > > This change will be effective within the next few days, so please check your > applications using the Search API and make any necessary code changes. > > Thanks, > Doug
[twitter-dev] basic authentication using XMLHTTPRequest
I'm having a problem authenticating using XMLHTTPRequest like this:
XMLHTTPRequest.open('GET', url, false, user, password);
I'm issuing the users/show.json command, which doesn't require
authentication until you exceed 100 calls in an hour. At that point I
begin getting 400 errors.
I'm not sure what the problem is. I am able to authenticate using
curl -u, so I know I should be able to get authentication working with
XMLHTTPRequest. Anyone have any suggestions? Is there more to it
than calling open with user/password?
Jonas
[twitter-dev] user/show does not return 401
When I send incorrect credentials with a user/show.json command I expect to get a 401 code from twitter. However, when I do this from a browser using xmlhttprequest I get 400 instead. Actually, for the first 100 tries I get 200 codes, and there after I get 400 codes, because there is a rate limit of 100 per hour. The point is, at no time does authentication ever occur. Could this be a bug in twitter? As this post explains http://groups.google.com/group/twitter-development-talk/browse_thread/thread/35c3918ec2317e98/d05dd17c5a261dfa?lnk=gst&q=xmlhttprequest+401#d05dd17c5a261dfa the RFC dictates that the browser does not send credentials until it first receives a 401.
[twitter-dev] Re: user/show does not return 401
Hi Matt, I can see why it's done this way. The javascript code for adding credentials to the header is straight-forward and works fine. I don't do much http programming, so this was all new to me, but it would be nice if the api docs reflected what kind of authentication is required -- forced or passive. Thanks, Jonas On Jun 22, 11:08 am, Matt Sanford wrote: > Hi Jonas, > > The issue here is that /users/show allows both authenticated and > un-authenticated access. Unlike the bug you referenced [1], the RFC > does not really mention what to do in that case to my knowledge. For > resources that require authentication we respond with a 401, and the > browser prompts for a username/password and re-sends and authenticated > request. In the case of /users/show we return valid data when not > authenticated so the browser does not bother. > In most programming languages/libraries there is an option to > preemptively authenticate, or you can manually add the Authorization > header. Someone has even done this in Javascript [2], albeit in XUL > since it lacks a cross-domain security issue. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > [1] -http://code.google.com/p/twitter-api/issues/detail?id=135 > [2] -http://groups.google.com/group/twitter-development-talk/browse_frm/th... > > On Jun 19, 2009, at 8:21 PM, Jonas wrote: > > > > > When I send incorrect credentials with a user/show.json command I > > expect to get a 401 code from twitter. However, when I do this from a > > browser using xmlhttprequest I get 400 instead. Actually, for the > > first 100 tries I get 200 codes, and there after I get 400 codes, > > because there is a rate limit of 100 per hour. The point is, at no > > time does authentication ever occur. > > > Could this be a bug in twitter? > > > As this post explains > > >http://groups.google.com/group/twitter-development-talk/browse_thread... > > > the RFC dictates that the browser does not send credentials until it > > first receives a 401. > >
[twitter-dev] created_at format
I am using search.json and track.json and I noticed that the date format for created_at is different. search.json: Tue, 11 Aug 2009 20:23:36 + track.json: Tue Aug 11 20:23:36 + 2009 Is there a reason why Twitter uses different formats for the same information? Is there any interest in using just one format? I would prefer the format outputted by search.json because it is easily parsed by the DateTime object in .NET.
[twitter-dev] can't register an app
When I attempt to register a new app on http://dev.twitter.com/apps/new I always get this error: "Website: Not a valid URL format." I get this error no matter what I type in the Website field. I've tried every variation of URL format I can think of. I also tried to register my app on http://twitter.com/apps/new. Why are there two different registration pages? Are they for different purposes? Is one obsolete? Anyway, whenever I try to register on this page the "Twitter is over capacity" with the whale image. Any suggestions? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Re: can't register an app
Ok, I stumbled upon what part of my valid URL was preventing my app from getting registered. The URL had an underscore, like http://blah_blah.woof.com. Despite what the error message says, this is a valid URL format. How about a message that says "No underscores allowed" or something? On Jul 22, 8:33 pm, Jonas wrote: > When I attempt to register a new app onhttp://dev.twitter.com/apps/new > I always get this error: "Website: Not a valid URL format." I get > this error no matter what I type in the Website field. I've tried > every variation of URL format I can think of. > > I also tried to register my app onhttp://twitter.com/apps/new. Why > are there two different registration pages? Are they for different > purposes? Is one obsolete? Anyway, whenever I try to register on > this page the "Twitter is over capacity" with the whale image. > > Any suggestions? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] hard-coded oauth access token
Is it possible to authenticate from a web page without any server-side program? I would like to use javascript (and jsonp with query-string oauth, I am guessing) and hard code my access_token in a javascript variable. I know this would be a major security no-no. I have no intention of putting the webpage on the internet. I simply would like to know if my intention is even possible. It would be greatly appreciated if someone could put aside the security issue for a moment and answer my question. Thanks! -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] other twitter forums
Are there any other active twitter forums? -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] how would I test an app?
Hi everyone I wrote an app for the Django web framework that forces users to authenticate themselves using Twitter before being able to access certain parts of the website. I'm a huge fan of unittesting and continuous integration testing, so I'm wondering how I would test the oauth API automated. Looks like I need to register an App but I'm not sure if Twitter allows setting up apps just for testing and I don't know how I would go about storing keys etc so people can test it but not abuse it. Jonas -- 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
