Re: [twitter-dev] Re: Draft of List API documentation

2009-12-13 Thread Marcel Molina
The list of member IDs as well as a resource to post ids and get full user objects back is on the todo list. No ETA at the moment other than "not next week". On Thu, Dec 10, 2009 at 8:09 AM, Orian Marx (@orian) wrote: > Any update on possibly supporting bulk add / remove actions for list > member

[twitter-dev] Re: Draft of List API documentation

2009-12-10 Thread Orian Marx (@orian)
Any update on possibly supporting bulk add / remove actions for list memberships? What about the request to fetch all list member IDs in a single call? On Nov 5, 2:01 pm, Marcel Molina wrote: > We will support specifying alistby bothidand slug indefinitely. > Though we recognize the short comings

[twitter-dev] Re: Draft of List API documentation

2009-11-05 Thread Marcel Molina
We will support specifying a list by both id and slug indefinitely. Though we recognize the short comings of finding by slug since they are prone to changing, there are use cases where finding by slug is a lot more convenient. So we'll be supporting both. You never *have* to search by slug :-) On

[twitter-dev] Re: Draft of List API documentation

2009-11-05 Thread Marcel Molina
Status timelines paginate with the page parameters. Social graph resources such as the members in a list use the cursor parameters. We're looking to rationalize all this as we move to new systems but for now there are different interfaces. You use the same mechanisms for the list statuses timeline

[twitter-dev] Re: Draft of List API documentation

2009-11-05 Thread Marcel Molina
I think it should work for any request. Not sure though. Give it a try ;-) On Thu, Nov 5, 2009 at 5:48 AM, Paul Kinlan wrote: > Can you confirm that _method=DELETE only works on POST's and not GET's? > Paul > > 2009/11/3 Marcel Molina >> >> A work around for environments that don't support the

[twitter-dev] Re: Draft of List API documentation

2009-11-04 Thread Marcel Molina
We plan to support this. It's on the todo list. Thanks for the suggestion. On Tue, Nov 3, 2009 at 8:38 PM, Damon Clinkscales wrote: > > On Fri, Oct 16, 2009 at 1:04 AM, Marcel Molina wrote: >> >> Hey folks. As some of you have likely read we're starting to do some >> private beta testing of our

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread Lee Semel
Seconding... In our app, whenever someone enters a screen name they want to add to a list, we have to do two API calls, to first get the id before adding the user to the list. Lee On Tue, Nov 3, 2009 at 11:38 PM, Damon Clinkscales wrote: > > On Fri, Oct 16, 2009 at 1:04 AM, Marcel Molina wrot

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread Damon Clinkscales
On Fri, Oct 16, 2009 at 1:04 AM, Marcel Molina wrote: > > Hey folks. As some of you have likely read we're starting to do some > private beta testing of our new lists feature. We're not quite ready > to open it up to everyone but we've made some headway on the API and > wanted to share some detai

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread wilfred yau
I have try this and It's work, thank you =] On Nov 4, 7:16 am, Marcel Molina wrote: > A work around for environments that don't support theDELETErequest > method is, I believe, to pass a parameter called _method with the > value "DELETE". In other words "_method=DELETE". > > > > On Mon, Nov 2, 2

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread Cameron Kaiser
> A work around for environments that don't support the DELETE request > method is, I believe, to pass a parameter called _method with the > value "DELETE". In other words "_method=DELETE". I'll take a look at that. -- personal: http://www.cameronkaiser.com/

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread Marcel Molina
A work around for environments that don't support the DELETE request method is, I believe, to pass a parameter called _method with the value "DELETE". In other words "_method=DELETE". On Mon, Nov 2, 2009 at 11:26 PM, wilfred yau wrote: > > It there any method to delete user from list other then

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread Rich
Does Air not support REST properly? For an application to be RESTful it should support GET, POST, PUT and DELETE On Nov 3, 2:14 pm, Cameron Kaiser wrote: > > It there any method to delete user from list other then using DELETE > > method? > > Since I am using Flex (but not Air) to develop third

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread Cameron Kaiser
> It there any method to delete user from list other then using DELETE > method? > Since I am using Flex (but not Air) to develop third party Twitter > Client, There are no way to call "DELETE" (which only GET and POST). > So, will twitter provide POST or GET method API to "delete"? Thanks I'd li

[twitter-dev] Re: Draft of List API documentation

