14 votes

“You can't reply to this user yet. Please wait 29 minutes”

I just got this when trying to answer a comment. What’s that about?

18 comments

  1. DrStone
    Link
    I just hit it today with a simple A-B-A-attemptedB. This seems like something that should have at least reply count chain threshold before kicking in. The goal is to nip unnecessary, long...

    I just hit it today with a simple A-B-A-attemptedB. This seems like something that should have at least reply count chain threshold before kicking in. The goal is to nip unnecessary, long back-and-forth arguments in the bud instead of waiting for a mod (e.g. in political topics), right?. The current settings feel a bit stifling if both users happen to be online and the "X new unread / replies to your comment" indicator/notifications pull you back to a thread.

    A - Asked question
    B - ~30 after A - Replies
    A - ~1h after B - Follow up question or request for clarification
    B - Tried to reply, but told to wait 30 minutes after A most recent even though B hasn't participated in chain for an hour plus already. Hopefully B remembers to come back (since the "1 new reply" notification is probably auto-flagged as read and gone)

    I think it really needs to be more nuanced. Maybe a certain chain length in a window before it kicks in and based on your average reply time over that chain. So if in an hour, you've replied 3 times already and you've replied within a few minutes (less than some threshold) to the post you're replying to, then we say "hey, looks like you're in a heated back-and-forth, maybe take a half hour to cool off before you can reply". Ideally, and more likely when we have more active people, it could take into consideration upvotes and flags (e.g. if a back-and-forth is quick, but mostly getting votes and not getting any bad flags, let good discussion continue)

    5 votes
  2. [14]
    Wes
    (edited )
    Link
    This was addressed a couple weeks ago. https://tildes.net/~tildes/pee/whats_going_on_with_rate_limited_comments edit: Oh, you actually responded in that thread. edit2: I was wrong, and this is...

    This was addressed a couple weeks ago.

    https://tildes.net/~tildes/pee/whats_going_on_with_rate_limited_comments

    edit: Oh, you actually responded in that thread.
    edit2: I was wrong, and this is about another issue.

    2 votes
    1. [11]
      Bauke
      (edited )
      Link Parent
      I don't think that's it actually, a few new changes were pushed today that might be what mrbig is talking about. This is the notable change from the linked commits: The threshold is currently set...

      I don't think that's it actually, a few new changes were pushed today that might be what mrbig is talking about.

      This is the notable change from the linked commits:

      Return how many mins replying_user needs to wait to respond to replying_to_user.

      replying_user is the one that wants to be able to post a new reply. They can't do
      so if there exists a back-and-forth between them and replying_to_user where the
      most recent comment is within the time threshold.

      That is, call the user trying to reply "A", and the user they're replying to "B".
      If a sequence of comments exists that are written by users (B, A, B) and the last
      comment is "too recent", this will return how many minutes they need to wait. If
      there isn't any recent sequence like that, it will return None.

      The threshold is currently set to 30 minutes, so it looks like if you're going back-and-forth too quick there's now a hard limit.

      12 votes
      1. [9]
        Wes
        Link Parent
        You're right! My mistake.

        You're right! My mistake.

        1 vote
        1. [8]
          mrbig
          Link Parent
          I checked just to make sure, there were a few hours between interactions: https://imgur.com/gallery/wfmugXp I was trying to answer to the comment with the 18h21m timestamp.

          I checked just to make sure, there were a few hours between interactions:

          https://imgur.com/gallery/wfmugXp

          I was trying to answer to the comment with the 18h21m timestamp.

          1. Wes
            Link Parent
            Haha, were you trying to reply to me? Small world and all that. I was too hasty with my original assumption. I should have checked if there'd been other site developments since that last post.

            Haha, were you trying to reply to me? Small world and all that.

            I was too hasty with my original assumption. I should have checked if there'd been other site developments since that last post.

            1 vote
          2. [6]
            mrbig
            Link Parent
            @Wes it happened again. I cannot reply to you at this moment even though my last reply to you was more than 2 hours ago. If this is happening with everyone, it’s a pretty major bug, I think.

            @Wes it happened again. I cannot reply to you at this moment even though my last reply to you was more than 2 hours ago. If this is happening with everyone, it’s a pretty major bug, I think.

            1. [4]
              Deimos
              (edited )
              Link Parent
              It's not a bug. This is how it's intended to work: when you're involved in a back-and-forth with a user (as you are with @Wes here), you can't reply to the most recent comment in the chain until...

              It's not a bug. This is how it's intended to work: when you're involved in a back-and-forth with a user (as you are with @Wes here), you can't reply to the most recent comment in the chain until it's at least 30 minutes old. It doesn't matter how much time passed between previous comments.

              It's very possible this is too aggressive and I'll end up toning it down, but that's why I'm testing it—I want to see how it actually triggers in practice. So far, not a single other user has hit this between the time it happened to you yesterday (when you tried to reply to a comment less than a minute after it was posted) and this time now.

              Tildes isn't a chat program, you don't need to refresh the site constantly and reply to people immediately.

              6 votes
              1. [3]
                mrbig
                Link Parent
                I understand Tilde is not a chat program, I just found it odd because I literally went to sleep and was unable to reply to a comment several hours later. “ I was unaware of that requirement, and...

                I understand Tilde is not a chat program, I just found it odd because I literally went to sleep and was unable to reply to a comment several hours later. “ I was unaware of that requirement, and because of that I was unable to follow it. I apologize.

                5 votes
                1. [2]
                  Deimos
                  Link Parent
                  No need to apologize—it's brand new, and like I said, it's an experiment and you're helping test it by triggering it. I do think that trying to slow down could be a good thing overall though (for...

                  No need to apologize—it's brand new, and like I said, it's an experiment and you're helping test it by triggering it.

                  I do think that trying to slow down could be a good thing overall though (for everyone, not you in particular). I've tried to push in that direction in some ways on Tildes already, such as using "Activity" for the default sorting method so that topics are longer-lived. There are other related changes I'm working on too, like updates to how reply notifications work, because I think the current method definitely heavily encourages immediate responses.

                  4 votes
                  1. skybrian
                    Link Parent
                    Having just hit this, I would prefer not seeing the notification until I can reply. It seems like a slightly different throttle might be better: you can't reply until N minutes after your previous...

                    Having just hit this, I would prefer not seeing the notification until I can reply.

                    It seems like a slightly different throttle might be better: you can't reply until N minutes after your previous ancestor post?

                    Combined with the above, If it's been N minutes since your previous post, you can reply immediately, but your correspondent wouldn't see the notification immediately because they just posted.

                    2 votes
            2. Wes
              Link Parent
              That does seem problematic. We're not responding so frequently as to be in a flame war (which I assume this was meant to combat). Nice workaround though with the ping. :p @Deimos, you might want...

              That does seem problematic. We're not responding so frequently as to be in a flame war (which I assume this was meant to combat).

              Nice workaround though with the ping. :p

              @Deimos, you might want to tweak the numbers on this feature?

              2 votes
      2. mrbig
        Link Parent
        I was trying to answer after waking up, I'm pretty sure many hours had passed.

        The threshold is currently set to 30 minutes, so it looks like if you're going back-and-forth too quick there's now a hard limit.

        I was trying to answer after waking up, I'm pretty sure many hours had passed.

        1 vote
    2. [2]
      mrbig
      (edited )
      Link Parent
      I believe this previous thread -- which was actually deleted -- was about another thing: a rate limit on a single user, preventing them to post on any thread. From what I can gather, it seems that...

      I believe this previous thread -- which was actually deleted -- was about another thing: a rate limit on a single user, preventing them to post on any thread. From what I can gather, it seems that in this case I was only prevented from answering to a single user or comment.

      2 votes
      1. Wes
        Link Parent
        You're quite right. See the comment by Bauke in this thread for more details, if you haven't already. I didn't realize that previous thread had been deleted either. Unfortunately that also deleted...

        You're quite right. See the comment by Bauke in this thread for more details, if you haven't already.

        I didn't realize that previous thread had been deleted either. Unfortunately that also deleted Chad's response to the issue.

        3 votes
  3. [3]
    Five
    Link
    I’ve not experience this on here yet but it seems like the same thing Reddit does and it’s so annoying I really hope it isn’t a permanent feature on here.

    I’ve not experience this on here yet but it seems like the same thing Reddit does and it’s so annoying I really hope it isn’t a permanent feature on here.

    1 vote
    1. [2]
      Bauke
      Link Parent
      It was recently removed but will likely come back at some point:

      It was recently removed but will likely come back at some point:

      Remove comment back-and-forth delay

      I think overall this is triggering more than I want, and getting in the
      way of perfectly reasonable conversations. I like the idea still, but
      needs adjusting.

      6 votes
      1. Five
        Link Parent
        That is great news, I’m not against the feature completely just think it has to be done right from the start.

        That is great news, I’m not against the feature completely just think it has to be done right from the start.