[twitter-dev] Re: Using oAuth by Curl
On Sep 1, 10:36 pm, Andrea Stagi stagi.and...@gmail.com wrote: There are any alternatives?? You can try Curlicue: http://github.com/decklin/curlicue There is no installation step at the moment, just run the script (see the instructions for how to get and save your tokens). Feedback 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?hl=en
[twitter-dev] Re: Streaming API and lists
On Aug 12, 11:46 am, Matt Harris thematthar...@twitter.com wrote: The streaming API allows you to follow user IDs and track keywords but not lists directly. Instead you need to follow all the user IDs of the list and then assemble their Tweets on your server to recreate the list. The limit for a list is 500 members, but we can only follow 400 user ids by default with the streaming API. Is there any way around this?
[twitter-dev] Re: What tools do you use?
[Bringing this old stickied thread back up for an announcement... apologies for semi-broken threading.] With basic auth on the way out at Twitter, I've wanted a way to make requests from the command line just as I used to with curl. Rather than implementing an HTTP client in Ruby/Python/whatever, I decided to do this as a shell script wrapping curl: http://github.com/decklin/curlicue It's really just curl under the hood, so you have access to all your favorite command-line options. It should work with any OAuth 1.0a service, not just Twitter. There is of course an initial setup step that requires your consumer key and secret, but if you save your credentials in the correct location after that, you can pretty much just replace curl with curlicue in commands and forget about it. Please direct any bugs/issues/questions to Github. Thanks! (I wrote this a month or so ago, but was holding off on posting here because I was hoping for the open source key exchange process to move forward. Now that that is officially not going to be ready in time[1], I figured I might as well get this out there. For now, you will have to register your own app before you can use it, and make requests as that app.) [1] http://xrl.us/bhva55 Abraham Williams wrote: Lets collect an awesome list of tools and applications we use to help develop with the Twitter API.
Re: [twitter-dev] Open-source, distributed PHP app and consumer secret
Excerpts from Michael Babcock's message of Mon Jul 26 19:28:15 -0400 2010: So, I after spending the day looking through documentation, developer's discussion and testing various OAuth code bits, it is my understanding that there is no secure OAuth solution for open-source PHP developers. But, the August 16th deadline is still looming. I am also concerned about this. Here is the response I got from support: we're continuing to experiment with this feature, and have not made it available further. I apologize for the delay and inconvenience, but keep an eye on our developer talk group for future announcements. I have been watching this list for about a month (prior to checking with support) in case the feature is discussed here before being announced. @twitterapi, could we get some clarification on whether or not something will be ready before the August 16 deadline?
Re: [twitter-dev] How is this a solution?
Excerpts from Cameron Kaiser's message of Fri Jul 16 01:00:55 -0400 2010: Actually, no. The process creates a completely new app key and secret cloned from the original one. They do not have anything in common with each other apart from the name and branding (and the user can change it later; it's just a regular old app key). You can see this in action by looking at TTYtter, which uses the process. They are not the same key and secret at all. When was this process turned on? (I just checked out TTYtter and indeed, it works.) I asked for an update a couple weeks ago but I hadn't seen anything here or on the announce list, so I assumed other things had taken priority. -- things change. deck...@red-bean.com
Re: [twitter-dev] oauth_sign - simple C code to generate an OAuth signature
Excerpts from Jef Poskanzer's message of Mon Jul 05 12:48:27 -0400 2010: I needed was a simple command-line program to make an OAuth-signed HTTP call. Did that already exist? Sort of - there was Marcel Molina's twurl: http://github.com/marcel/twurl Only problem is that it's written in Ruby, which I do not have installed and am not really intrerested in installing. There is also Curlicue, which I've written: http://github.com/decklin/curlicue I've been waiting on the open source workflow to announce it here, but may already be useful for those who don't have a need for directly linking to C code. -- things change. deck...@red-bean.com
[twitter-dev] Re: Coming soon: a solution for Open Source applications using OAuth with the Twitter API
Taylor Singletary wrote: We're waiting on a few minor bug fixes to be in place before rolling this out to a wider audience. I'll post a new message when things are good to go and we're ready to accept applications into the feature. Any update or ETA on this? I have an app that I'm eager to test out. (I notice that if you open http://dev.twitter.com/apps/key_exchange with a valid oauth_consumer_key, instead of a 404 there is a page that says Sorry, key exchange is not permitted for this application. Does this mean the answer is soon?) -- things change. deck...@red-bean.com
