No internet connection
  1. Home
  2. Support

Clear Notifications

By Cody @codywarmbo2018-08-25 15:20:25.054Z

My users and I used a chat the other day and now I have 45+ notifications waiting for me. I figured viewing the most recent one from the chat would clear them all but it did not. Am I cursed to a life of 99+ notifications eventually?

  • 24 replies

There are 24 replies. Estimated reading time: 10 minutes

  1. KajMagnus @KajMagnus2018-08-27 13:36:40.621Z

    I have the same problem :- P
    I mean, too many notifications waiting for me.
    Need to fix this, ... (won't happen immediately, ... I'm a bit short of time for the moment)

    I'll add a "clear-all-notifications" button, and also notifications from the same chat, can probably be collapsed, so one see only one of those notifications. And like you said, looking at the most recent ones, should probably clear all (in a chat).

    (Possibly a group of notifications that have been collapsed to just one, could expand on click, so one sees all those notifications from the same topic? hmm. I'll have a look at how this works, at other places)

    1. C
      In reply tocodywarmbo:
      Christian Scheuer @chrscheuer2018-09-09 02:02:27.689Z

      I'm also experiencing this. We're not using chats but regular forum threads/posts and in general reading/viewing a thread or post won't clear the notifications for that thread/post. So we have to manually click each and every notification to clear them (or ignore them) even if we've read the contents already.

      1. C
        In reply tocodywarmbo:
        Christian Scheuer @chrscheuer2018-10-23 19:05:59.993Z

        New bug possibly related to this: I'm getting a "Post not found" error when clicking on the notifications for this thread. It's consistently only for this thread.

        1. CChristian Scheuer @chrscheuer2018-10-23 19:06:35.404Z

          Clicking "Mark all as read" removed some notifications and now they work.... Hmm.

          1. KajMagnus @KajMagnus2018-11-01 11:29:12.941Z

            Seems this a bug: If someone, maybe I, reply to you, and then delete the reply (maybe I replied to the wrong comment, deleted my reply and re-posted it elsewhere) — then the notification to you, about the deleted reply, won't get deleted. I should delete the notification too. I'll add a comment about that in the source code so I'll remember. Thanks for mentioning.

        2. Progress
        3. @KajMagnus marked this topic as Planned 2018-08-27 13:36:46.582Z.
        4. @KajMagnus marked this topic as Started 2018-09-23 20:46:14.309Z.
        5. In reply tocodywarmbo:
          KajMagnus @KajMagnus2018-09-24 04:04:18.758Z

          I'll add a Mark All As Read button, as step one. Later on, maybe notifications can be grouped by page? And clicking [a notification that represents all notifications on a page] could clear [all notifications from that page].

          And yes @chrscheuer I'll look into marking those one reads, as read, too.

          1. CChristian Scheuer @chrscheuer2018-09-24 08:07:06.095Z

            Sounds like a good plan - thank you :)

          2. In reply tocodywarmbo:
            KajMagnus @KajMagnus2018-10-05 18:01:17.597Z

            Fixed now (mostly). Now there's a "Mark all as seen" button in your username menu, so you can mark all notifications as seen, at once. @codywarmbo, @someburneraccount, @melanopsis

            @chrscheuer I also wrote code that auto-marks posts as seen, when they're on screen. I'll enable it in the next release. (I.e. will fix this: "reading/viewing a thread or post won't clear the notifications for that thread/post". Maybe some tweaks will be needed, to adjust for people's reading speed.)

            1. CCody @codywarmbo2018-10-05 19:48:13.936Z

              This is great! Thanks for the update.

              1. In reply toKajMagnus:
                CChristian Scheuer @chrscheuer2018-10-14 18:29:36.739Z

                Hi @KajMagnus. For the "Admin review" part, I still have to manually review almost all content on the site even from members that are fully trusted. Have you looked at that bug yet?

                1. KajMagnus @KajMagnus2018-10-15 14:15:40.524Z

                  I think I found the problem: if a comment get posted, in a topic that's been closed — that comment appears in the review queue (but it shouldn't). I'll write more in the other topic.

                2. In reply toKajMagnus:
                  CChristian Scheuer @chrscheuer2018-10-14 18:32:10.417Z

                  For notifications. The behavior here is still that if there has been 7 new comments in a thread and I click one of the notifications for that, then I have actually read all the conversations in there, but I still will have to manually click the other 6 notifications for the same thread to make them go away.

                  1. KajMagnus @KajMagnus2018-10-15 14:39:35.124Z

                    (Sorry about the previous reply — I replied to the wrong comment)

                    That will be fixed in the next release, later this week. And maybe won't work "perfectly" directly — maybe the Javascript code will sometimes incorrectly think you weren'd done reading and won't clear the notification. Or it might clear it too soon. Maybe some done-reading timeouts will need to be adjusted.

                  2. In reply toKajMagnus:
                    CChristian Scheuer @chrscheuer2018-10-14 18:50:18.907Z

                    Additionally I've noticed the notifications don't come up automatically but only when I re-launch the page. It's always been like that but I thought it was just meant to do that, but now that I remember all our conversations about the open long polling / websocket like requests you're doing, isn't it meant to be working in realtime? Right now I'll get an email with a new topic, but nothing changed in the open tab I have of the forum. Then after reloading the forum page, I'll see both a red circle for the review item and a blue for the new post. But only after reloading the page.

                    1. CChristian Scheuer @chrscheuer2018-10-15 14:17:05.982Z

                      Additional info. The realtime stuff here on the talkyard.io does seem to work. Maybe there's something going on with automatic refreshes and custom domains?

                      1. KajMagnus @KajMagnus2018-10-15 14:35:26.459Z

                        Thanks for the info,

                        It's this problem: Notifications stop working because of an Nginx worker segfault.

                        1. CCody @codywarmbo2018-10-15 14:49:18.377Z

                          Working great here now! Thanks for the update.

                          1. KajMagnus @KajMagnus2018-10-15 15:11:31.007Z

                            Well yes it works fine, until the worker crashes :- P.
                            It crashes only infrequently.

                            (B.t.w. a "desperate" workaround could be to auto-restart Nginx, nightly, in a Cron job. ... Until the segfault has been fixed. Restarting Nginx takes only 1 second or so)

                  3. In reply tocodywarmbo:
                    KajMagnus @KajMagnus2018-10-22 13:39:09.266Z

                    @chrscheuer

                    Now the server has been upgraded, and it tries to mark post you have read, as read. For this to work, the browser needs to have focus. You'll see a small blue dot, at the top of a post:

                    and when it disappears, that means the browser thinks you've read the post. (If you reload the page, the blue dots reappear, but the related notifications should be gone & marked as read).

                    It'd be interesting to hear how this works for you.

                    1. CChristian Scheuer @chrscheuer2018-10-23 18:58:25.924Z

                      Nice implementation. What's the reason the blue dots reappear? Is that by design or just because it's not stored yet?
                      It seems like a really good experience at first, but it's a little confusing that they reappear :)

                      1. KajMagnus @KajMagnus2018-11-01 11:21:34.310Z

                        The idea is that the server will remember which posts you've read (namely the ones for which the blue dots have disappeared). Then, the next time you re-visit this page, ... the server will know which posts you have read, ... and which you have not read. You'll going to be able to cycle through the remaining unread posts, is the plan. ... So, if you're away for lunch, or sleep for a night, then, when you're back, you'll directly find any new & unread posts. There could be keyboard / mobile-phone shortcuts for cycling through unread posts, + they'll appear in a tab in the right hand sidebar (next to the Recent tab). ... Or if there's a really huge discussions, and you read a little bit here, a little bit there ... then, it can be hard to keep track of what you've read, and haven't. Then the computer can help you find things you've missed (haven't read yet).

                        This hasn't yet been implemented, though. The server doesn't remember which posts you've read. It only clears notifications (if three happen to be any) ... and the blue dots reappear on each page reload.

                        ((Storing has-been-read status won't take much storage space. A long int = 8 bytes = 64 bits = remembers 64 comments, is enough for almost all discussions.))

                    2. @KajMagnus marked this topic as Done 2018-11-26 07:45:06.054Z.