At present we collect the most recent ~2000 tweets from each user, per Twitter API limits. This can give an uneven approximation of a community, since it does not represent "recent" interactions in a true time sense, and will include the most recent tweets from a user even if they haven't tweeted in months.
Propose adding a --maxage-A flag to the script for specifying an integer (or float?) number of days. No tweets older than this threshold will be collected.
At present we collect the most recent ~2000 tweets from each user, per Twitter API limits. This can give an uneven approximation of a community, since it does not represent "recent" interactions in a true time sense, and will include the most recent tweets from a user even if they haven't tweeted in months.
Propose adding a
--maxage
-A
flag to the script for specifying an integer (or float?) number of days. No tweets older than this threshold will be collected.Implementation will require adding optional
oldestDate
argument toacquireTweets
, which can take an epoch time stamp. If any tweets older than that timestamp are detected, break out of the for-loop currently at: https://github.com/DaylightingSociety/SocMap/blob/c8e9f40efdcee2c765cd02b6398d948fecf6bd83/acquire.py#L101-L113This will not require any changes to analysis.py, or auxiliary tools, or any new interactions with tweepy.