2010/3/23 grantcv1 <grant...@gmail.com> > I want to programmatically log into twitter periodically and update my > status. This will happen a few times a day from my server without any > user interaction. In order to do this, I need my server-based app to > authenticate itself with twitter using my login credentials. >
If you want a *real* easy way: http://www.commandlinefu.com/commands/view/176/update-twitter-via-curl Not sure what the equivalent in OAuth style would be, but I'd like to see it! > > It seems I have two choices. First, I can take the easy route and use > basic authentication, but this is considered bad practice at this > point in time. The second and apparently preferred approach is to use > OAuth. So I have spent the past day learning what I can about OAuth. > While I have learned loads about who created OAuth, what the history > of the name is and that it is a "double entente" [sic - it's double > entendre]. I have read beginners guides only to find that they are > obsolete or authoritative gruide's only to find they are incomplete. > All in all, I feel I have read about a lot of things, but in the end I > haven't learned much at all. > > What I have learned is that, if this is to work at all, it will > require the two-legged model rather than the three-legged model. I > have struggled to find very much information about the two-legged > model or get any confirmation that twitter even supports this. I did > find what I believe to be the original spec for this model and it > seemed to indicate that the model was simpler than the three-legged > dance. It apparently requires the consumer key and consumer secret but > no token key or token secret. I guess that the consumer key and secret > is adequate to authenticate the application - and somehow maybe the > app is associated with the twitter account so that is good enough. > [???]. > > So I registered my app with twitter, got the consumer key and > consumer secret, found a library to work with, and set about trying to > get something to work, But alas, all I seem to get is a login popping > up at me and then nothing. > Am I on the right track? Or should I just abandon an effort to follow > best practices and instead do the simpler thing? > > -- > You received this message because you are subscribed to the Google Groups > "OAuth" group. > To post to this group, send email to oa...@googlegroups.com. > To unsubscribe from this group, send email to > oauth+unsubscr...@googlegroups.com <oauth%2bunsubscr...@googlegroups.com>. > For more options, visit this group at > http://groups.google.com/group/oauth?hl=en. > > -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.