Well, like I said, I'm using Phirehose, which does all of that for
you .... But, based on what you said, I hacked into Phirehose's code
and did an echo of the output of the POST data to the console, and
that enabled me to figure it out.

Phirehose takes an array, then converts it via implode into a comma-
delimited string ... but since I'm storing the list in a flat file
(for caching purposes) and reading in via file() - to get an array -
each value also contained the newline character, which was getting
encoded into the comma-delimited array.

I did      array_map("trim",$array);   to fix it ....

thanks...



On Oct 22, 3:45 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Can you share the executed URL you used for the request, the POST body, and
> the OAuth authorization headers and signature base string? It's possible
> there's an encoding issue with your commas or otherwise.
>
> Thanks,
> Taylor
>
> On Fri, Oct 22, 2010 at 11:18 AM, AdamW13 <adam...@gmail.com> wrote:
> > attempting to use streaming API - with Phirehose ...
>
> > Twitter is throwing back the following error:
>
> > ERROR 406: Not Acceptable (Parameter follow has unparseable items
> > 140501028).
>
> > That ID is the first in my list - but doesn't seem to have anything
> > wrong with it. ... The list is about 70 long - separated by commas, as
> > it's supposed to be ...
>
> > I cannot make sense of that error message.  What is unparseable about
> > a comma-separated list of integers?
>
> > --
> > 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:
> >http://groups.google.com/group/twitter-development-talk

-- 
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: 
http://groups.google.com/group/twitter-development-talk

Reply via email to