Actually following on from this, I see @screenName/listName
automatically links to the list on the site, so surely we have to be
able to call the API using listNames too unless there is a reverse
lookup API to convert list id to slug?
On Oct 30, 11:31 pm, Rich rhyl...@gmail.com wrote:
Well we
It appears that user/lists.xml only shows lists that are created by
the user and not those that they follow.
Any change coming to that or am I missing a way to see all lists that
a user follows?
Thanks,
Jeremy
On Oct 28, 3:00 pm, Marcel Molina mar...@twitter.com wrote:
Two additions and two
The update says all requests that produce a list *of lists* will have
a cursor option.
What about lists of members following/followed on/by a list?
If I want to download the list of people following a list, members.xml
currently gives only 20 users. Is there a way to ask for more, or to
get the
Does calling the status timeline for a list count against rate limit?
What I'm thinking of is doing an Ajax widget that auto updates with
new tweets from a list every few seconds,
similar to how many people use the Search API to do this by hashtag.
If the status API request is rate limited this
Well we be able to use slug or will we HAVE to use list id? At the
moment I'm using the slug in my API calls
On Oct 30, 5:53 pm, LeeS - @semel lse...@gmail.com wrote:
Does calling the status timeline for a list count against rate limit?
What I'm thinking of is doing an Ajax widget that auto
Marcel,
Great changes. A couple of questions:
- How long can a list description be?
- A title can only be 15 chars - will that remain unchanged?
- Will there be a little overlap where memberships and subscribers
will still work while people migrate to followers/following?
It would be awesome
Answers inline:
On Wed, Oct 28, 2009 at 1:14 PM, Tim Haines tmhai...@gmail.com wrote:
Marcel,
Great changes. A couple of questions:
- How long can a list description be?
160 :-)
- A title can only be 15 chars - will that remain unchanged?
Unchanged.
- Will there be a little overlap
+1 to this
Any news on when the rest of us devs can get access to this to work on
our apps?
On Oct 28, 8:11 pm, Jesse Stay jesses...@gmail.com wrote:
Maybe a little more appropriate to post this to a private list (no pun
intended) for beta users? I admit I feel a little jealous every time I
Real soon now. We appreciate everyone's patience while we gradually
ramp up traffic to lists to ensure we've got all our ducks in a row.
On Wed, Oct 28, 2009 at 2:53 PM, Rich rhyl...@gmail.com wrote:
+1 to this
Any news on when the rest of us devs can get access to this to work on
our apps?
How does one keep a list up to date for a client without the concept
of since_id, like we have for the timeline methods? I look at a lists
as just a different timeline (granted one filtered to specific users),
but that is how I would expect to view them in a client.
From my understanding of
The cursors are for lists of lists and lists of users followed
by/following lists. The statuses timeline for a given list takes all
the same options you'd expect to manage status timelines.
On Wed, Oct 28, 2009 at 5:43 PM, Naveen knig...@gmail.com wrote:
How does one keep a list up to date for
Thanks for the quick response. I guess I was confused.
On Oct 28, 2009, at 8:53 PM, Marcel Molina wrote:
The cursors are for lists of lists and lists of users followed
by/following lists. The statuses timeline for a given list takes all
the same options you'd expect to manage status
12 matches
Mail list logo
