PyTwerp vs latest Twitter API change ("since" param)

0 views
Skip to first unread message

vlb

unread,
Apr 10, 2009, 3:16:56 PM4/10/09
to twerp
(reposting with a more appropriate subject)

As far as I can tell, Twitter's recent removal of the since parameter
and If-Modified-Since header
support for timeline methods has broken pyTwerp.

http://groups.google.com/group/twitter-api-announce/browse_thread/thread/76de3c01bdadc209

At least, my guess is that this is the problem as PyTwerp is now
getting the same stream over and over and over again, apparently
ignoring the fact that I just downloaded those posts 10 minutes ago. :-
(

Is there something I can do to patch my copy of PyTwerp?

Decklin Foster

unread,
Apr 10, 2009, 3:34:21 PM4/10/09
to twerp
Unfortunately, this is true. I have been using tircd myself these days,
but I did vote in the dev poll since I remembered this was how twerp
kept track of read state (apparently we were in the minority -- I think
this was a lame move on Twitter's part but oh well). It could be patched
to save a status ID instead of a date string. I don't have time to do
this myself at the moment :-(

Excerpts from Vicki Brown's message of Fri Apr 10 15:16:56 -0400 2009:

--
things change.
dec...@red-bean.com

Reply all
Reply to author
Forward
0 new messages