Alex, I finally figured this out. As you probably guessed, was not an issue with the Twitter API.
In case someone else winds up on this thread, here's what the issue ended up being: When using PHP CURL and doing a POST (vs. a GET), there are two ways to pass in the POST parameters. One is as a A=B&C=D string. The other is to use an associative array. As it turns out, there's some issue with using the associative arrays when there is an @ symbol as the first character. There's likely a simpler explanation, but I don't know what it is. Simply switching to using a URL encoded parameter string fixed the problem. Thanks, and sorry for the false alarm. Regards, Dharmesh On Nov 15, 3:47 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > Could you please provide an example of the failing request and response? > > On Fri, Nov 14, 2008 at 23:56, Dharmesh <[EMAIL PROTECTED]> wrote: > > > I'm having an issue posting status updates that start with an > > @someone. > > > Posting updates that are not @someone replies seem to work just fine. > > > The error occurs when updating with an [EMAIL PROTECTED] to users that are > > followers and not followers. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
