1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
russellbal [6:35 PM]
I came up with a new SaaS idea today.
Aggregated (digest) notifications as a service.
jamie [6:36 PM]
is dat twitter
russellbal [6:37 PM]
You punt a fire hose of notifications at it and based on user (destination) settings it aggregates daily / weekly (edited)
jamie [6:37 PM]
what kind of notifications?
russellbal [6:38 PM]
App / webapp notifications (email notifications)
jamie [6:38 PM]
I mean what's the data
that are in the notifications
russellbal [6:38 PM]
That's up to the app developer
For me it would be "node events" where a node is a comment
jamie [6:39 PM]
asking because it's a common feature baked into SaaS's
do you get the daterdoge weekly from your account?
russellbal [6:39 PM]
Right, I'm building it now for Remarkbox and it's a pain in the arse.
jamie [6:39 PM]
it's like "your bla alerts were up 22%, transactions in x were 5% slower" etc
russellbal [6:40 PM]
Would love to be able to spray a bunch of notification documents at some other service and it would aggregate them Intellegently
Instead of 15 separate emails, one email a day with all the notifications
jamie [6:42 PM]
generically speaking, tuning sounds difficult
russellbal [6:43 PM]
Tuning how often to digest?
jamie [6:43 PM]
since agging data requires dimensions and thresholds and whatnot, which vary by data (and what info you want summarized from it)
that's just vaguely speaking though, not sure what kind of things you'd want in there
but deduping notifications in generally is like, good (inboxes are noise)
russellbal [6:43 PM]
I think I could make it generic.
jamie [6:44 PM]
what are "notification documents"?
russellbal [6:44 PM]
Yeah first version would likely focus on email, maybe web and push next
JSON blob with some minimal schema to make it work.
jamie [6:45 PM]
although re: the tuning mention, some implementations are smart about that, e.g. those that have the "show me less of this" for a particular message type
so you have to build heuristic engines
russellbal [6:45 PM]
I don't want 30 push notifications in an hour, I want 1 and hour with a summary
I don't think the "show me less" actually works.
jamie [6:46 PM]
for tuning, it does
russellbal [6:46 PM]
I would rather have more concrete control.
jamie [6:46 PM]
and that is usually the complexity
that control is distributed over your 30 services which have different controls
russellbal [6:47 PM]
If I want to see less of something typically don't want to see it at all and you tricked me
jamie [6:47 PM]
shaped for the data source type
russellbal [6:47 PM]
Lol
Thinking of Twitter right now.
jamie [6:47 PM]
yeah t has some examples of that
their user inputs are heuristics and heuristics are also fed into ML
russellbal [6:48 PM]
Shitty one's because if I could, I would completely disable the things that I don't want to see.
Aka notify never
jamie [6:48 PM]
right, so you have hard filters, but that doesn't fit to every problem
russellbal [6:48 PM]
I think it could.
jamie [6:49 PM]
so for instance with dd, let's say I get summary digests for all of the infra tagged with my team
and I want the digests for staging but higher fidelity for prod
a binary on/off doesn't work there
russellbal [6:49 PM]
I don't want an algorithm to show me less or more, I want to control the algorithm and merge notifications into a single one and consume it if or when I need it.
jamie [6:50 PM]
what would you be _controlling_ the algo to do?
russellbal [6:50 PM]
Let's say I'm going to moderate new comments on my blog weekly, I want to be notified weekly, for example.
jamie [6:50 PM]
show more or less? :troll:
russellbal [6:51 PM]
Showing the same and/or aggregating
At a better user defined frequecy of my choosing.
Which better fits my desired frequency I want to use that data.
jamie [6:53 PM]
hm, how many notifications do you have that you want batched?
russellbal [6:53 PM]
Knowing I got a new comment instantly triggers my FOMO and makes me want to react right away
I could switch that to weekly and I only get bothered weekely.
jamie [6:53 PM]
so now you can get FOMO batches
lol
russellbal [6:54 PM]
Right, once a week, once a month.
jamie [6:54 PM]
that ux in particular would be odd, comments a week old are basically tombstoned
russellbal [6:54 PM]
Once a day, less distractions are better.
jamie [6:54 PM]
I actually legit just put my phone on DND
I have some filters (ios thing) that can alert through it
so if specific people text me, etc
not re: your idea but re: general notification fatigue, it be real
russellbal [6:55 PM]
Naw they are not, especially if responding triggers a notification back at the asker
Still helps the next user too
jamie [6:55 PM]
I mean you'd be having interactions at a delay longer than the other end
so if you had some turbonerd that always responds (edited)
they may always respond right after you, but each of your responses is delayed by a week
me personally, I mentally batch those things and ignore them until the evening or something
russellbal [6:58 PM]
I don't do that, but a daily for you would work in this contrive example.
Could be awesome to allow not only frequency but a specific time window.
Only bother me between 8-9pm
Lol
jamie [6:59 PM]
that's the "tuning" stuff I mentioned, although much simpler to deal with than "less / more of" heuristics
russellbal [6:59 PM]
Yeah the service would expose ways for the end user to tune.
jamie [6:59 PM]
because then users would define "alert me daily from source x but only between 8 and 9, weekly on this on saturday morning from source y" (edited)
russellbal [7:00 PM]
My service would be business to business, other apps punt at me and I aggregate based on user settings.
Yes exactly that
I want to build that!
jamie [7:00 PM]
adoption blocker is that most don't have external push for their events
that and most services are particularly building their own digests (partly to "have data science teams because 2018" that are doing learning and shit on what people want to see)
russellbal [7:01 PM]
And I don't think it would be too hard to build, but I could have a decent time frame where I was the only service around.
jamie [7:01 PM]
e.g. with DD if you have a thousand different monitors setup, do you want to enable which to get digests from?
what if it's hundreds?
if you have a learning mechanism, you could for instance auto digest monitor alerts from the top 15 services present in dashboards by top usage
(I don't actually know the model, but that's an example)
the alternative is flipping k of 1,000 switches on or off
russellbal [7:03 PM]
Learning mechinism is more an advance problem that could be added to once the core works
Which would make the service even better.
jamie [7:04 PM]
that's the hard part everyone is solving individually
there's good models you could build with only the visibility of the messages, but it won't have the view inside the apps
(former being like doing likes in spotify, latter being the dd example of the app deciding what is best to notify based on user activity)
_hardest part_ -> naming services
saggurdaytur
combines aggregator, saturday, and dater
russellbal [7:12 PM]
I think the biggest objection would be that many companies know they are abusing people's attentions and they don't want to stop.
jamie [7:13 PM]
yeah, engagement is a critical business metric
russellbal [7:13 PM]
So I would have to make the case that better controls will lead to more use
Less people disabling notifications.
Altogether.
jamie [7:13 PM]
elevator pitch "improved notification fidelity and reduced fatigue will prevent people from ignoring you all together"
russellbal [7:14 PM]
Yup!
jamie [7:14 PM]
although, that's _why_ most companies want to do their own aggs, if they're semi decent they know they're going to notification fatigue users into ignoring them
russellbal [7:14 PM]
From my experience Twitter doesnt
Which is why I deleted the app few years ago (edited)
Funnily enough slack is my new time sink
jamie [7:16 PM]
I dunno, twitter was never too wild with notifications unless I opted in
it's gone up slightly (which mostly mirrors the web ux), e.g. showing likes from people you follow toward people you don't
which is noise that comes about with their attempt and boosting engagement
yeah, slack can easily be a timesink
russellbal [7:19 PM]
Anyways that's my idea and I wouldn't be trying to sell it to a Twitter or a datadog or a remind or a Fireeye, my target would be smaller startups, bootstrappers, etc. At least at first. (edited)
Indie games
That sort
jamie [7:24 PM]
do you remember wuphf from The Office (edited)
it was basically the opposite
russellbal [7:25 PM]
another spin is to pretend it's a must have for GDRP
market it that way.