[ajays]

It can be easily done; but I think the problem here is that if you're using the Twitter API (as is the case with the link you mentioned), you are required to honor deletion requests. If you don't, then your access is revoked, which is what happened in this case.

Now, you could just archive the tweets internally and reveal them under some other name...

[A_COMPUTER]

The choke point seemed to me to be that they end up notifying you of it via...twitter. You can go to their site and still see deleted tweets. If you weren't putting them back up on Twitter, you could easily monitor politician tweets and never get caught by Twitter.

How do archive sites and sites like Storify get away with storing deleted tweets? Storify even lets you repost your stories on Twitter.

[cinquemb]

Then again, with the thousands, if not tens of thousands of oauth credentials checked in on public github repos, I don't really see that revoking access to one credential as a major bottle neck.