Open milespomeroy opened 12 years ago
Thanks for reporting!
The problem with the HTTPS connection is that there was never an official update release from the twitter-node library that included the fixes to actually use HTTPS. Which is exactly why the example code includes a vendored version of it. The problem I have with the code that uses ntwitter is that users must have full OAuth credentials at the ready, which significantly increases the entrance barrier to using the code. Currently Twitter doesn't seem to have any specific plans to deprecate Basic Auth for the streaming API, so I'd rather stick to something that requires just the username and password.
I'm open to suggestions. twitter-node is obviously abandoned by now, but it still sort of works, unfortunately not when installed globally via npm.
as a point of reference, i just did a git clone on your repo, and ran twitter-riak.js without an issue.
Tried running
twitter-riak.js
it failed without an error. I installed thetwitter-node
andriak-js
modules globally and changed the script to reference those and then it failed with,ECONNREFUSED
. It seems to be related to thetwitter-node
module and recent changes to the twitter streaming api. I ended up usingsethew
's fork and, with some twitter api tokens, got it working: https://github.com/sethew/nosql-handbook-examples.git