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

Querying strategy for @NiemanLabFuego tweets? #22

Open
scarothers opened this issue Feb 15, 2015 · 2 comments
Open

Querying strategy for @NiemanLabFuego tweets? #22

scarothers opened this issue Feb 15, 2015 · 2 comments

Comments

@scarothers
Copy link

Hiya. I've been having some fun setting up OpenFuego instances, and have a question about the Twitter account @NiemanLabFuego

I've always really found that account useful, so want to set one up in conjunction with my Fuego pages.

My question is: How often do you query to get the right mix of tweets? How many does it request?

I have a cron job set up that, every half hour, looks for the 1 most popular link over the past 6 hours, and if it's new, tweets that out. (Scoring, metadata set to true). It's ok, but seems like it's not quite right ...

Would love to know how the official account queries! Thanks for any info.

@jbenton
Copy link
Member

jbenton commented Feb 16, 2015

Hi Sara! @phelps coded that up, so I'm not 100% sure, but I believe it's triggered whenever a link is in the top 3 of the past 24 hours. (I feel quite confident about the top 3 part, not as much about the 24 hours part.)

@scarothers
Copy link
Author

Thanks for the info! I tried that over the past few days, seems like it's on the right track. I'm still getting a lot of links over a 24-hour period that break into the top three (so that means more tweets than the Nieman Lab version, which seems to dull the importance of each one, if that makes sense.). Makes me think it's symptom of the universe I'm following, so am going to try tweaking that.

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

No branches or pull requests

2 participants