Hacker News Reader

Comment by dabluecaboose | Hacker News Reader

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.

View on HN

I 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.

It 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.

Just 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?

This 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.

I use a 3rd party app, and see messages marked [delayed] not infrequently. Just as another data point.

Ok, that tracks. Which third party app?

I use Materialistic and see [delayed] all the time. Never knew what it was. I'm one of today's 10, I guess.

I'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.

It'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.

Reply on news.ycombinator.com