I guess that by "bundling" you refer to present several notifications of
the same type as a single element.
I think that aggregating them by type is something really good for certain
kind of notifications, but other content-related notifications may benefit
from being aggregated by content.
Thats especially relevant when several individual events are correlated or
can be interpreted as signs of a more global event (which is somewhat
related to the concerns raised by Chris).
For example, if a page receives 1k reads, 20 comments and 2 cross-link, it
may be useful to present that as a single "Your page on Higgs Boson is
becoming popular (1k reads, 20 comments and linked by 2 other pages today)".
More than a specific solution I wanted to make sure that different kinds of
aggregation critera are considered when the "bundling" discussion happens.
On Thu, Jan 10, 2013 at 11:50 PM, Matthew Flaschen
On 01/10/2013 05:30 PM, Chris McMahon wrote:
Facebook has a really nice design along those lines, which I think
we can emulate.
See these screenshots
our best practices deck.
I am starting to think that the "<page> was linked" should not be
subject to individual notifications at all.
I thought about this, and at first I thought I agreed. But I actually
think it could be interesting for main namespace pages I created,
especially recent ones. If it's mainspace->mainspace (a link *on* an
article *to* an article) and there is a time-based filter ("links to
articles you created within the last 30 days"), I would probably use it.
Pages you created in the past being linked by
others are a different
kind of interaction that is not human-to-human, but more akin to, for
example, someone visiting a blog page that you wrote some time in the
I'd say it's somewhere in between, since writing something (the link is
just one aspect) using your page is different from just visiting it.
EE mailing list