On Mon, Mar 9, 2009 at 6:05 PM, Alex Payne a...@twitter.com wrote:
We're discussing a local proxy that could be used for testing. It's
definitely a known problem.
Um, am I reading this correctly?
is 'curl --netrc' not going to work anymore once OAuth is implemented?
TjL
We're discussing a local proxy that could be used for testing. It's
definitely a known problem.
Um, am I reading this correctly?
is 'curl --netrc' not going to work anymore once OAuth is implemented?
More accurately, it's not going to work when Basic Auth is discontinued.
--
As Alex stated above, we know cURL usage will break if and when basic
authentication support is wholly discontinued. It's something we're
equally concerned about and something we would like to avoid. Stay
tuned.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Tue, Mar 10, 2009
I believe it has been suggested on the list before Twitter implement a dev
sandbox with fake data that continues to support BasicAuth similar to how
BrightKite(?) does. Using Curl to get started is another reason to implement
this.
Abraham
On Tue, Mar 10, 2009 at 09:40, Cameron Kaiser
On Tue, Mar 10, 2009 at 10:45 AM, Doug Williams d...@twitter.com wrote:
As Alex stated above, we know cURL usage will break if and when basic
authentication support is wholly discontinued. It's something we're
equally concerned about and something we would like to avoid. Stay
tuned.
OK, I
On Tue, Mar 10, 2009 at 11:33 AM, Cameron Kaiser spec...@floodgap.com wrote:
This is the same issue I'm working with for TTYtter, and I think I have a
solution which I plan to implement when OAuth goes open. I'll post more about
the workflow (it's open source) when I get a working beta
Ditto.
-Original Message-
From: Chad Etzel jazzyc...@gmail.com
Date: Tue, 10 Mar 2009 11:47:57
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: Using curl with Twitter
On Tue, Mar 10, 2009 at 11:33 AM, Cameron Kaiser spec...@floodgap.com wrote
The real trick was what to do with keys in an open source app, but fortunately
the key issue is already solved because Twitter is presumably not relying on
oauth_consumer_key to unambiguously or securely identify consumer clients,
But then how could Twitter revoke access for a rogue app? I
The real trick was what to do with keys in an open source app, but
fortunately the key issue is already solved because Twitter is presumably
not relying on oauth_consumer_key to unambiguously or securely identify
consumer clients,
But then how could Twitter revoke access for a rogue
Great tip! This should become a great thread with cURL tips.
Below shows how to send POST data (note the -d flag):
curl -u username:password -d status=Updating with cURL
http://twitter.com/statuses/update.xml
You can also send GET requests:
curl -u username:password
What else does the community have to offer when it comes to our
favorite API unit test framework :)
I was just going to comment on this what happens when OAuth hits?
I fear that this very simple diagnostic mechanism will become
obsolete. Now asking someone to run a quick curl test becomes
11 matches
Mail list logo
