My users are complaining about the same thing.

On a perfectly valid tweet, the system kicks back an error that
basically says the status parameter was empty.

I cannot provide more debug information because I cannot reproduce the
error at will. It is completely unpredictable.


On Sep 26, 4:28 pm, Marco Kaiser <> wrote:
> Hi,
> we've received reports from users that posting a status update returns an
> error 403 and a message saying that
>  Client must provide *a* 'status' *parameter* *with* *a* *value*
> A quick search on this shows that not just our clients, but others are
> affected, too (e.g., people were reporting it for DestroyTwitter, Tweetie
> and Echofon):
> Anyone has input on this?
> Thanks,
> Marco

Reply via email to