2009-11-03 Thread wilfred yau
It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call "DELETE" (which only GET and POST). So, will twitter provide POST or GET method API to "delete"? Thanks On Oct 16, 3:04

[twitter-dev] Re: Draft of List API documentation

2009-11-02 Thread yoni
Bulk Add would be huge. Likewise, Bulk Delete. ~ yoni On Oct 20, 4:40 am, Tim Haines wrote: > Hey Marcel, > Another 2 methods I'd like to see added to the list api - a way to get the > id's of all current members (all 500), and a way to get the id's of all > current subscribers - cursor based w

[twitter-dev] Re: Draft of List API documentation

2009-10-24 Thread Dave Briccetti
By the way, I changed this code to do ten or fifteen of these at a time, using multiple threads, and it’s much, much faster.

[twitter-dev] Re: Draft of List API documentation

2009-10-24 Thread LeeS - @semel
Seconding bulk add. I'm working on a Lists app and everyone I've shown it to asks for this feature. Lee On Oct 18, 3:31 am, Dave Briccetti wrote: > Bulk add would be great. Here’s a log from doing individual adds. > Notice there were many over capacity errors. And that it took about a > minut

[twitter-dev] Re: Draft of List API documentation

2009-10-21 Thread Marcel Molina
There are plans to expose a description field eventually. On Wed, Oct 21, 2009 at 9:59 AM, nipunj wrote: > > Hey Marcel, > I expect there were many things cut in Lists v1,... but, that said, I > am surprised that Title is essentially the only attribute on the List > object that informs the consu

[twitter-dev] Re: Draft of List API documentation

2009-10-21 Thread nipunj
Hey Marcel, I expect there were many things cut in Lists v1,... but, that said, I am surprised that Title is essentially the only attribute on the List object that informs the consumer what a Public List is intended to actually represent. There's no "bio" analog. IMO, this lack of explicit descrip

[twitter-dev] Re: Draft of List API documentation

2009-10-19 Thread Michael Steuer
+1 for referring to lists by id and a bulk add feature. But as bulk features go, my highest priority is still the one discussed under the "cursors are slow" thread, ie. retrieving user objects based on id in bulk (vs doing users/show for each individual id retrieved via the social graph met

[twitter-dev] Re: Draft of List API documentation

2009-10-19 Thread Tim Haines
I'll +1 the requests for using the list id instead of the slug (and user id instead of screen name), and for a bulk add feature - I've already asked for a bulk remove feature... Tim. On Sun, Oct 18, 2009 at 5:34 PM, Beier wrote: > > I'm just wondering why can't we use list 'id' to call API funct

[twitter-dev] Re: Draft of List API documentation

2009-10-18 Thread Dave Briccetti
Sorry, that video is here: http://www.youtube.com/watch?v=NUVDP5sX2rA Copy/paste error.

[twitter-dev] Re: Draft of List API documentation

2009-10-18 Thread Dave Briccetti
Once Twitter posted details of the API in this public forum, that opened the door to our discussing lists publicly (if it wasn’t open already). And I’ve been doing so. I even made a video showing TalkingPuffin all of Robert Scoble’s lists at once on a big screen: http://twitter.com/dcbriccetti/sca

[twitter-dev] Re: Draft of List API documentation

2009-10-18 Thread Ollie Parsley
I created an app today using just the Lists API at http://listleagues.com when can I start publicising it? If anyone has any feedback let me know ol...@ollieparsley.com : thanks Ollie On Oct 16, 8:04 am, Marcel Molina wrote: > Hey folks. As some of you have likely read we're starting to do so

[twitter-dev] Re: Draft of List API documentation

2009-10-18 Thread Dave Briccetti
Multiple identical list create requests result in multiple lists, differing in slug/url/full name. Perhaps it should ignore, or return an error? $ curl -u dcbriccetti -d "name=Scala" http://twitter.com/dcbriccetti/lists.xml 29926 Scala @dcbriccetti/scala-2 scala-2 ... $ curl -u dcbricc

[twitter-dev] Re: Draft of List API documentation

2009-10-18 Thread Dave Briccetti
Bulk add would be great. Here’s a log from doing individual adds. Notice there were many over capacity errors. And that it took about a minute 42 to add about 60 users. If I could do all in one request, perhaps that would help reduce the over capacity errors. I’m enjoying lists. Thanks for the fe

[twitter-dev] Re: Draft of List API documentation

2009-10-17 Thread Beier
I'm just wondering why can't we use list 'id' to call API functions such as update, delete, timelines? I found out that list_slug can change when you update list name. This will give 3rd party apps lots of headaches. For example, right now my app has group features and I'm planning to migrate it

[twitter-dev] Re: Draft of List API documentation

2009-10-17 Thread LeeS
So far, I've observed the limits to be 20 lists per user, 500 users per list. Lee On Oct 17, 5:57 pm, Rod Begbie wrote: > Some questions on lists that came from a quick hack I made this morning > (http://github.com/rodbegbie/emulate-with_friends): > > 1) Are there any restrictions on list size

[twitter-dev] Re: Draft of List API documentation

2009-10-17 Thread @epc
When adding a user to a list, only the numeric id appears to work, eg: curl -k --user epc:pass -d id=7758742 --url https://twitter.com/epc/defrag/members.xml works, but curl -k --user epc:pass -d id=enorlin --url https://twitter.com/epc/defrag/members.xml results in a 500 Internal Server

[twitter-dev] Re: Draft of List API documentation

2009-10-17 Thread Brian Smith
Usually non-GET requests are not counted toward the rate limit. I agree that an “add in bulk” command would be better than having to individually issue multiple “add user to lists” calls. Rod Begbie wrote: 3) Does each "add user to list" call count towards the API Limit? If so, are th

[twitter-dev] Re: Draft of List API documentation

2009-10-17 Thread Rod Begbie
Some questions on lists that came from a quick hack I made this morning ( http://github.com/rodbegbie/emulate-with_friends): 1) Are there any restrictions on list sizes? 2) Are there any limits to the number of lists one user can have? 3) Does each "add user to list" call count towards the API Li

[twitter-dev] Re: Draft of List API documentation

2009-10-17 Thread Adam Loving
I just want to say thank you for looping us in early, much appreciated!

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Bill Kocik
Hi Marcel - First, thanks for the preview, this is very helpful. Second, a question: When retrieving an existing timeline such as / statuses/friends_timeline, or a list of friends from /statuses/ friends, will there be any indication in the output as to which list (s) the authenticated user is

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Kevin Makice
This is great. Will there be some mechanism to keep track on new and changed lists coming from the Twitter community, like a public timeline for list creation? Or is the only way to become aware of lists through the API to start checking users for their list creation/inclusion?

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Cameron Kaiser
> Hey folks. As some of you have likely read we're starting to do some > private beta testing of our new lists feature. We're not quite ready > to open it up to everyone but we've made some headway on the API and > wanted to share some details of what we've got so far. Thanks for the list API des

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Dave Briccetti
If anyone’s interested, here’s the commit for TalkingPuffin for preliminary support for displaying lists: http://github.com/dcbriccetti/talking-puffin/commit/ea86bfb523d7aea98df6ebae52893c16f53fa542 A picture of the feature: http://www.flickr.com/photos/dcbriccetti/4015781495/

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Rich
Yeah I'm holding off committing to code until we have the formal API docs and I can see how this works on the live site. On Oct 16, 10:02 am, Andrew Badera wrote: > Any chance of massive UI changes? Unless I'm missing something, the > List features is totally unmanageable via the GUI for anyone

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Dave Briccetti
Thanks, Marcel. I’ve started playing with this and it is working nicely so far. It would be nice to have a list count included in the user object so one doesn’t have to make a separate call for each user to see if that user has lists. Or something else that solves the same problem.

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread janole
Any chance to get on the private beta testing for adding the feature to my Twitter client or is the API coming later? Ole ;-) On Oct 16, 10:11 am, Marcel Molina wrote: > Depending on how our performance tests, bug fixes and all the other > myriad things go we could be public with the feature as

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Marcel Molina
Depending on how our performance tests, bug fixes and all the other myriad things go we could be public with the feature as early as a week or two from now. We shall see... On Fri, Oct 16, 2009 at 1:06 AM, Rich wrote: > > This is fantastic, I hope to start working on it soon.  Do you guys > have

[twitter-dev] Re: Draft of List API documentation

2009-10-16 Thread Rich
This is fantastic, I hope to start working on it soon. Do you guys have and idea of possible timespans, only because it takes us two weeks to get things past Apple's appoval process! On Oct 16, 8:04 am, Marcel Molina wrote: > Hey folks. As some of you have likely read we're starting to do some