Hmmm...but there is no way to know the ids of the tweets without
having a list of all of the tweets, which would kind of defeat the
purpose of the limit.
Oh well...
On Sep 30, 12:39 pm, Tom van der Woerdt i...@tvdw.eu wrote:
Only the 3200 most recent ones, unless you know the IDs of the tweets.
Here is a closed feature request from forever ago to return the status_id of
all statuses for a user. Maybe Twitter wil reconsider the request.
http://code.google.com/p/twitter-api/issues/detail?id=379
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham |
I also posted a request a long time ago that an authenticated user be
able to retrieve all of his own tweets, back beyond the 16-page limit.
In retrospect, now that I'm within shooting distance of 40,000 I'm not
sure how good an idea that is. ;-)
--
M. Edward (Ed) Borasky
It remains a good idea. Imagine if Gmail only let you retrieve your
last 3200 messages even if you had 40,000.
On Sep 30, 4:20 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
I also posted a request a long time ago that an authenticated user be
able to retrieve all of his own
Fair point. Searching over it is trivial however, and perhaps that
would provide the most immediate benefit if implemented by Twitter.
Obviously though they don't have the capacity to handle that right
now, so at least allowing users to access all of their own tweets so
they can potentially index
I'll agree with all of you that'd it be valuable for us to do this.
The current state of availability of tweets is a capacity issue. It's
not in anyway a deliberate prevention of access.
As for since_id in this context -- it'd be great if it'd work to just
use since_id=1, but it doesn't. I don't
This should probably be a separate thread, but... what about a bulk
tweet lookup using status_ids for one very specific use case: turning
search results into proper tweets and avoiding all the other issues
that exist with the current implementation? I know bulk tweet lookup
by id has been asked
Considering Twitter can support returning the ids of almost 300,000
followers then 40,000 tweets should be easy.
http://api.twitter.com/1/followers/ids.json?screen_name=rsarver
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am |
Theorizing from the outside-in on our capacity issues aside, I'm a big
advocate for a bulk status/show or lookup function. We're definitely
giving that a lot of thought at the moment.
Taylor
On Thu, Sep 30, 2010 at 2:10 PM, Abraham Williams 4bra...@gmail.com wrote:
Considering Twitter can
Us outsiders have to get our pokes and prods in while we can :-P
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Thu, Sep 30, 2010 at 14:19, Taylor
Of course :)
I'll arm chair conjecture a bit also, since while I do work here I'm
definitely not the caliber of engineer as my colleagues, and certainly
not very knowledge in what it takes to scale a service like Twitter:
Things like followers/ids and friends/ids are likely accessible easily
Thank you for the conjecturing :)
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Thu, Sep 30, 2010 at 14:57, Taylor Singletary
If you need any reinforcement from the developer community just let us
know ;)
On Sep 30, 5:19 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Theorizing from the outside-in on our capacity issues aside, I'm a big
advocate for a bulk status/show or lookup function. We're definitely
13 matches
Mail list logo
