[twitter-dev] Re: xhr2 and cross domain Ajax requests
bump Would be good to hear from Twitter API devs on this. On Apr 27, 12:50 am, André Luís andreluis...@gmail.com wrote: As long as they keep this from affecting other non-API endpoints, +1 Other than that, it could be disastrous. -- André Luís On Tue, Apr 27, 2010 at 12:04 AM, rmanalan rich.manal...@gmail.com wrote: +1 On Apr 26, 5:01 am, Remy Sharp r...@leftlogic.com wrote: Is there any thoughts towards setting the following header on the Twitter API server: Access-Control-Allow-Origin: * For those of us developers working with web technology in closed environments (such as PhoneGap) we can useXHRcontrolled requests to Twitter - i.e. we can read headers (like the X-RateLimit-Remaining), abort requests, handler timeouts and handle the all important fail whale coming back instead of a JSON response saying it's failed. Such a small change would open up using the web to access the API. What do you think? - Remy. -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] xhr2 and cross domain Ajax requests
Is there any thoughts towards setting the following header on the Twitter API server: Access-Control-Allow-Origin: * For those of us developers working with web technology in closed environments (such as PhoneGap) we can use XHR controlled requests to Twitter - i.e. we can read headers (like the X-RateLimit-Remaining), abort requests, handler timeouts and handle the all important fail whale coming back instead of a JSON response saying it's failed. Such a small change would open up using the web to access the API. What do you think? - Remy. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Mobile oAuth always says access update
It appears that mobile oAuth is ignoring the *access only* flag set on the connection permissions. I go out of my way to ensure I'm not writing to people's account, and now it says it anyway, screen shot here: http://img42.yfrog.com/img42/3104/ifrw.jpg Any chance of a fix? Thanks, Remy. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Error in API wiki for favs - please?!
Just doing a review of the API docs to catch up on any changes, and the favorites method is now saying that authentication is required. Currently on the old and new API, authentication *isn't* required. Please, please, tell me this is just a mistake and you don't plan to close this to auth access only. This being open makes for some really cool little JavaScript apps, including http://snapbird.org/rem/favs/dev (for example) and a bunch of other apps. This is just a typo in the wiki, right? Remy / @rem
[twitter-dev] Re: Error in API wiki for favs - please?!
I should add that the RSS is completely open for this on all users pages, so it stands to good reason that this API method should remain open (obviously with the exception of protected user accounts). Remy / @rem
[twitter-dev] JavaScript API library
I wrote this to make my own life easier and dev quicker when I was building my own JS based apps, but I figured it might be worth sharing it here. http://github.com/remy/twitterlib Twitterlib.js is an open source library to handle all the open (i.e. no auth required) API calls, and normalises the request methods and response data - i.e. search and timeline are the same. It includes a bunch of utility methods, including linkifying and generating standard rendered list items from a tweet object. It also supports custom method calls, allowing you to also hit pre- authenticated URLs (you can see this in use on http://snapbird.org when searching DMs or the friend timeline). It also has search filtering baked in to the library, so you can use the same syntax as the search API, but to search any of the existing API calls - i.e. a user's timeline. The library is being used in production on http://snapbird.org which searches beyond the 10 day limit using exactly the method described above. Hope this helps someone. Cheers - Remy.
[twitter-dev] Retweet count in status
I'm not sure if this has been covered already, so if it has please point me in the right direction (had a quick search too). Once piece of really valuable information on the user timeline against each status would be the retweet count. Obviously doing this ourselves via API calls could be expensive (in terms of hits we're sending), so it makes sense if it were available in the API. I can see lots of use for having just the count in there, just as we have the favorited flag. Any chance it's coming? Cheers, Remy.
[twitter-dev] Mentions with since_id is worthless - proposed fix
Sorry for a slightly gaming subject line, but I've just worked out that the 'since_id' parameter is worthless in the mentions api call. It may also be the case in every other API call - but let me explain. The only time that I can think that you need to use the since_id param is if you want to start looking at tweets from that point in time onwards. The API supports a count param, so technically I may only be interested in the first tweet since X id: If the tweet with the ID 1800200012 was posted 15 days ago (and I've had lot of mentions since) - I would expect to use the following call to get the mentions after that particular tweet: http://twitter.com/statuses/mentions.xml?since_id=1800200012count=1 However, since the API call does all the mentions up to now - it gives me the my latest tweet. If there was a way to work backwards, i.e. in reverse order then it would solve this issue in one fell swoop. Possibly using: http://twitter.com/statuses/mentions.xml?since_id=1800200012count=1sort=desc This would be really useful for the personal timeline too, since I could track the first tweet when I got on holiday, and then follow each tweet since without having to depend on the search API (which is still limited to 3 weeks of data). What do you think? Should/could this be made in to feature? Cheers -- Remy Sharp
[twitter-dev] A way to see replies to specific tweets
Hi, I've been looking around the API (and the search.twitter.com pages) and I believe it's not possible to find all the tweets that are in direct reply to a specific status_id. I know I can get all the replies *since* a specific status_id, but this gives me the latest replies - so if it was some time ago I can't see the real replies. It would be really useful to see direct replies to X status_id to be able to track a conversation. I've also tried the search.twitter.com API, but it looks like the since_id breaks the request: Specifically since there's the 'in_reply_to' key in the return object from the statuses. Even better if we didn't need to have an authenticated session to get the conversation. Anyway - be great if it was considered for the API - happy to add the request to the issues log if you think it's worth while. Cheers, -- Remy Sharp
Favorites: logged in requires auth, logged out doesn't
Hi, I can't make out whether I've misunderstood the documentation, or if this is just wrong - but: When I am logged out, the following url works fine with no authentication request: http://twitter.com/favorites/rem.json However, when I'm logged *in* - the same request asked for my credentials. Is that correct? That seems like a bug to me - I thought you could get anyone's favorites via the URL (as above). Cheers, Remy.
