Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
I was away from Codidact for a few hours and, coming back, saw that I had ⑨ unread notifications. Practically as I was watching it, the number grew to ⑩. This wouldn't be so bad, but it turned ou...
#3: Post edited
by
ArtOfCode
·
2021-08-01T19:24:46Z (over 3 years ago)
#2: Post edited
by
Canina
·
2021-08-01T15:29:58Z (over 3 years ago)
Don't add duplicate notifications if an unread notification for the same event type and content already exists
- Don't add duplicate notifications if an unread notification for the same event type and parent post already exists
- I was away from Codidact for a few hours and, coming back, saw that I had ⑨ unread notifications.
- Practically as I was watching it, the number grew to ⑩.
- This wouldn't be so bad, but it turned out that they really were for just three comment threads.
- Getting one notification for each comment being added, before you have even had a chance to react to the notifications already in your notification inbox, can get rather overwhelming.
Hence, I propose that: **if there is an existing *unread* notification, for the same type of event and relating to the same container** (new answers to the same question, edits to the same post, comments within the same comment thread, new comment thread on the same post, etc.) **then no further notification should be added to the inbox.**
- I was away from Codidact for a few hours and, coming back, saw that I had ⑨ unread notifications.
- Practically as I was watching it, the number grew to ⑩.
- This wouldn't be so bad, but it turned out that they really were for just three comment threads.
- Getting one notification for each comment being added, before you have even had a chance to react to the notifications already in your notification inbox, can get rather overwhelming.
- Hence, I propose that: **if there is an existing *unread* notification, for the same type of event and relating to the same parent post** (new answers to the same question, edits to the same post, comments within the same comment thread, new comment thread on the same post, etc.) **then no further notification should be added to the inbox.**
#1: Initial revision
by
Canina
·
2021-08-01T15:29:03Z (over 3 years ago)
Don't add duplicate notifications if an unread notification for the same event type and content already exists
I was away from Codidact for a few hours and, coming back, saw that I had ⑨ unread notifications. Practically as I was watching it, the number grew to ⑩. This wouldn't be so bad, but it turned out that they really were for just three comment threads. Getting one notification for each comment being added, before you have even had a chance to react to the notifications already in your notification inbox, can get rather overwhelming. Hence, I propose that: **if there is an existing *unread* notification, for the same type of event and relating to the same container** (new answers to the same question, edits to the same post, comments within the same comment thread, new comment thread on the same post, etc.) **then no further notification should be added to the inbox.**