Does the since param in twitter.Api.GetUserTimeline do anything?

[Terry Jones]

Does the 'since' param in twitter.Api.GetUserTimeline do anything? I tried
pulling back some old tweets, but the param seems to be ignored.

The docs tell me to send an HTTP-formatted date (without telling me quite
what that is). It reads like I should be able to pass something like "Fri
Dec 1 12:00:00 +0000 2006" (which was before my first ever tweet). But no
matter what date I send, I always get the most recent tweets back. The
count param works, but if I make it too large (e.g., 2000), I get an
urllib2.HTTPError: HTTP Error 502: Bad Gateway.

Thanks for any help.

Terry

[Marc Hartstein]

Excerpts from Terry Jones's message of Sun Jun 14 20:53:52 -0400 2009:

>
> Does the 'since' param in twitter.Api.GetUserTimeline do anything? I tried
> pulling back some old tweets, but the param seems to be ignored.

Yeah, the twitter API is a little weird there. Try using the 'page'
parameter as well as 'since' and 'count'.

The API sends you the most recent 'count' statuses which are more recent
than 'since' (or 'since_id'). If you set 'page' greater than 1, it will
skip the most recent (page-1)*count statuses to find a group to return.

Last time I checked the API, 'count' could not exceed 200.

[Terry Jones]

>>>>> "Marc" == Marc Hartstein <marc...@gmail.com> writes:

Marc> Excerpts from Terry Jones's message of Sun Jun 14 20:53:52 -0400 2009:

>> Does the 'since' param in twitter.Api.GetUserTimeline do anything? I
>> tried pulling back some old tweets, but the param seems to be ignored.

Marc> Yeah, the twitter API is a little weird there. Try using the 'page'
Marc> parameter as well as 'since' and 'count'.

Hi Marc.

Thanks for the reply. GetUserTimeline doesn't take a page argument,
though. (I'm looking at the Twitter Python code from the svn trunk).

Marc> Last time I checked the API, 'count' could not exceed 200.

It worked for me last night with 1500.

Terry

[Maex]

On Jun 15, 2:53 am, Terry Jones <terry.jo...@gmail.com> wrote:
> Does the 'since' param in twitter.Api.GetUserTimeline do anything? I tried
> pulling back some old tweets, but the param seems to be ignored.

http://apiwiki.twitter.com/REST+API+Changelog
April 8, 2009
* Changed (REST): The since parameter and If-Modified-Since
header are
no longer supported.

It should be removed from the python-twitter API, too.

\Maex

[DeWitt Clinton]

I fixed this in the -dclinton branch a while back ... just back-ported it to /trunk now:

  http://code.google.com/p/python-twitter/source/detail?r=171

On that topic, I'm increasingly comfortable with the -dclinton branch (the major change being a switch to protobufs instead of hand-coded datatypes) being an okay long term direction.  But that's a major new dependency, and one I wouldn't want to force on people.  Once it settles down a bit more I'll ask for opinions about whether it should become the new trunk.

-DeWitt

[Terry Jones]

There's a small cut&paste bug in the 0.7-devel release (svn revision 171):

if max_id:
try:
parameters['max_id'] = int(count)
except:
raise TwitterError("max_id must be an integer")

should be int(max_id).

Terry

[DeWitt Clinton]

Fixed in trunk in r174. Please verify. Thanks!

http://code.google.com/p/python-twitter/source/detail?r=174

[Terry Jones]

Works for me. Thanks a lot.

Terry

>>>>> "DeWitt" == DeWitt Clinton <dcli...@gmail.com> writes:
DeWitt> Fixed in trunk in r174. Please verify. Thanks!

DeWitt> http://code.google.com/p/python-twitter/source/detail?r=174

[Markus Stumpf]

On Sat, Jun 20, 2009 at 09:31:16PM -0700, DeWitt Clinton wrote:
> Fixed in trunk in r174. Please verify. Thanks!

Shouldn't this better be a long()?

\Maex