Notifications
Jason Robinson
Public
Seen by 148
OK this thing is bugging me daily so raising a thread about it.
The notifications popup that we have, why does it have to mark all the five visible comments as read when you keep it open for a few seconds? This is just really frustrating as the notifications themselves don't give any clue what the target post is, so after they are all marked read, I have to click through all of them even if they would all concern only a few posts.
Also, why just 5? I would love to have it scrollable, so I can read my notifications from the menu and they would be only marked read when I have seen the actual post in question.
This is how Facebook works and tbh it's fantastic :)
Do people like the way it is or can I make an attempt to change it?
goob
Thu 20 Mar 2014 9:23PM
I have to vote to keep current functionality until I hear that http://videobin.org/+7h1/9s2.html will be implemented as part of this PR.
Rasmus Fuhse
Fri 21 Mar 2014 5:34AM
The current behavior is unintuitive, I think.
goob
Sat 22 Mar 2014 12:51PM
With https://github.com/diaspora/diaspora/pull/4869 implemented, the auto-mark-as-read won't be needed.
Ryuno-Ki
Wed 26 Mar 2014 9:19AM
It annoys me to see plopping the notifications to "read" status before I got to it. Moreover, it doesn't work in the "Show all notifications" stream!
Thomas Leister
Wed 26 Mar 2014 4:26PM
Since my first day on Diaspora this has been the most annoying thing.
It would be great if there was a small extract of the Post, too, so you can quickly recognize which notification belongs to which post.
goob Wed 19 Mar 2014 11:19AM
@morgenstern you can see a preview of how this would work in @steffenvanbergerem's video here: http://videobin.org/+7h1/9s2.html
I think that's quite intuitive.
Steffen van Bergerem Wed 19 Mar 2014 11:42AM
@goob The code I used for the video has not been pushed to the branch and I think I lost the code. However, rewriting that shouldn't be a lot of work.
Jason Robinson Wed 19 Mar 2014 12:52PM
I read Ruxton’s comment as warning against making a change which might break code/functionality for users. If this is not a danger/possibility, I would be happy to see the notification behaviour changed. But I’d like that clarified before voting.
I think Ruxton meant was not break code, but change functionality. YES keeps current functionality as default, NO changes it.
goob Wed 19 Mar 2014 1:41PM
@steffenvanbergerem Oh, thanks for the clarification. I thought your video was to show me that this is how your PR will work if implemented. I could only vote for a change of functionality if it worked in the way shown in the video. If you could please clarify whether or not the functionality shown in your video would be implemented with your PR, that would help me decide how to vote on this proposal.
goob · Wed 19 Mar 2014 11:17AM
I read Ruxton's comment as warning against making a change which might break code/functionality for users. If this is not a danger/possibility, I would be happy to see the notification behaviour changed. But I'd like that clarified before voting.