In case you haven't seen, User:Rillke on Commons has implemented a (default-on!) gadget that makes it possible to subscribe to notifications of different types, e.g. policy changes, new features, etc. These are shown as watchlist banners and upon login.
Here's a screenshot of the "subscription" interface: http://i.imgur.com/gdImENz.png
IMO that type of gadget lends supports to the notion of shooting for a subscription model to be ultimately integrated with Echo so that users can get standard read-once notifications about things they care about while keeping the core UI clutter-free.
Erik
-- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation
Thanks, Erik.
Interesting development.
We can take a closer look at this idea once we get further along with high priority tasks like HTML Email and Cross-wiki notifications.
We should also discuss when and how to ramp up wishlist features like these for Echo, now that the notifications team is starting to move on to other projects.
To be continued,
Fabrice
On Jun 21, 2013, at 2:49 PM, Erik Moeller wrote:
In case you haven't seen, User:Rillke on Commons has implemented a (default-on!) gadget that makes it possible to subscribe to notifications of different types, e.g. policy changes, new features, etc. These are shown as watchlist banners and upon login.
Here's a screenshot of the "subscription" interface: http://i.imgur.com/gdImENz.png
IMO that type of gadget lends supports to the notion of shooting for a subscription model to be ultimately integrated with Echo so that users can get standard read-once notifications about things they care about while keeping the core UI clutter-free.
Erik
-- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation
On Friday, 21 June 2013 at 11:49 PM, Erik Moeller wrote:
In case you haven't seen, User:Rillke on Commons has implemented a (default-on!) gadget that makes it possible to subscribe to notifications of different types, e.g. policy changes, new features, etc. These are shown as watchlist banners and upon login.
Here's a screenshot of the "subscription" interface: http://i.imgur.com/gdImENz.png
IMO that type of gadget lends supports to the notion of shooting for a subscription model to be ultimately integrated with Echo so that users can get standard read-once notifications about things they care about while keeping the core UI clutter-free.
My understanding was that this sort of "feed" stuff was intended for a different subsystem that would become a part of Flow.