I am also very glad to see this functionality added the Twitter platform, and personally dont care that we created groups already, as lists adds more functionality that needs to reside on the platform. It is sorely needed to make the data portable so users can use the best client in the browser or desktop or mobile devices, and take this data with them.
However the announcement really was very vague. Avoiding the word groups seems strange, and tells me they then wont be implemented purely as subset timelines of the main timeline (suggestable/ followable or not), arranged by following IDs. If they are more complicated than this, and are more like suggested followings to help with user discovery (aka TweepML), I suspect many clients will retain their own group functionality, not really solving this problem (which maybe Twitter does not consider as much of a priority). If we are unable to easily display "groups/lists", or whatever you call them, as subsets of the home timeline I fear a lot of client developers will end up supporting lists but also having their own Groups features. We likely would since we have built it already. Will we get to see the API as it is drafted and being tested for a period of time before it is released at all (not just a small group of Twitter friends) so that will know what is intended and have a chance to adjust development priorities? --ejw Eric Woodward Email: e...@nambu.com On Sep 30, 9:22 pm, Derek Gathright <drg...@gmail.com> wrote: > Yay! Lists are a much needed feature and it's great to get some official > word out of Twitter that they are coming. The real killer part of this > feature is the ability to subscribe to other people's lists, you really hit > the nail on the head with that one. The list subscription functionality > I've toyed around with in my Tweenky client and most recently implemented at > tweetgroups.net. Being able to create a list and allow others to subscribe > to it is huge! > Along with the saved searches API, the introduction of these features is > great because it is one less thing the client devs have to worry about > storing & managing ourselves. And face it... interoperability was never > going to happen with groups/lists between clients, so this is a great way to > give choice back to the users. Boo to silos. > > On Wed, Sep 30, 2009 at 6:22 PM, dean.j.robinson > <dean.j.robin...@gmail.com>wrote: > > > > > > > Nice stuff! > > > Glad I didn't spend a heap of time developing my own list/group > > solution for Hahlo, instead I can just drop in the API. sweet. > > > On Oct 1, 9:13 am, Marcel Molina <mar...@twitter.com> wrote: > > > Over on the main Twitter blog @nk has written about a new Lists > > > feature we're getting ready to launch: > >http://blog.twitter.com/2009/09/soon-to-launch-lists.html. We just > > > wanted to let API developers know that we'll be shipping an API for it > > > on day one. You'll be able to do things like create lists, add and > > > remove users from lists, find out who has been added to a list and > > > read the tweet timeline for a given list. > > > > Stay tuned for documentations on the full Lists API soon. > > > > -- > > > Marcel Molina > > > Twitter Platform Teamhttp://twitter.com/noradio
