Correct, I still had the issue when escaping "track=...". Escaping
params individually did not work either. Still able to tweet though...
Maybe it is a hint at the trouble being more/different than double
encoding?

Cheers,
Bradley

On Oct 25, 4:59 pm, Ciaran <ciar...@gmail.com> wrote:
> On Mon, Oct 25, 2010 at 10:53 PM, bradley.meck <bradley.m...@gmail.com> wrote:
> > So in my case i just encodeURIComponent somewhere? I tried on the POST
> > params and it did not work, nor did the 4 permutations of api-key/
> > secret and access-token-key/secret.
>
> Odd, Escaping "track="+tracking.join(",")+"&count=0" should work ?
> -cj.

-- 
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