I'm really curious what a system designed to push that much info out all over the place looks like. Where can I learn more about this?
N1, N2, ... NN are notifications.
Time 0 ms: N1 is delivered. It appears at y=0 with no animation.
Time 100 ms: N2 is delivered. It appears at y=0 with no animation. N1 is animated to y=50 over 100 ms.
Time 150 ms: N3 is delivered. It appears at y=0 with no animation. N2 is animated to y=50 over 100 ms. N1 is currently at y=25 (halfway through its animation) and is now animated to y=100 over 100ms.
Now N1 appears to accelerate downward while N2 is moving at half the speed downward, and N3 is behind both of the notifications waiting to be pushed down. The effect is like a waterfall of notifications accelerating downwards, without ever explicitly coding it that way.
[Celebrity wakes up & glances at phone]
>> IG: "You are still very popular and everyone loves you"
[Celebrity breathes a sigh of relief and goes back to bed]
Second, why does the os allow this many notifications? Obviously this is an edge case, but there are countless apps and any of them could have a bug or unexpected situation like this that causes a lot of notifications.
Why wouldn't it? How would you implement a throttle that behaves correctly with all notification types?
Seems to me the better solution here would be Instagram bundling up notifications within a specific amount of time and sending you just one saying "You have 15,000 new likes!" etc.
A low and configurable limit exists w.r.t. the number of notifications per app that will appear in the lock screen or notification drawer.
The user also has full control over whether s/he wants any notifications at all from Instagram.
I don’t see the problem.
I'm surprised the cell towers were able to keep up without skipping a beat.
They are slowed down somehow. Because even if I disconnect the Internet immediately after I remember what awaits me, it keeps bugging me for quite some time after. Associated ring/buzz is not "grouped" so it is a hellish experience (and perhaps that's the reason why it is so slow).
In short I can imagine the trade-off of less-optimal support for some edge cases like these.
Surely sending all these notifications isn't entirely free - someone else posted Snowden receiving 47 gigs of mail because of email notifications.
You could do something like send notifications with some sort of back-off. Send them for 10 seconds, then back off to a minute's worth chunk, then 10 minutes, then an hour.
Then again, I don't have any statistics on how much these external services actually cost, nor how often this actually does happen. Simplest thing is for instagram/twitter to not care, and to point the finger at apple/android and tell them they should have UI to squelch high-frequency notifications.
Bad assumption, given the 90:9:1 rule (99% lurk while 1% participate)
1% does mean a lot when you have millions of followers, though.