See Twurl:
http://thechangelog.com/post/536535280/twurl-oauth-enabled-curl-for-the-twitter-api
and
http://github.com/marcel/twurl
+Clint
On Thu, Apr 29, 2010 at 9:47 PM, mcfnord wrote:
> I think I know the answer to this question (YES), but I wanna clarify:
> Everywhere in the docs that I see
I think I know the answer to this question (YES), but I wanna clarify:
Everywhere in the docs that I see curl followed by credentials,
if the topic includes REST, that's an API that I will not be using
curl for,
because curl doesn't use oauth, so it cannot authenticate.
i'll certainly know in 30 d
this is part of the oauth rewrite that we mentioned at chirp - we hope to be
rolling it out soon.
On Sat, Apr 17, 2010 at 7:17 AM, Lil Peck wrote:
> On Sat, Apr 17, 2010 at 8:09 AM, sdesapio wrote:
> > Classic ASP VBScript OAuth library and example project:
> > http://scottdesapio.com/VBScriptO
On Sat, Apr 17, 2010 at 8:09 AM, sdesapio wrote:
> Classic ASP VBScript OAuth library and example project:
> http://scottdesapio.com/VBScriptOAuth/
>
> :)
>
My hero! (Although I am still waiting for Twitter to complete its 2
legged oauth.)
--
Subscription settings:
http://groups.google.com/gro
Classic ASP VBScript OAuth library and example project:
http://scottdesapio.com/VBScriptOAuth/
:)
On Apr 14, 11:16 am, Lil Peck wrote:
> On Tue, Apr 13, 2010 at 11:01 PM, TJ Luoma wrote:
> > I'm still unclear what people who use 'curl' will do after basic auth
> > is deprecated.
>
> Likewise fo
Why not just distribute a key with it? The worst that happens is someone
uses it in their app and it gets disabled and some people get pissed off at
you. I have yet to hear of this happening to a Twitter application. If
someone abuses your key and Twitter does not handle the situation well I
will p
> > yes, it could be a problem - however, there are known solutions to
> > obfuscating and keeping your consumer key secret. __not perfect, but pretty
> > good. __maybe we can start a discussion around this?
>
> What's the known solution for an open-source Web-based application
> that I want to di
On Wed, Apr 14, 2010 at 18:26, Raffi Krikorian wrote:
> yes, it could be a problem - however, there are known solutions to
> obfuscating and keeping your consumer key secret. not perfect, but pretty
> good. maybe we can start a discussion around this?
What's the known solution for an open-sourc
yes, it could be a problem - however, there are known solutions to
obfuscating and keeping your consumer key secret. not perfect, but pretty
good. maybe we can start a discussion around this? people are going to
need to start to move towards this method, and we are here to help you if
you need i
I am all for oAuth replacing basic, but one of the remaining issues is
consumer keys. With 1.0 signing is required thus requiring
distributing keys with your application. We all know this is pretty unsafe
since any hacker could yank them out.
oAuth 2.0 does seem to solve a lot of the issues involvi
We're getting ready to release a few changes to our oauth
implementation that will allow two legged oauth for public methods.
On Apr 14, 2010, at 9:16 AM, Lil Peck wrote:
On Tue, Apr 13, 2010 at 11:01 PM, TJ Luoma wrote:
I'm still unclear what people who use 'curl' will do after basic a
On Tue, Apr 13, 2010 at 11:01 PM, TJ Luoma wrote:
> I'm still unclear what people who use 'curl' will do after basic auth
> is deprecated.
>
>
Likewise for those of us who have Classic ASP web apps that use
XMLHTTP
(http://asp.web.id/update-twitter-status-with-classic-asp-vbscript.html)!
Will
OAuth was intended to facilitate inter-platform user account access without
requiring actual usernames or passwords to be exchanged. This would allow
platforms such as Twitter, Facebook, TwitPic, etc. to access each others
user accounts while maintaining the privacy of that user's access
credentia
OAuth has benefits all around for everybody. In addition to the
benefits already mentioned:
1) For a web app like mine, it saves a TON of support workload with
people who change their Twitter password, don't change it in my
system, and then blame my system for not working because it's not able
to
>> Cheers,
>>
>> Dean
>>
>>
>> --
>>
>> *From:* twitter-development-talk@googlegroups.com [mailto:
>> twitter-development-t...@googlegroups.com] *On Behalf Of *Raffi Krikorian
>> *Sent:* Wednesday, April 14, 201
-development-talk@googlegroups.com
Subject: Re: [twitter-dev] Re: Basic Auth Deprecation
we developed xauth specifically for that - mobile and desktop clients were
complaining about usability problems when they have to bounce their users to
a web browser. i'm well aware of the implications
googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Raffi
Krikorian
Sent: Wednesday, April 14, 2010 10:08 AM
To: twitter-development-talk@googlegroups.com
Subject: Re: [twitter-dev] Re: Basic Auth Deprecation
again - overly dramatic.
everything i said above still stan
xauth is definitely useful for the browserless case.
On Wed, Apr 14, 2010 at 6:33 AM, Cameron Kaiser wrote:
> > Why are you Twitter guys pushing xAuth so hard? Even for new desktop
> > clients? Instead of recommending a proper oAuth flow with PIN or such?
> > I understood its main purpose is to h
,
> >
> > > Dean
> >
> > > -Original Message-
> > > From: twitter-development-talk@googlegroups.com [mailto:
> twitter-development-t...@googlegroups.com] On Behalf Of Dewald Pretorius
> > > Sent: Tuesday, April 13, 2010 7:31 PM
> > >
i would love it to :P
On Wed, Apr 14, 2010 at 6:18 AM, wrote:
>
> - "Raffi Krikorian" wrote:
>
> > in my ideal world, nobody would have access to a user's password
> > except twitter.com -- oauth provides a framework so end applications
> > are not storing the actual password. people are no
> Dean
>
>
> --
>
> *From:* twitter-development-talk@googlegroups.com [mailto:
> twitter-development-t...@googlegroups.com] *On Behalf Of *Raffi Krikorian
> *Sent:* Wednesday, April 14, 2010 8:59 AM
> *To:* twitter-development-talk@googlegroups.com
>
On Wed, Apr 14, 2010 at 8:39 AM, Dean 'at' Cognation dot Net
wrote:
> But why is oauth better than basic for a desktop client?
>
> i understand it for the webapps but on a desktop client whats the
> point?
>
> Basically you are saying the desktop end user cant be trusted? Sorry
> but that doesn't
m [mailto:
> twitter-development-t...@googlegroups.com] *On Behalf Of *Raffi Krikorian
> *Sent:* Wednesday, April 14, 2010 8:59 AM
> *To:* twitter-development-talk@googlegroups.com
> *Subject:* Re: [twitter-dev] Re: Basic Auth Deprecation
>
>
>
> in my ideal world, nobody would
> Why are you Twitter guys pushing xAuth so hard? Even for new desktop
> clients? Instead of recommending a proper oAuth flow with PIN or such?
> I understood its main purpose is to help legacy clients with
> transition, and new clients should do proper oAuth.
I can tell you that there are many TT
will have to start using oauth.
>
> > Cheers,
>
> > Dean
>
> > -Original Message-
> > From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald
Pretorius
> > Sent: Tuesday, April 13, 2010 7:31
- "Raffi Krikorian" wrote:
> in my ideal world, nobody would have access to a user's password
> except twitter.com -- oauth provides a framework so end applications
> are not storing the actual password. people are notoriously bad with
> using the same password on lots of different sites. ad
top will
> > still work correct? Basic functionality is only being turned off for web
> > apps correct? It's not like desktop apps will have to start using oauth.
>
> > > > Cheers,
>
> > > > Dean
>
> > > > -Original Message-
>
e-
> > From: twitter-development-talk@googlegroups.com
> > [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald
> > Pretorius
> > Sent: Tuesday, April 13, 2010 7:31 PM
> > To: Twitter Development Talk
> > Subject: [twitter-dev] Re: Ba
I understand this, applications running on the desktop will
> still work correct? Basic functionality is only being turned off for web
> apps correct? It's not like desktop apps will have to start using oauth.
> >
> > > Cheers,
> >
> > > Dean
> >
>
t using oauth.
>
> > Cheers,
>
> > Dean
>
> > -Original Message-
> > From: twitter-development-talk@googlegroups.com
> > [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald
> > Pretorius
> > Sent: Tuesday, April 13, 2010 7
marcel (@noradio) and i have been working on http://github.com/marcel/twurl --
there is definitely some work that needs to be done, but we're getting
close.
On Tue, Apr 13, 2010 at 9:01 PM, TJ Luoma wrote:
> On Tue, Apr 13, 2010 at 7:35 PM, Raffi Krikorian
> wrote:
> >
> > we'll make sure to me
On Tue, Apr 13, 2010 at 7:35 PM, Raffi Krikorian wrote:
>
> we'll make sure to message it long before hand!
I'm still unclear what people who use 'curl' will do after basic auth
is deprecated.
Is there an OAuth for the commandline? If so: pointers, please.
TjL
-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Dewald Pretorius
Sent: Tuesday, April 13, 2010 7:31 PM
To: Twitter Development Talk
Subject: [twitter-dev] Re: Basic Auth Deprecation
Could you please announce the hard turn off date somewhere on one of
your Tw
we'll make sure to message it long before hand!
On Tue, Apr 13, 2010 at 4:30 PM, Dewald Pretorius wrote:
> Could you please announce the hard turn off date somewhere on one of
> your Twitter blogs about a month ahead of time, so that we all have an
> official source to point our users to when we
Could you please announce the hard turn off date somewhere on one of
your Twitter blogs about a month ahead of time, so that we all have an
official source to point our users to when we explain to them why
we're converting everything over to OAuth?
On Apr 13, 8:19 pm, Raffi Krikorian wrote:
> we
Another beta tester here! ;-)
On Jan 18, 9:54 am, TJ Luoma wrote:
> On Mon, Jan 18, 2010 at 12:48 PM, Raffi Krikorian wrote:
> > we have a command line tool that acts exactly like curl but does all the
> > oauth signatures transparently to the end user (the user simply needs to
> > register the
On Mon, Jan 18, 2010 at 12:48 PM, Raffi Krikorian wrote:
> we have a command line tool that acts exactly like curl but does all the
> oauth signatures transparently to the end user (the user simply needs to
> register the keys with the tool). this way people who rely on the ability
> to use curl
we have a command line tool that acts exactly like curl but does all the
oauth signatures transparently to the end user (the user simply needs to
register the keys with the tool). this way people who rely on the ability
to use curl to interact with the API (such as scripts, etc.) can still do
so.
On Mon, Jan 18, 2010 at 11:05 AM, ryan alford wrote:
> yes, it's official. The depreciation of Basic Auth will "start" in June.
So — I will ask again — what are those of us using curl programs
(commandline, not web) supposed to do then?
TwitReport works on this:
curl --location --referer ";aut
> Thanks. Hope it's not official. I don't remember reading anything like
> that on the 2 lists.
No, it wasn't posted here at the time. I insert a fairly loud *ahem* to
ensure such things are posted here also in the future.
--
personal: http://www.cameronkaise
yes, it's official. The depreciation of Basic Auth will "start" in June.
Ryan
On Mon, Jan 18, 2010 at 10:57 AM, Hwee-Boon Yar wrote:
> Thanks. Hope it's not official. I don't remember reading anything like
> that on the 2 lists.
>
> --
> Hwee-Boon
>
> On Jan 18, 7:01 pm, Rich wrote:
> > Ryan
Thanks. Hope it's not official. I don't remember reading anything like
that on the 2 lists.
--
Hwee-Boon
On Jan 18, 7:01 pm, Rich wrote:
> Ryan Sarver said it last last
> yearhttp://twitter.com/Scobleizer/status/6493268213
>
> On Jan 17, 4:46 am, Hwee-Boon Yar wrote:
>
>
>
> > On Jan 14, 8:30
Ryan Sarver said it last last year
http://twitter.com/Scobleizer/status/6493268213
On Jan 17, 4:46 am, Hwee-Boon Yar wrote:
> On Jan 14, 8:30 am, twittme_mobi wrote:
>
> > Hello ,
>
> > Regarding Basic Auth Deprecation is June
>
> Any where this is announced?
>
> --
> Hwee-Boon
On Jan 14, 8:30 am, twittme_mobi wrote:
> Hello ,
>
> Regarding Basic Auth Deprecation is June
Any where this is announced?
--
Hwee-Boon
> Thanks for your reply!
> Couldn't I just save the access token in a database and use it later?
Yup. Many, if not most, applications do just that.
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@
Hello,
Thanks for your reply!
Couldn't I just save the access token in a database and use it later?
Thanks.
On Jan 14, 1:31 am, Cameron Kaiser wrote:
> > Regarding Basic Auth Deprecation is June - would it be possible using
> > OAuth to automate
> > some users posts - for example - there are so
Because Twitter would require keys, not usernames and passwords.
Logons go to Twitter, and keys are returned. Programs would (will)
break unless grandfathered, but that's a manageable issue.
That said, there should be a way for developers to use Basic Auth to
"hash out" (develop) their code for
47 matches
Mail list logo
