Hey,
I've been experimenting with the streaming API for the past couple of days. While playing with different methods, I've discovered an interesting phenomenon -
This has to be something trivial - I can't imagine this being a bug on twitter's side, as I'd expect this scenario to be used extensively. When I use basic auth, everything works well, hence this must be a bug with OAuth. When generating a signature, the library I am using is encoding "," as %252C which I initially thought might be wrong, but after studying the OAuth specs, seem to be correct.
Thanks,
jan