Oh right, understood. I was already thinking about logging in once,
storing the credentials and using them over and over again until they
expire. Then what you suggest is the way I'll go. Thank you for your
quick reply!

On Sep 20, 5:19 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> The login procedure is used to generate credentials for the user. Since
> these credentials don't expire, you can simply use them in your script.
> In fact, Twitter provides these credentials (for the application owner
> only) on a page on dev.twitter.com, to make it even easier to implement.
> Simply use those credentials instead of the whole authentication dance ;-)
>
> Tom
>
> On 9/19/10 10:30 PM, Dave wrote:
>
>
>
> > Hi everybody,
>
> > we run a big community website which has a shoutbox. We have a Twitter
> > account, and every shout in the shoutbox appears as a status update on
> > our Twitter stream. This was pretty easy to accomplish with using the
> > old authentication methods. I've been reading a couple of documents on
> > OAuth and Twitters implementation of OAuth, and it seems the new way
> > of authenticating always involves users having to authenticate with
> > their own Twitter account. In our case though, we're publishing the
> > posts of all our users on one account. Also only we have the
> > credentials for this account and we of course we don't want to
> > redirect every user on our site through the Twitter authentication
> > process. The way it was and we'd like it to stay is that when one
> > posts a shout in the shoutbox, the status of our Twitter account gets
> > updated.
>
> > Is this possible with the new authentication methods? Have I been
> > missing something there?
>
> > Thanks in advance for helping me out.
>
> > David

-- 
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

Reply via email to