One implementation option you have is to build only the portions of OAuth
that you need to meet your goals. On dev.twitter.com we provide a feature
that allows you to retrieve the access token for your own account, owning
the application. You would then hard code this access token and your API
keys
On 8/11/10 6:30 PM, ERenken wrote:
> So how can I use OAuth on a hardware device we are creating that
> doesn't have a UI? Can I share the key between all the devices? This
> is only twittering to 1 account that we have created. Seems like
> OAuth is going to make stuff like this harder for peop
So how can I use OAuth on a hardware device we are creating that
doesn't have a UI? Can I share the key between all the devices? This
is only twittering to 1 account that we have created. Seems like
OAuth is going to make stuff like this harder for people to develope.
Seems like it would have ju
