Twitter API Question posted in
The official Twitter API documentation can be found here.

Can Twitter's Streaming API be safely deployed client side? – Twitter API

I’m trying to develop an open source solution which will be deployed on Raspberry Pi’s or similar SBCs. The RPi part is only relevant insofar as it means all the code and app resources need to be publicly available.

The solution needs to read Twitter statuses, as close to real time as possible, and with as little interference from third parties as possible. I found Twitter’s Streaming API, which is blazingly fast, and would be perfect for my application – except it requires OAuth. And as far as I can tell, the OAuth mechanism isn’t well suited for deployment on users’ machines, since it relies on a secret key which belongs to the application owner (the consumer secret).

I couldn’t find any easy way around this – the only solutions I could think of are either handling request signing on a central server, or asking each user to create their own Twitter app account. And I find both solutions terribly distasteful.

Do you see any elegant way out?

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    It turns out this is indeed not currently feasible cleanly with any of Twitter's public APIs; not now, and not in the foreseeable future. Refreshingly, for once we do have proof for a negative: I also asked this on Twitter's own forum, and I was lucky enough to have my question kindly answered by Andy Piper, Global Lead Developer Advocate at Twitter. There you go.


  2. 0

    Your app can open a web browser with Twitter’s application authentication webpage loaded. When the user enters their credentials Twitter will return a code which they can copy/paste into your app. It’s not particularly elegant. Here is a Python example of the workflow: https://github.com/geduldig/TwitterAPI/blob/master/examples/oauth_test.py

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search