StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5691528
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-17T04:41:54.187
FavoriteCount
0
LastActivityDate
2014-12-23T09:56:51.057
LastEditDate
2014-12-23T09:56:51.057
LastEditorUserId
2427542
OwnerUserId
210774
ParentId
5680552
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
One approach would be to use the <a href="https://dev.twitter.com/streaming/reference/post/statuses/filter" rel="nofollow">streaming API</a> (or perhaps the more specific <a href="https://dev.twitter.com/streaming/userstreams" rel="nofollow">user streams</a>, if that's better suited to your application) to start collecting all tweets as they occur from your target user(s) without having to bother with the traditional rate limits, and then use the REST API to backfill those users' historical tweets. Granted, you only have 350 authenticated requests per hour, but if you run your harvester around the clock, that's still 1,680,000 tweets per day (350 requests/hour * 24 hours/day * 200 tweets/request). So, for example, if you decided to pull 1,000 tweets per user per day (5 API calls @ 200 tweets per call), you could run through 1,680 user timelines per day (70 timelines per hour). Then, on the next day, begin where you left off by harvesting the next 1,000 tweets using the oldest status ID per user as the <code>max_id</code> parameter in your <a href="http://dev.twitter.com/doc/get/statuses/user_timeline" rel="nofollow">statuses/user_timeline</a> request. The streaming API will keep you abreast of any new statuses your target users tweet, and the REST API calls will pretty quickly, in about four days, start running into Twitter's fetch limit for those users' historical tweets. After that, you can add additional users to fetch going forward from the streaming endpoint by adding them to the <code>follow</code> list, and you can stop fetching historical tweets for those users that have maxed out, and start fetching a new target group's tweets.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POgetting all tweets of a twitter user, rate limit problem
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USaspiring_sarge
UserOwnerUserId
1. USarcain
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.