Comment by zamadatix

5 days ago

Comment items look like https://hacker-news.firebaseio.com/v0/item/45533616.json?pri...:

  {
    "by" : "jkarneges",
    "id" : 45533018,
    "kids" : [ 45533616 ],
    "parent" : 45532549,
    "text" : "The HN&#x2F;Firebase API doesn&#x27;t make this easy. For <a href=\"https:&#x2F;&#x2F;hnstream.com\" rel=\"nofollow\">https:&#x2F;&#x2F;hnstream.com</a> I ended up   crawling items to find the article.",
    "time" : 1760043552,
    "type" : "comment"
  }

"parent" can either be the actual parent comment or the parent article, depending where in the comment chain you are.

4 comments

zamadatix

esafak 5 days ago

Perhaps @kogir, who was active on https://github.com/HackerNews/API could add the thread id.

smusamashah 5 days ago

https://jaytaylor.github.io/hn-live2 is doing it though.

zamadatix 5 days ago
As does hnstream.com from the sourced sample comment itself. Both just traverse the parent id until it's the root (article). It takes more queries, but the API is not rate limited.
- krapp 5 days ago
  
  It wouldn't take more queries if the comments were cached. It could probably be done entirely in memory, HN's entire corpus can't be that large.
  If one were to start at the page endpoints (eg /topstories) one could add references to origin ids while preloading comments, and probably cover the most likely to be referenced ID, and even make traversal up the tree even more efficient.