4 ms·

So this is who bought foster.co. Good to see someone made something with it!

• stewfortier 4y ago
  We were wondering who that other bidder was… ;)
  • echelon 4y ago
    Unrelated comment: How is it that your comment's timestamp is one to two minutes older than the parent comment? (It might take a few refreshes to see.) Is this an HN bug, or is there some strange thread merging behavior happening here?
    • dang 4y ago
      That wouldn't just be an HN bug, it would be the HN bug equivalent of breaking the third law of thermodynamics. (Unless we grafted a comment to a different parent for some reason, which we didn't here.) I'll look into it. Edit: Oh, it's an artifact of us re-upping the thread, which we do with Launch HNs as long as commenters are staying engaged. We use the same software as when putting submissions in the second-chance pool (explained at https://news.ycombinator.com/item?id=26998308 https://news.ycombinator.com/item?id=26998308), and that relativizes timestamps as I've described here: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=by%3Adang%20timestamps&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que.... Actually that arguably is a bug, because we don't need to do anything with comment timestamps in cases like this. We do it because when we first started the second chance pool, people would get confused by submissions on the front page with timestamps like "3 days ago" or whatever, and the same if there are comments in the thread saying "3 days ago". It doesn't change the official timestamps, though, which you can see by hovering over the "x minutes/hours/days" ago text. So in that sense physics remains intact.
      • echelon 4y ago
        Fascinating! Thanks for sharing, Daniel!