Nice job, Tuan! Having written an HN interface myself, my hat off to you for seeing it through and sharing it. Building on Minor49er's comment about requests,

Nice job, Tuan! Having written an HN interface myself, my hat off to you for seeing it through and sharing it. Building on Minor49er's comment about requests, a nice feature in your next iteration of Lipu might be to cache some or all of the details of the submission on your server side. Three benefits from doing that are: (1) you can choose how often you query firebaseio for fresh data to avoid hammering their server, (2) your UX latency isn't so dependent on network traffic, and (3) you can reuse the submission details (i.e., provide a speedy response to user) when the user switches from one category (e.g., top, new, ask, show) to another and the same story happens to be present in both categories. For other HN readers, Tuan has a brief dev blog of sorts about developing Lipu: https://tsk.bearblog.dev/journal-lipu/ https://tsk.bearblog.dev/journal-lipu/ . (Not too bad for a 14-year-old!)