Simply awesome...great effort !
--
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:
No he means each source is a user and has its own account, and
authorizes the single app for separate access tokens..
However, my question is, is not having aliases a btter solution for
this? In other words, on user having several aliases, each alias being
permitted to get separate access tokens
permitted to get separate access tokens for the same app?
Regards,
Shob
On Aug 11, 2:04 pm, Jacky jaga...@gmail.com wrote:
No he means each source is a user and has its own account, and
authorizes the single app for separate access tokens..
However, my question is, is not having aliases a btter
No its not, and I wish it was allowed/supported...
On Aug 11, 2:09 pm, Skygazer marc.bouc...@gmail.com wrote:
That makes sense to me but that's not supported at this time from my
understanding.
On Aug 11, 5:04 pm, Jacky jaga...@gmail.com wrote:
No he means each source is a user and has its
I am trying to get everybody who wants to test using this Mozilla REST
client, so we can have a common baseline, we can narrow source of
errors.-copy and past header here and POST
https://addons.mozilla.org/en-US/firefox/addon/9780/
Shob
On Aug 4, 9:19 am, Ben Jones
just watch the timestamps...
On Aug 4, 12:58 pm, Jacky jaga...@gmail.com wrote:
I am trying to get everybody who wants to test using this Mozilla REST
client, so we can have a common baseline, we can narrow source of
errors.-copy and past header here and POST
https://addons.mozilla.org/en
Works well...helps you crosscheck...and narrow your source of error
On Aug 2, 9:46 pm, Jacky jaga...@gmail.com wrote:
Amy users using this REST client to test OAuth header
https://addons.mozilla.org/en-US/firefox/addon/9780/
so we can have a common base to check against
Also,
OAuth
oauth_consumer_key=
instead of
Oauth
oauth_consumer_key=...
in the authorization header as per Taylor, thanks...
Amy users using this REST client to test OAuth header
https://addons.mozilla.org/en-US/firefox/addon/9780/
so we can have a common base to check against
It might be a good idea to be able to use this REST client for all
commands as a test benchmark for Twitter API calls(just a thought)...
(I have not tested much on this yet, I am just looking at it)...
https://addons.mozilla.org/en-US/firefox/addon/9780/
Shob
On Jul 8, 1:22 pm, Jacky jaga
to compare to the results you
are getting from your function.
Hope that helps,
Matt
On Tue, Jul 6, 2010 at 7:10 AM, Jacky jaga...@gmail.com wrote:
Hullo,
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key
%3DhUMUUZO3Zx9zNzJ9DghcA
heavy lifting for you so you can develop an
application for use with Twitter quickly. If you then want to roll your own
solution you could use the TwitterVB library to compare to the results you
are getting from your function.
Hope that helps,
Matt
On Tue, Jul 6, 2010 at 7:10 AM, Jacky jaga
12 matches
Mail list logo
