A while ago David mentioned that he wanted to unify tracks and actions, because most filter conditions are reused by both. The one major difference is that tracks work on all messages, while actions work only on messages in your timeline. Maybe it's worth thinking about factoring out common things.
On Wed, Oct 20, 2010 at 9:16 AM, Richard Hirsch <[email protected]> wrote: > On Tue, Oct 19, 2010 at 9:09 PM, Ethan Jewett <[email protected]> wrote: >> Well, as Vassil has pointed out, the tracks do a lot more than just tracking >> tags, so they definitely still offer something. Unfortunately they also are >> not very accessible to the average user. >> >> This type of question is part of the reason that I created ESME-285 ( >> https://issues.apache.org/jira/browse/ESME-285) in Release 1.2, so that we >> can make the decision to turn something like Tracks off by default, but >> leave it in the code base. I'm not saying that is necessarily the right >> decision here, but it is an option. >> >> Regarding lists of things being tracked, we need to figure out a reasonable >> item-tracking-management interface so that people can see everything they >> are following in one place and manage it. Maybe that is what "Tracks" should >> become eventually? I think that's a little ways off (maybe not Release 1.2 >> material), but definitely an interesting UI challenge. > > I like the idea of having one place to track everything I follow: > * Tags > * Conversations > * People > ... > > It would also be useful to be able to turn the items on and off at one > location. > >> >> Ethan >> >> On Tue, Oct 19, 2010 at 1:43 PM, Richard Hirsch <[email protected]>wrote: >> >>> Now that we can follow conversations and tags, do we still need tracks >>> as well? Besides the fact that I get a list of things I track, I don't >>> see any reason to keep them. >>> >>> D. >>> >> > -- Twitter: http://twitter.com/vdichev Blog: http://speaking-my-language.blogspot.com
