Skip to content
This repository has been archived by the owner on Jun 25, 2018. It is now read-only.

Feature request: 'archive' should honor deletion #97

Open
za3k opened this issue Dec 13, 2015 · 3 comments
Open

Feature request: 'archive' should honor deletion #97

za3k opened this issue Dec 13, 2015 · 3 comments

Comments

@za3k
Copy link

za3k commented Dec 13, 2015

This is a request to make 'archive' remove tweets on re-running. If that requires checking all accessible tweets, it could be enabled by flag so the default run speed is reasonable.

Use case: Right now I'm using this to archive my friends' twitter, and it's basically making them uncomfortable that posting something online guarantees it will never be removed.

P.S. believe it or not, this is currently the best tool for archiving twitter that I've found.

@negatendo
Copy link
Contributor

This is difficult to do right now because of the way the Twitter api limits the number of tweets the archiver can retrieve. It's possible to have a tweet deleted outside of the range of the tweets received, so the archiver would never know about its deletion.

A different approach might be making something else that "cleans" the archive as a side task. It could check each id in the archive for existence and remove those that are gone.

This is a good point regardless. Twitter says that developers should honor deletions in their applications. Folks rolling out bots for their friends or others should be aware of this issue.

@za3k
Copy link
Author

za3k commented Jan 21, 2016

Honoring deletions only within the 30,000 tweet archive limit would not be too bad of a compromise for me--I think most tweets get deleted within a day or two, except in cases where someone is closing their entire account.

@negatendo
Copy link
Contributor

The limit is more like 3,200 tweets, by the way! Mentioned here: https://dev.twitter.com/rest/reference/get/statuses/user_timeline

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

No branches or pull requests

2 participants