31–40 of 40 posts
The query api at: https://hn.algolia.com is pretty amazing, searches all stories. The biggest qualms for me would be; notifications of comments and searching my previous comments. Other than that Hacker News is actually highly reliable and available and I've never personally needed an off-line version (except maybe on a plane)
I'd be very interested in something that can cache the actual article/page from the main HN link as well as a reading list. There are times when I add HN articles to mobile chrome's "read later" list, and when I have time go through them. Being able to read them later when not having internet access would be amazing (London's tube is annoying when it comes to internet, internet only exists in the stations).
Earlier quoted context omitted.
What is your use case for this server that makes optimizing for LAN vs WAN latency a valuable outcome? I’ve never really noticed that latency in email clients or when using the HN website and so I’m curious what is unique to your specific scenario that makes it a priority. (This isn’t criticism, but I definitely don’t understand why it’s a criteria in your case yet.)
HN itself is fast, but the comparison I'm making is with readers that use the HN API. See how getting each comment requires an additional API request: https://hacker-news.firebaseio.com/v0/item/22481199.json?pri... It's more about the consistency of operating on data local to the user. For example, see this comment referencing how HN paginates threads at 250 comments for performance reasons: https://news.ycombinator.…
In particular I like the fact that I can bookmark posts and comments with it.
I very often jump to the discussion to read opinions - there's often a treasure trove of stuff there of someone who knows something more than what the article states.
A really annoying, missing feature for the discussion/comments parts, is that the threads are extremely difficult to tell apart and traverse. On a small screen, the threads are very close together and only distinguishable through color differences. Scrolling through them is a nightmare, whereas I've really come to love the Reddit app's feature with a button that allows you to scroll to the next sibling comment, e.g. if you want TO quickly see the next comment to the OP, instead of scrolling endlessly and not knowing how far along you are.
Don’t forget to include the basics - upvote, downvote, unvote, comment, submit, save submission, save comment - and have all that sync when reconnecting to internet.
Don’t forget to include the basics - upvote, downvote, unvote, comment, submit, save submission, save comment - and have all that sync when reconnecting to internet.
- mark links and comments as seen
- hide seen
- fold comments to only show top level
- favorite links (preferably to a list that is easily dumped in to e.g. pocket with a few buttons for that)
Earlier quoted context omitted.
What is your use case for this server that makes optimizing for LAN vs WAN latency a valuable outcome? I’ve never really noticed that latency in email clients or when using the HN website and so I’m curious what is unique to your specific scenario that makes it a priority. (This isn’t criticism, but I definitely don’t understand why it’s a criteria in your case yet.)
HN itself is fast, but the comparison I'm making is with readers that use the HN API. See how getting each comment requires an additional API request: https://hacker-news.firebaseio.com/v0/item/22481199.json?pri... It's more about the consistency of operating on data local to the user. For example, see this comment referencing how HN paginates threads at 250 comments for performance reasons: https://news.ycombinator.…
Curiously enough, we should also be able to eliminate the pagination of comments by then as well. Both changes are waiting on some software work that we expect to improve performance significantly. I don't know when this will all be done, but I hope it's this year.