Wait… I’m using `delay` to create an “edit window” because I often spot mistakes after posting. Didn’t realize it actually shows up instead of being, well, delayed.
Edit: tested it on this comment (in another private window). Observations: delay=1 is actually around 3 minutes. The comment didn’t show up until the time has passed. No * * * was observed.
Interesting, I’ve never seen that. Reading HN since circa 2012, but it feels like delay > 0 should be rare enough. Maybe the author of that app (or is it a mailing list?) would be interested in researching what hn’s js itself does in this case. Maybe delay was just “slapped on top” like we all sometimes do :)
P.s. I edited the comment above somewhat later after tinkering, so if you received a notification and followed it quickly enough, it was expected that I was too slow to post an update. I don’t think there’s another issue here.
Also, just as an idea how it may happen. I was thinking about how you go to comments from this app. If you follow a “context” link, the page may not yet contain the #hash and may simply omit the comment. But if you follow a “reply” link, aka “time ago”, HN itself may have no choice but to show three stars until the delay is over.
Edit: tested it on this comment (in another private window). Observations: delay=1 is actually around 3 minutes. The comment didn’t show up until the time has passed. No * * * was observed.