It should affect and I wonder if John has any upgrade in mind. Now that API 1.0 is scheduled for retirement on
May 7, yourTwapperKeeper will need some adjustments to work. You can see that
yTK code makes calls at
search.twitter.com/search and after May 7 all requests to
search.twitter.com/search will receive HTTP 410. Apparently we'll have to move to GET search/tweets instead, but I'm afraid there are other parts of the code that also require amendments. Let's hope John is checking this group periodically and has a solution in mind.
Cheers,
Marco