Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Comments on Don't add duplicate notifications if an unread notification for the same event type and parent post already exists

Parent

Don't add duplicate notifications if an unread notification for the same event type and parent post already exists

+4
−2

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.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

I'm curious what the downvotes mean (3 comments)
Post
+1
−0

I thought we did this already, so I had a look. Turns out we were using the wrong link to check for duplicates, which I've updated. You should find you only get one notification per comment thread when there are any number of new comments now.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Seems to be wrong the other way around now (2 comments)
Seems to be wrong the other way around now
Canina‭ wrote over 3 years ago

This sounded promising, but when I was pinged in https://software.codidact.com/comments/thread/3801 after this answer was posted, I didn't receive any inbox notification at all. (My most recent inbox notification is currently listed as 11 hours ago, I marked that as read previously, and I was pinged in a comment timestamped 9 hours ago in a comment I hadn't seen.) So now it seems to be buggy in the opposite direction.

Canina‭ wrote over 3 years ago

Okay, at a glance, it appears to be working as intended now.