Hi Diogo,

If you're intent is to provide access to multiple users for the same Twitter
account, at this time it'd be best for you to obtain an access token for the
Twitter account and your application (we offer a feature on
dev.twitter.comthat makes this very easy, you can find it in the
sidebar while viewing one
of your applications: "My Access Token") and hard code that into the
application. That way, all API actions taken in your application will be on
behalf of the single user.

Tom: Contributors as an API hasn't been fully baked yet and is still in very
limited rollout.


On Tue, Aug 10, 2010 at 8:08 AM, Tom van der Woerdt <i...@tvdw.eu> wrote:

> On 8/10/10 3:29 PM, Diogo wrote:
> > Hello, I'm developing a system for a company where the employees can
> > read and answer tweets from a single account. It is working, but not
> > using oAuth. I read that Twitter will no longer support the basic
> > authentication.
> > The question is, if I change the authentication to oAuth, everybody
> > will have to know the username and password of Twitter account and
> > sign in manually to begin work?
> No. With oAuth, you get a pair of keys. You can change these keys at any
> time (assuming that you only use your own keys, and don't provide the
> login system which OAuth allows) and they can only be used in
> combination with your own application.
> Tom
> PS: Maybe someone else can answer this: I've seen <contributors> in some
> tweets, is this a feature which is already available to us? Haven't seen
> it on the api wiki...

Reply via email to