Skip to content

Issues: technoweenie/twitter-node

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11 Open 8 Closed
11 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Multiple instance issue
#27 opened Jun 3, 2012 by abhisheksoni
calling twit.stream(); from within a function gives a connection refusal
#24 opened Dec 14, 2011 by anthonywebb
2
TypeError: Object #<Object> has no method 'createClient' after npm update
#18 opened Oct 7, 2011 by itwars
3
Connection refused
#17 opened Oct 5, 2011 by NHQ
7
what should i do when a twitter-node disconnects from the firehose?
#13 opened Jun 22, 2011 by fat
1
Updating filter should follow Twitter's predicates
#12 opened May 26, 2011 by AfraidOfMonsters
1
Error: Cannot find module 'twitter-node'
#11 opened May 11, 2011 by cocodrino
1
install fails
#10 opened Mar 27, 2011 by cedricpinson
reconnect on failure ?
#6 opened Oct 5, 2010 by friggeri
4
EPIPE when following lots of users
#5 opened Sep 1, 2010 by elliottkember
.end() isn't always called on previous stream when .stream() is called
#4 opened Apr 28, 2010 by ptarjan
2
ProTip! Updated in the last three days: updated:>2024-12-01.