Is there a way to get more than the last 20 updates? I'm working on
integrating twitter with my blog, and I'd like to import all my
updates, even the old ones. I've got a nice twitter plugin for
wordpress, but alas the api or the feeds only give 20 updates. Do I
have to resort to writing a regular expression and parsing the html
pages, or is there a secret parameter to get the last X updates?
Thx,
Lode
This has been a frequent question of late, and we'll be clarifying it
early next week. I'd like to give developers as much flexibility
with our data as possible while still maintaining performance. I'm
sure we can figure out a good middle ground.
Thanks!
--
Alex Payne
http://twitter.com/al3x
I sure do understand possible performance issues. I'd be perfectly
fine with ie. a limit on the amount of times the complete backlog
could be downloaded in a certain timeframe, or even a subset of the
past tweets for those with huge backlogs. I do think this possibility
could foster some new exciting mashed up applications built around the
Twitter platform.
Looking forward to the news from you guys. Have a very nice weekend!
On May 4, 9:17 pm, Alex Payne <a...@al3x.net> wrote:
> Lode,
>
> This has been a frequent question of late, and we'll be clarifying it
> early next week. I'd like to give developers as much flexibility
> with our data as possible while still maintaining performance. I'm
> sure we can figure out a good middle ground.
>
> Thanks!
>
> --
> Alex Paynehttp://twitter.com/al3x
Cheers,
Lode
--
twitter.com/lode
www.lodev.name
On May 4, 9:17 pm, Alex Payne <a...@al3x.net> wrote:
> Lode,
>
> This has been a frequent question of late, and we'll be clarifying it
> early next week. I'd like to give developers as much flexibility
> with our data as possible while still maintaining performance. I'm
> sure we can figure out a good middle ground.
>
> Thanks!
>
> --
> Alex Paynehttp://twitter.com/al3x
> any news on this? "Early next week" has passed some time ago now..
I am curious about this as well. I created a quick script exactly for
the purposing of backing up all of my tweets [1]. I would rather focus
on ways of repurposing the data for long term storage rather than the
mechanics of parsing, fetching, and error checking. An official
interface for downloading our entire account archive (and those of our
friends) would be peachy.
[1]: http://raysend.com/mark/2007/05/21/making-twitter-safe-for-historians/
On May 23, 10:59 am, "Alex Payne" <a...@al3x.net> wrote:
> Here's the deal: we've already got this code working, but we're
> hesitant to open it up to everyone until we're satisfied that the
> database won't choke under the load. So, the functionality is there,
> we're just a bit more testing away from making it widely available.
> Thanks for your patience!
>
> On 5/23/07, Mark James Adams <mark.james.li...@gmail.com> wrote:
> database won't choke under the load. So, the functionality is there,
> we're just a bit more testing away from making it widely available.
> Thanks for your patience!
No, thank *you* for helping me to remain a lazy programmer.
--
Mark
http://twitter.com/mja
*ping*
Any news on this?
The question I thought this thread was asking was when will the API
allow for *more* than the most recent 20 updates to be pulled?
Right now if my bot polls the public timeline it receives *only* 20
replies no matter what the query parameters are and no matter if there
has been 25 or 30 updates since the last poll. That means if it's a
friendly bot and polls once a minute or every other minute it can
easily miss half of the updates.
Has this been changed? Did I miss an API update?
On Jun 27, 3:14 pm, "Britt Selvitelle" <anotherbr...@gmail.com> wrote:
> This has been rolled out. You should always get the latest 20 updates,
> regardless of the age.
>
Can Britt or Alex react on this?
Cheers!
--
Alex Payne
http://twitter.com/al3x
That's too bad. I understand your reasoning, but please add me to the
list of people who could really use something like this. I am
developing an app on Ning, and Ning can only run scripts automatically
every 30 minutes. Since I am looking for a keyword in all Twitter
statuses in the public timeline, the 30 minute thing combined with the
only 20 statuses per check certainly turns the thing into a needle in
a haystack, and maybe makes the whole app pointless. Oh well.
On Jul 6, 2:44 pm, Alex Payne <a...@al3x.net> wrote:
> It's been postponed. This could potentially put a lot of stress on
> our database, and we don't want to impact site performance.
>
> --
> Alex Paynehttp://twitter.com/al3x