Skip to content
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.

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

IRC-Bot: Show tweet level in the topic #10

Open
thejh opened this issue Aug 22, 2011 · 8 comments
Open

IRC-Bot: Show tweet level in the topic #10

thejh opened this issue Aug 22, 2011 · 8 comments
Assignees
Labels

Comments

@thejh
Copy link
Contributor

thejh commented Aug 22, 2011

Would be nice to have something like "tweet level: 2" (for magnitude 2, just an example) in the topic.

@ghost ghost assigned AvianFlu Aug 22, 2011
@thejh
Copy link
Contributor Author

thejh commented Aug 22, 2011

For this, the bot needs to be chanop, and for that, it needs to be registered.

@AvianFlu
Copy link
Contributor

I don't understand what you mean. Are you talking about the volume? The volume is auto-set based on channel activity, and has a hard cap - the bot is allowed five tweets, and then gets one more tweet back every seven minutes, so to speak. It takes ten messages in the channel in a minute before the bot reaches zero volume. These numbers were chosen for a different twitter feed in a different channel, and can be tweaked in any way desired. The volume, however, updates too quickly for putting it in the topic to be realistic. We'd be seeing the topic change every time someone spoke.

@thejh
Copy link
Contributor Author

thejh commented Aug 22, 2011

I'm not talking about the output volume. I'm talking about the incoming volume level, e.g. "500 tweets per minute about earthquakes although 3 are normal" would get transformed to a volume level of log2(500/3), so the bot would put "Twitter emergency tweet volume: 7" or so in the topic.

@AvianFlu
Copy link
Contributor

I understand. We're still talking about ~50 tweets a minute, so we need to decide how often we want the topic updated. Topic updates will take up a lot more visual space than the tweets did when the room is quiet.

@thejh
Copy link
Contributor Author

thejh commented Aug 22, 2011

Hmm, this is more complicated than I thought. :(

@AvianFlu
Copy link
Contributor

Yeah, filtering good information out of a heavy twitter stream is non-trivial. Improving our list of tracking terms will help.

@mmalecki
Copy link
Contributor

@AvianFlu First thing we should do should be to look for duplicates, and this should be easy.

@AvianFlu
Copy link
Contributor

https://github.com/hookio/twitter/blob/master/lib/twitter.js#L147-162 is already in play with a distance threshold of 30 and a history of the last 100 tweets. We can certainly tighten the distance, and we can add checking for duplicate links, although the latter is made somewhat useless by shortlinking services. Any other thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants