• (disco) in reply to blakeyrat

    Bwahahahahaa! I'm not mention-bomb-able! I turned off sending email to me on mentions entirely as one of the first things I did with this site. I guess I'll see the notification count go up a lot, but that just like a current score meter, yes? :smiley:

    (200 messages a day wouldn't make much odds to my mailstream in any case. Provided they don't all come in the same minute or so. Setting up filtering rules is trivial…)

  • (disco) in reply to dkf
    dkf:
    Bwahahahahaa! I'm not mention-bomb-able!

    Oh, so you wouldn't have issues in your notifications?

    dkf:
    I guess I'll see the notification count go up a lot,

    And lose track of other notifications you might actually care about.

  • (disco) in reply to abarker
    abarker:
    lose track of other notifications you might actually care about

    Name one. ;)

  • (disco) in reply to dkf
    dkf:
    abarker:
    lose track of other notifications you might actually care about

    Name one. ;)

    Replies. Quotes. :P

    Filed Under: Naming two

  • (disco) in reply to abarker
    abarker:
    Replies. Quotes.

    I find it easier to just read everything than make any attempt to look at my notifications.

  • (disco) in reply to dkf
    dkf:
    I find it easier to just read everything than make any attempt to look at my notifications.

    I generally read stuff I get notifications about first, but I do try to get around to reading everything (well, there are some topics I'm so far behind that it's not worth the bother). If only Discourse were consistent in what it takes to get the notifications marked read... I hate leaving notifications with blue highlights. (Yes, I know there's a "Mark all as Read" button; that's cheating.)

  • (disco) in reply to Yamikuronue
    Yamikuronue:
    We do a lot of the same things over and over, which can be standardized and practiced.

    And that's great for things we do over and over. I spend a great deal of time doing exactly that.

    But we don't implement the same feature (or fix the same bug) over and over, and I do not share the blind faith that ISO 9000 contributes anything to quality there.

    Most QMS's seem designed to sanctify recurring activities (and "artifacts" - uggh), as if to draw attention away from the places where a QMS doesn't really help.

  • (disco) in reply to HardwareGeek
    HardwareGeek:
    If only Discourse were consistent in what it takes to get the notifications marked read... I hate leaving notifications with blue highlights. (Yes, I know there's a "Mark all as Read" button; that's cheating.)

    In certain combinations of moves and notifications generated before the move, marking the notification read is impossible.

  • (disco) in reply to PleegWat

    Yes, I know that. I was mostly talking about the fact that sometimes reading the post that the notification is for will mark the notification as read. Read all the posts :fa_arrow_right: read all the notifications. However, sometimes reading the post won't mark associated notification read, and you have to actually click on the notification to convince Discourse that you've read it. (Note: You don't have to actually read the associated post; just clicking is sufficient. You don't have to wait for the post to load.) Sometimes, if there is more than one notification for a post (e.g., a like and a reply, or I see this especially when two bots simultaneously get the first like on a post in t/1000, and both likes generate notifications), reading the post will cause Discourse to mark one of the notifications as read, but not the other one.

Leave a comment on “Uncommon Respect”

Log In or post as a guest

Replying to comment #:

« Return to Article