The oauth_single_token isn't really a feature -- it's just a demonstration
of how you would go about it if that was your use case.
The usage of a stored access token is the same in most implementations,
whether you got that single access token through the feature on
dev.twitter.com or you got the access token by performing the OAuth token
negotiation dance -- with most OAuth libraries, you still instantiate an
access token object the same way -- you might be pulling the token from a
database in context to a user using your application instead of having it
For those that do have a single-user use-case, usually people who've written
an application mainly for their own research purposes, it's a quick and easy
way to skip over the hardest part of implementing OAuth and instead skip
right to the part where you're making resource requests.
But the pattern is the same regardless of how you got the access tokens.
Some libraries might obfuscate or simplify the process, but under the hood
they are doing very similar operations.
Developer Advocate, Twitter
On Sun, May 9, 2010 at 11:58 AM, Eric <eric.gaygesh...@sbcglobal.net> wrote:
> Is the point of oauth_single_token that you can only work with a
> single account? Meaning if I have a feature on my site, I can't use
> this library to interact with the users accounts, I can only use this
> library to work with my own, or one account?
> Much appreciated!
> On May 3, 2:35 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > You can checkout this page describing using a script to post to a single
> > Twitter account:http://dev.twitter.com/pages/oauth_single_token
> > One of the examples is for my PHP library:
> > Abraham
> > On Mon, May 3, 2010 at 13:04, YCBM <youcannotb...@gmail.com> wrote:
> > > Hi Paul,
> > > Posting status updates using Basic Auth like that won't work any more
> > > after 6/30. You'll need to use a PHP oAuth class (there are a few of
> > > them athttp://dev.twitter.com/pages/oauth_libraries#php) as well as
> > > register an oAuth app.
> > > Best,
> > > Y
> > > On May 3, 3:17 pm, "Paul A." <hellodev....@gmail.com> wrote:
> > > > Hi guys,
> > > > Quick question that "hunts" me and can't find an answer.
> > > > I'm using this line of code to post tweets to my account direclty
> > > > from my website
> > > > $host = "http://twitter.com/statuses/update.xml?
> > > > status=".urlencode(stripslashes(urldecode($message)))
> > > > and posting it with curl with my user/password
> > > > Will this still going to work after Twitter upcoming June
> > > > for Oauth. It's unclear to me.
> > > > Thanks, Paul
> > --
> > Abraham Williams | Developer for hire |http://abrah.am
> > @abraham |http://projects.abrah.am|http://blog.abrah.am
> > This email is: [ ] shareable [x] ask first [ ] private.