I'm an early beginning myself.
you can try following the stream of a hashtag at
http://stream.twitter.com/1/statuses/filter.json?track=%23DamnItsTrue
for #DamnItsTrue
It require basic authentication with a valid twitter account
On Aug 10, 12:31 pm, deepa wrote:
> can anyone post the sample usi
can anyone post the sample using streaimg API..
im not gettng how to start with this...
--
Have you visited the Developer Discussions feature on
https://dev.twitter.com/discussions yet?
Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitt
On Fri, Nov 12, 2010 at 11:31 PM, dan wrote:
> By ui-encoding you mean percent-encoding?
I did mean uri-encoding ;) iphone's suck :)
-cj.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracke
The differences between "+" are "%20" are subtle.
When you are using + instead, it *should* still work as long as + is
represented in your signature base string as: %2B
Are you able to see what + yields in your signature base string?
A little background on the difference between + and %20 in URL
By ui-encoding you mean percent-encoding?
On Nov 10, 3:38 am, Ciaran wrote:
> Try ui-encoding them first, my understanding of the Twitter OAuth
> signature validation is that it is non-standard (although there
> appears to be debate about this) I suspect if you encode them first
> before signing
Taylor,
Thanks for your response. The crux might be
> Normalizing spaces to %20, and avoiding "+" is also a best practice.
tweetstream4j uses Apache's HttpClient 4.0 (see
http://hc.apache.org/httpcomponents-client-ga/index.html). I believe
if a request has application/x-www-form-urlencoded param