Pagination Limits?

[Damon C]

I was debugging something with TweetStats this evening and noticed
that pagination limits are now strictly enforced. I can't even bypass
the UI by just putting ?page=n. I was pretty bummed to find this out
as this is the method that TweetStats uses to retrieve archive data
and generate it's pretty graphs.

First - Will this feature be coming back? (I'm assuming it will, so)
If so, when?
Second - Is PubSub going to be available to all again in the
(hopefully) near future?

I was hoping to use PubSub to alleviate load on both my and twitter's
servers, but then the great Twitter crash of '08 came along.

I would love to continue providing TweetStats as a service, so
hopefully there are some postive answers to the above.

Thanks,

Damon (@dacort)

[Alex Payne]

> First - Will this feature be coming back? (I'm assuming it will, so)
> If so, when?

This wasn't a supported feature - "bypass" says it all. Until we can
reliably serve timelines without a bunch of cache trickery, we're
forced to only allow pagination as far back as cache can sustain.
When our new architecture is in place it should be possible to
paginate back 60 days for friends_timeline, and possibly more for
user_timeline.

> Second - Is PubSub going to be available to all again in the
> (hopefully) near future?

PubSub will be available again with an agreement. It may or may not
be XMPP. Our timeline is unclear.

--
Alex Payne
http://twitter.com/al3x

[Damon C]

Soooo....a followup question.

Will our own full archives ever be accessible to us again via the
Twitter service?

[Alex Payne]

Yes, that's absolutely a goal. I consider our service defective
unless users can export all of their own content.

--
Alex Payne
http://twitter.com/al3x

[mdy]

Just wanted to jump in and say that I hope our archives can be made
available via an export-type feature so people can get a copy of the
tweets that they've made even if much older tweets are no longer
browse-able via the website.

I'm fine with the tweets not being navigable via the website if I can
get my own offline copy upon request. And I'm fine with the request
not being serviced immediately (e.g., I'm 100% okay with submitting a
request and getting a csv dump of my archive emailed to me several
days later).

I'd be really disappointed if I can no longer get a copy of my tweets
in some way. I know Al3x said we can possibly get more than 60 days
for the user timeline, but since I've been on Twitter since September
2006, I think it's safe to say even 450 days of navigable history
won't be enough for me to get my entire archive.

Thanks for listening,
~mdy