Hi Alex,
Thanks for the updates - one of the things I noticed is that the
archive API method was marked as wontfix. I was wondering what this
means for the future of accessing our Twitter history?
Is this just something where we won't be able to export it in one
shot, but still have access to
Yup, until some other under-the-hood stuff changes, we can't really
hand out a user's archive in a single request/response in a timely and
database-friendly fashion. You'll still have to page through to get a
user's full archive, but with effectively non-existent rate limits,
this should be much
We'll keep the current version running for a stretch (probably six
months tops) as developers transition over to the new version of the
API.
On Tue, Dec 2, 2008 at 12:33, Chad Etzel [EMAIL PROTECTED] wrote:
Thanks for the update! For those of us doing current development with the
API, will
On Tue, Dec 2, 2008 at 2:27 PM, Alex Payne [EMAIL PROTECTED] wrote:
Additionally, Matt has been working with our User Experience (UX) team
on a beta of OAuth support. The UX component of this work is almost
complete, and we should be ready for our first deploy in the next week
or ten days.
Sure, I'll talk to the UX folks about writing some of that up. OAuth
is still in its early stages, and it seems most every organization
that implements it ends up taking some slightly different paths.
On Tue, Dec 2, 2008 at 13:03, Christopher St John [EMAIL PROTECTED] wrote:
On Tue, Dec 2,
