4 ms·
I have a delay set in my profile because I often edit a comment once or twice after posting, and don't want to cause issues by someone attempting to respond to
by dabluecaboose 3y ago
I have a delay set in my profile because I often edit a comment once or twice after posting, and don't want to cause issues by someone attempting to respond to a comment that's about to change.
I didn't realize the comment showed as [delayed], I thought it just didn't post. Sorry for the trouble.
- mulmen 3y agoI also have a delay set in my profile. I give myself 10 minutes to edit or cool off and delete. But I have never seen a [delayed] comment. That seems to undermine the purpose of the delay.
- masfuerte 3y agoIt could be a bug. If the comment is about to become visible the code that chooses whether to show it at all might think the delay has expired but the code that renders it might still think it should be delayed. Especially if the rendering happens first.
- pests 3y agoI've been an active reader on HN for over 12 years and I have _never_ seen a comment displayed as [delayed] even once. Not on the site nor any of the third party mobile apps, and I've tried a lot of them. Weird.
- __jonas 3y agoJust a guess: Maybe the person who saw it as [delayed] is using a third party HN reader app and the HN website itself filters out delayed comments while returning it via the API as the [delayed] string and expecting clients to do the filtering?
- jader201 3y agoThis would explain the OP being annoyed to the point of asking for a ban on it. I’ve also never seen it in the many users of (mostly many times daily) visiting HN.
- Ruthalas 3y agoI use a 3rd party app, and see messages marked [delayed] not infrequently. Just as another data point.
- mulmen 3y agoOk, that tracks. Which third party app?
- rainbowzootsuit 3y agoI use Materialistic and see [delayed] all the time. Never knew what it was. I'm one of today's 10, I guess.
- saagarjha 3y agoIt's a little more complicated than that. A long time ago delayed comments actually showed up in the API, leaking their contents early. I reported this to 'dang as it obviously broke the purpose of the feature, and at some point the behavior changed to returning "[delayed]" for a bit instead of the actually contents of the comment. I assume changing things to indicate that the comment wasn't available yet was more work, and this was an easy compromise.