Created
October 25, 2011 14:41
-
-
Save pkarl/1312964 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $.get('https://api.twitter.com/1/statuses/mentions.json?include_entities=true', {'since_id':'1234'}, function(data){ | |
| // parse that shit | |
| // insert that shit | |
| }); |
Author
Polling every 30 seconds. Mentions are a rarer creature. We can insert as
they come in. The order doesn't need to be precisely important. We can lose
them on refresh.
We're storing IDs in the active list, so we can pull every mention (after a
since_id) from twitter, and compare against what's already there to keep
from inserting dupes. Obvs some waste there, but we'll be paid in smiles.
…On Tue, Oct 25, 2011 at 10:45 AM, Steve Losh < ***@***.***>wrote:
How often do we poll? Does it insert that shit in order or just stick it
at the top?
Needs to check for tweets that were already pulled down by the server, and
also needs to add code to the current tweet-rendering stuff to check for
duplicates as well.
What about when they refresh the page? Don't worry about old replies?
##
Reply to this email directly or view it on GitHub:
https://gist.github.com/1312964
Sounds good -- go for it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How often do we poll? Does it insert that shit in order or just stick it at the top?
Needs to check for tweets that were already pulled down by the server, and also needs to add code to the current tweet-rendering stuff to check for duplicates as well.
What about when they refresh the page? Don't worry about old replies?