Figuring out how Flow integrates with the watchlist and Echo is one of the toughest and most important parts of the project. The feedback that the team got from the last couple releases was actually pretty diverse, and showed us that there's going to be a lot of work ahead of us to figure out how to represent Flow activity.
Some people are seeing Flow messages as really important, something that they want to get updates on right away -- and "right away" can mean either in their watchlist where they go all the time, or in Echo where they'll see the notification. Other people see Flow messages as something they'll get to later, and they want to see more of a message inbox. The interesting thing for me is that this doesn't seem to break down along "new user" vs "power user" lines. People with the same level of experience and activity can still use and think about those tools differently. The work that we've done on the Flow/Echo/watchlist integration so far is just a couple steps into what is going to be a longer process. We need to build more options into the feature to help people choose what kind of notifications they want to see, and where. Danny On Mon, Sep 15, 2014 at 7:55 AM, Diego Moya <dialm...@gmail.com> wrote: > On 15 September 2014 15:24, Amir E. Aharoni > <amir.ahar...@mail.huji.ac.il> wrote: > > That is quite true. A deep modernization of the Watchlist should be > coupled > > with the Flow poject somehow. Either Special:Watchlist itself should be > > profoundly redesigned and upgraded, or the Flow+Echo notifications should > > become so good that they can replace it. > > > > Whatever you do, please don't try to replace the Watchlist with Echo > notifications; they serve quite different roles and are complementary, > not a surrogate. > > The recent backlash that Echo received when it was updated last week > was in part because of that, as it included as notifications all the > updates that would normally be seek out at the watchlist and therefore > shouldn't generate an alert. > > I agree that the Watchlist could be enhanced with more granular > filters, groupings and search functions. A lot of user workflows are > based on personal usages of the watchlist, which work as the de-facto > coordination tool between editors participating in the same projects. > > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines > Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
