Oh,
On Fri, Apr 10, 2009 at 8:48 PM, Dominik Schwind wrote:
["body:protected"]=>
> string(60) " � sK��IMQ(�W(K��LI,IU�O,-�P(�L�K,)- ��٩y0y(�+" }
That gibberish is just a gzip version of:
string(43) "Failed to validate oauth signature or token"
Thx,
Dominik
Hi,
I'm seeing it on two applications "EagleTweet" and "EagleTweetDev" - I
am using the Zend_OAuth library for PHP and I'm updating location
fields for roughly 100 users with their FireEagle location once in a
while. You can see it at http://eagletweet.com/ and I can give you the
API Keys in priv
Before opening an issue [1] it would have been nice to discuss. What are you
trying to do? What steps have you taken to debug? Why do you think this is
on our end and not a bug in your code? We can't help without knowing what's
going on.
1. http://code.google.com/p/twitter-api/issues/detail?id=447
I;ve created an issue,.. can you all comment there too?
http://shortr.me/lz
On Apr 10, 12:19 pm, Dominik Schwind wrote:
> Hi everyone,
>
> since about half an hour ago I seem to be getting 401 Unauthorized
> responses to my OAuth-ed API calls.
>
> Is that a known problem?
>
> Regards,
>
> Do
Guys,
Details are essential to help track down claims like these. What are you
doing, and more importantly, how are you doing it?
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Fri, Apr 10, 2009 at 6:48 AM, Bluespark wrote:
>
> Same here.
>
> On Apr 10, 10:19 pm, Dominik Schwind
Same here.
On Apr 10, 10:19 pm, Dominik Schwind wrote:
> Hi everyone,
>
> since about half an hour ago I seem to be getting 401 Unauthorized
> responses to my OAuth-ed API calls.
>
> Is that a known problem?
>
> Regards,
>
> Dominik
