our membership to this group:
>> http://groups.google.com/group/twitter-development-talk?hl=en
>>
>>
>
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhanceme
; not authorized for the client registered to 'http://
> www.mymobileplanet.co.uk'.
>
> I have tried several methods to somehow make it work but all in vain.
>
> I would appreciate if someone can visit my pages and see what the
> problem is or guide me how I can make it
appears to impact the Twitter web interface.
>
> Is it just me seeing this bug? Is there any information on the issue?
>
--
Dana Contreras
Twitter Platform Team
http://twitter.com/DanaDanger
quot;Not found"}
>
> Now on the web, this is fine:
> http://twitter.com/twitterapi/status/15738870223
>
> I tried removing the id as post data, but then I got an invalid signature
> error. Any ideas?
> Thanks,
> Jim Cortez
>
--
Dana Contreras
Twitter Platform Team
http://twitter.com/DanaDanger
...and I see Taylor beat me to it. ;)
On Fri, May 21, 2010 at 10:34 AM, Dana Contreras wrote:
> When you're constructing your signature base string, don't include the
> query parameters in the URL. The query parameters do need to be
> included in the next part of the signature
t;,oauth_nonce="r3cy0enwrqeq1qns",oauth_signature_method="HMAC-
> SHA1",oauth_timestamp="1274461098",oauth_token="823083-
> ***",oauth_version="1.0",oauth_signature="dGhefwoSaiSQ0XMSswJ1UdPtkeI
> %3D"
> Connection: keep-alive
> Host: api.twitter.com
>
>
> Any ideas on what I am doing wrong?
>
>
--
Dana Contreras
Twitter Platform Team
http://twitter.com/DanaDanger
Oauth, I'm absolutely not a web developer in
> any sense of the word, and I'm wondering how I preserve the
> functionality of these tools across the pending changes.
>
>
> Any thoughts on how to provide a construction kit for command line/
> daemon users would be appreciated.
>
--
Dana Contreras
Twitter Platform Team
http://twitter.com/DanaDanger
t, exposing this type of information is valuable to
> the user, but user objects (not ids) would be required to create a UI
> for someone to view and then interact with such requests.
>
> --Naveen Ayyagari
> @knight9
> @SocialScope
>
>
> On Apr 13, 7:32 pm, Dana Contreras wrote
Limit headers document the standard REST
API rate limit. Both sets of headers will be sent in response to calls to
users/search.
You can find more information about this update here:
https://apiwiki.twitter.com/Rate-limiting
--
Dana Contreras
Twitter Platform Team
http://twitter.com/DanaDanger
-
itter-REST-API-Method%3A-friendships-incoming
https://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friendships-outgoing
Enjoy!
--
Dana Contreras
Twitter Platform Team
http://twitter.com/DanaDanger
Change the method from POST to GET.
On Wed, Apr 7, 2010 at 9:21 AM, Nitin wrote:
> Hi All-
>
> I've been trying to get read the friends timeline using Oracle PL/
> SQL's UTL_HTTP method but for some reason it throws a "HTTP client 400
> - Bad Request" message at line #19 - line with the get_res
11 matches
Mail list logo