[twitter-dev] Re: about OAuth
You need the token and the token secret. On Oct 10, 2009, at 3:40 PM, Oguzhan wrote: > > Hi Folks, > > I'm using OAuth in my twitter application and I was wondering > something. > > Have received the user's permission by OAuth. > I saved my database oauth_token after for example one day later. Can I > update twitter status with my saved oauth_token? > > >
[twitter-dev] Re: about OAuth
the only way to find out is to do it On Sat, Oct 10, 2009 at 2:05 PM, Oguzhan wrote: > > Hi Folks, > > I'm using OAuth in my twitter application and I was wondering > something. > > Have received the user's permission by OAuth. > I saved my database oauth_token after for example one day later. Can I > update twitter status with my saved oauth_token? > > > >
[twitter-dev] Re: about OAuth
Yes you can.. On 10 oct, 20:05, Oguzhan wrote: > Hi Folks, > > I'm using OAuth in my twitter application and I was wondering > something. > > Have received the user's permission by OAuth. > I saved my database oauth_token after for example one day later. Can I > update twitter status with my saved oauth_token?
[twitter-dev] Re: About OAuth
But ... but ... I'm trying to do a similar kind of thing from a perl
command line.
I looked at this on github before, and where it says:
// Register an application at http://dev.twitter.com/apps and from
your new apps page get "my access token".
There is no "application" for me to go to in order to get an access
token. I also need the script to run from a cron scheduler so I can't
have it stop and ask me for a verification PIN with each run.
Have you come across similar difficulties elsewhere? My searches are
turning up tantalisingly incomplete and inconsistent code snippets
that don't work ..
On Sep 4, 5:52 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Have a look athttp://gist.github.com/564882
>
> Abraham
> -
> Abraham Williams | Hacker Advocate |http://abrah.am
> @abraham |http://projects.abrah.am|http://blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>
> On Thu, Sep 2, 2010 at 19:50, David wrote:
> > I found out twitter does not support Basic Auth any, and I wonder how
> > can I change my code from Basic Auth to OAuth.
>
> > and my code like following:
>
> > $username=username;
> > $password=password;
> > $message=message;
> > $host = "http://twitter.com/statuses/update.xml";;
> > $ch = curl_init();
> > curl_setopt($ch, CURLOPT_URL, $host);
> > //curl_setopt($ch, CURLOPT_VERBOSE, 1);
> > //curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
> > curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
> > curl_setopt($ch, CURLOPT_TIMEOUT, $config->timeout );
> > curl_setopt($ch, CURLOPT_USERPWD, "$username:$password");
> > curl_setopt($ch, CURLOPT_POSTFIELDS,"status=$message");
> > //curl_setopt($ch, CURLOPT_HTTP_VERSION,
> > CURL_HTTP_VERSION_1_1);
> > curl_setopt($ch, CURLOPT_POST, 1);
> > $result = curl_exec($ch);
> > // Look at the returned header
> > $resultArray = curl_getinfo($ch);
> > curl_close($ch);
>
> > --
> > 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 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: About OAuth authorization
1. OAuth allows your user to authenticate without ever exposing his Twitter credentials to your application. 2. OAuth allows a user to revoke your application's access to their account. 3. If you don't use OAuth, tweets posted from your application will show up as "from API" (I believe). You can't put the name of your application in there unless you use OAuth. 4. Basic Auth will eventually be deprecated. If the first three reasons don't convince you, you should give this one serious consideration. :) I have some issues with OAuth, but they're minor and hardly insurmountable. Moreover, if you use a library that handles OAuth for you, implementing it is not a major endeavor. Regards, --Duane On Jul 9, 7:56 am, praveen kumar wrote: > Hi, > > I would like to develop a tool on Twitter, i have few doubts. Please > clarify. > > 1. What is the use of OAuth authorization ? > > 2. From Twitter API we can update tweets without OAuth authorization. Why > this OAuth authorization? > > -- > Regards, > Praveen Kumar .N > Software Engineer > Netelixir e-Marketing Solutions > Hyderabadwww.netelixir.com
[twitter-dev] Re: About OAuth authorization
Thanks Duane for your response. On Thu, Jul 9, 2009 at 8:11 PM, Duane Roelands wrote: > > 1. OAuth allows your user to authenticate without ever exposing his > Twitter credentials to your application. > > 2. OAuth allows a user to revoke your application's access to their > account. > > 3. If you don't use OAuth, tweets posted from your application will > show up as "from API" (I believe). You can't put the name of your > application in there unless you use OAuth. > > 4. Basic Auth will eventually be deprecated. If the first three > reasons don't convince you, you should give this one serious > consideration. :) > > I have some issues with OAuth, but they're minor and hardly > insurmountable. Moreover, if you use a library that handles OAuth for > you, implementing it is not a major endeavor. > > Regards, > --Duane > > On Jul 9, 7:56 am, praveen kumar wrote: > > Hi, > > > > I would like to develop a tool on Twitter, i have few doubts. Please > > clarify. > > > > 1. What is the use of OAuth authorization ? > > > > 2. From Twitter API we can update tweets without OAuth authorization. Why > > this OAuth authorization? > > > > -- > > > Regards, Praveen Kumar
Re: [twitter-dev] Re: About OAuth
* mikesouthern [100904 19:57]: > But ... but ... I'm trying to do a similar kind of thing from a perl > command line. See my reply in an earlier thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/160cb4d3f20ef61 -Marc -- 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
Re: [twitter-dev] Re: About OAuth
I wrote a small PHP script which can be run CLI:
Its at: http://dor.ky/entry/twitter-api-oauth-update-status
If you need any help adapting that to your needs, just pop me an email off list
and I'll be happy to help you.
Scott.
On 5 Sep 2010, at 03:16, mikesouthern wrote:
> But ... but ... I'm trying to do a similar kind of thing from a perl
> command line.
>
> I looked at this on github before, and where it says:
> // Register an application at http://dev.twitter.com/apps and from
> your new apps page get "my access token".
>
> There is no "application" for me to go to in order to get an access
> token. I also need the script to run from a cron scheduler so I can't
> have it stop and ask me for a verification PIN with each run.
>
> Have you come across similar difficulties elsewhere? My searches are
> turning up tantalisingly incomplete and inconsistent code snippets
> that don't work ..
>
> On Sep 4, 5:52 pm, Abraham Williams <4bra...@gmail.com> wrote:
>> Have a look athttp://gist.github.com/564882
>>
>> Abraham
>> -
>> Abraham Williams | Hacker Advocate |http://abrah.am
>> @abraham |http://projects.abrah.am|http://blog.abrah.am
>> This email is: [ ] shareable [x] ask first [ ] private.
>>
>> On Thu, Sep 2, 2010 at 19:50, David wrote:
>>> I found out twitter does not support Basic Auth any, and I wonder how
>>> can I change my code from Basic Auth to OAuth.
>>
>>> and my code like following:
>>
>>> $username=username;
>>>$password=password;
>>>$message=message;
>>>$host = "http://twitter.com/statuses/update.xml";;
>>>$ch = curl_init();
>>>curl_setopt($ch, CURLOPT_URL, $host);
>>>//curl_setopt($ch, CURLOPT_VERBOSE, 1);
>>>//curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
>>>curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>>>curl_setopt($ch, CURLOPT_TIMEOUT, $config->timeout );
>>>curl_setopt($ch, CURLOPT_USERPWD, "$username:$password");
>>>curl_setopt($ch, CURLOPT_POSTFIELDS,"status=$message");
>>>//curl_setopt($ch, CURLOPT_HTTP_VERSION,
>>> CURL_HTTP_VERSION_1_1);
>>>curl_setopt($ch, CURLOPT_POST, 1);
>>>$result = curl_exec($ch);
>>>// Look at the returned header
>>>$resultArray = curl_getinfo($ch);
>>>curl_close($ch);
>>
>>> --
>>> 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 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
Scott Wilcox
t: +44 (0) 7538 842418
+1 (646) 257 0580
e: sc...@dor.ky
w: http://dor.ky
http://synfinaty.com
smime.p7s
Description: S/MIME cryptographic signature
Re: [twitter-dev] Re: About OAuth
On 9/5/10 4:26 AM, Scott Wilcox at sc...@dor.ky wrote: > I wrote a small PHP script which can be run CLI: > > Its at: http://dor.ky/entry/twitter-api-oauth-update-status > > If you need any help adapting that to your needs, just pop me an email off > list and I'll be happy to help you. > > Scott. Thanks Scott I appreciate you taking time to reply. I'll grab the script and see how I can adapt it. Mike -- 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: About OAuth of Twitter
Ok, I see. thank you for your reply. On May 27, 3:20 pm, Taylor Singletary wrote: > You're safe to continue using the non-api-subdomain version of OAuth for > awhile longer (it won't disappear on June 30th), but we recommend switching > to using the api subdomain (and SSL!) pro-actively in the event we decide to > be stricter here in the future. But we have no immediate plans to invalidate > such requests at this time. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Thu, May 27, 2010 at 3:17 PM, emagic wrote: > > We use OAuth login in our application for a long time, but the links > > are sth. like: "http://twitter.com/oauth/request_token";, and we just > > found the new one should be sth. like " > >http://api.twitter.com/oauth/request_token";. > > It seems what we have now is OAuth 1.0A as mentioned in documents. We > > are not sure what should we change to avoid broken after June 30th. > > Any suggestions? Thank you.
