You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would simplify the code quite a bit if twarc simply wrote tweets to stdout and let the user decide what file they should go.
When run repeatedly twarc tries to determine the since_id to use when talking to the Twitter API based on data that has already been archived. But this functionality is dependent on twarc being run in the same directory as the other archive files, and the filenames matching a particular pattern (which can get ugly). The determination of the since_id isn't working properly with files created with --stream since they are ordered differently.
I propose this logic is removed and we add a --min_id option to match --max_id. The user can then control what they want to do, and where the data goes.
The text was updated successfully, but these errors were encountered:
I think it would simplify the code quite a bit if twarc simply wrote tweets to stdout and let the user decide what file they should go.
When run repeatedly twarc tries to determine the since_id to use when talking to the Twitter API based on data that has already been archived. But this functionality is dependent on twarc being run in the same directory as the other archive files, and the filenames matching a particular pattern (which can get ugly). The determination of the since_id isn't working properly with files created with --stream since they are ordered differently.
I propose this logic is removed and we add a --min_id option to match --max_id. The user can then control what they want to do, and where the data goes.
The text was updated successfully, but these errors were encountered: