I figured out the problem. The tweetstream RubyGem is using the function URI.encode on passwords. If you have punctuation in your password like any good, security- conscious developer would, then tweetstream will make your password invalid. Also, it will not produce any sort of error -- it will simply sit and do nothing (which may or may not be due to how the API is implemented from Twitter's side).
The short-term solution is to simply change your password and make it URL-safe. On Dec 28, 3:02 am, MikeJ <architeuthis...@gmail.com> wrote: > I hope this is a simple question. I am writing some code for the > stream API using the tweetstream RubyGem. It works perfectly for my co- > worker and works for me when I use his login, but when I use my own > personal login, or a new login I created just for streaming, it does > not work -- no errors, no limit message, but no tweets are seen. He > suggested that I needed to create at least one app -- maybe that would > register my account as a developer account -- but I tried it and it > didn't change anything. Any suggestions? -- 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
