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
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
The main thing that's changing with the new release of the API is the
URL scheme. We're cleaning things up, moving things around, making
the whole thing more RESTful. I'll confer with @mzsanford and see
about sharing our proposed set of URLs/methods.
Generally, though, we're still the same serv
The rewrite of the api has been on the cards for a while, and I've
kind of avoided doing any major work on Hahlo until I knew what was
happening, however it got the better of me last weekend and I began
work on Hahlo 4 which itself is a complete re-write.
Given that its a re-write how much do you
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,
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
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
Thanks for the update! For those of us doing current development with the
API, will the current version be kept around for a while (as a legacy
version I guess) so that we may continue development as the new API is being
rolled out? Or will it be a cut-over situation when the new API is
released?
Hi all,
Just wanted to give you an update on what's going on Twitter API land.
Firstly, my colleague on the API Team, Matt Sanford (@mzsanford), is
in town from Seattle and working from the Twitter offices. We're
trying to make the most of this in-person time to clear out
administrivia and plan
