loading...

Double-counting notifs

yujiri8 profile image Ryan Westlund Originally published at yujiri.xyz ・1 min read

Most platforms with some type of blog-like structure, like Twitter and DEV, face the problem of too many notifications. Users can have thousands of followers and even get thousands of replies on everything they post. This is exacerbated if the platform doesn't let you opt-out of notifs on silly things like "someone liked a reply to your tweet". So they usually have some sort of notification-aggregating system, where you see "Name and 7 others liked your post" instead of a separate notif for each one.

But both Twitter and DEV have a problem with double-counting in these aggregated notifs. They seem to count the number of "recent" occurrences rather than "since last view", so I'll see "15 people liked your post", then the next day "16 people liked your post", meaning 1 new person.

I've yet to see a platform that counts them since last view.

Discussion

markdown guide
 

This is not double-counting -- it is counting an aggregation.

Presumably they do this because people feel that numbers going up are good, and numbers going down are bad.

 

It's double-counting because the same event appears in two aggregations.

That may be why they do it, but it has the opposite effect. If I want to see numbers go up, I'm going to be even more upset when I see a big number and then realize the actual number is small.

 

It's really not double-counting.
Do they count anyone's vote twice toward the total?

It's just an unclear aggregation.
Either a progressive accumulation, or a rolling window of some kind.