Open GoogleCodeExporter opened 8 years ago
The problem with that is authentication. The major part of implementing
Twitters API is not the REST API but OAuth.
Original comment by fredrikj...@gmail.com
on 10 Dec 2010 at 3:15
Original comment by fredrikj...@gmail.com
on 10 Dec 2010 at 3:15
Well, I haven't looked at you implementation of the code yet, but since you
have OAuth implemented for twitter would it be substatially difficult to add
another provider for another api endpoint? And if they didn't use OAuth (which
I suppose they wouldn't need to do to implement the Twitter API, although I was
assuming that they would) could you just fall back on basic auth (for instance).
As I said, I haven't checked out the code yet, and I hope to take a look at it
this weekend - maybe the difficulties will be clearer to me then.
Original comment by cori.sch...@gmail.com
on 10 Dec 2010 at 3:40
It is certainly doable, just not sure how much work it would be. I am currently
using a Twitter lib as well but that might be compatible with other services if
they are mirroring the API.
Original comment by fredrikj...@gmail.com
on 10 Dec 2010 at 4:31
Thanks for adding the twitter API that is the main reason I switched to your
app. It makes tracking and teams much easier!
Original comment by studiopr...@gmail.com
on 1 Feb 2011 at 10:24
Original issue reported on code.google.com by
cori.sch...@gmail.com
on 10 Dec 2010 at 3:06