* > Moderators occasionally unkill such threads if they see it in time, although it rarely sticks
Moderators sometimes turn off the flags on posts like this, in which case the thread will usually stay on the front page.
* > Hacker News allows users to see what the front page looks like at any point in time
This wording makes me squeamish because the /front pages don't show what the front page looked like at any point in time - they're a blended average of the frontpage stories from a particular day. At no point did the front page actually look like that, but that's because you can't get a 24 hour view from any particular snapshot.
Additions:
* /next (or /prev) link on comments jumps to the next (or previous) comment at the same nesting level
* /root links (on item pages) jump to the top-level GP comment (this may be renamed to /top in the future)
* /context on a comment (when not on the original /item page) links to the comment in its place on the original /item page
* HN's software auto-edits titles to make them less linkbaity, but if it gets the edit wrong, you can change it after you submit (per https://news.ycombinator.com/item?id=38775366)
Also, see https://news.ycombinator.com/item?id=38779156 because that's another undocumented aspect. How to sum it up in a sentence? Maybe: "If you only use HN to submit your own stuff, the software will eventually start filtering your submissions." But then I need a second sentence: "It's fine to submit your own stuff, but it should be part of a diverse mix of unrelated/interesting things."
NB: One characteristic of "/context" is that where a comment has been flagged or killed, then the comment for which context has been requested isn't visible. The more so if "showdead" isn't enabled or when viewing from an unauthenticated session.
I run across this fairly frequently when checking on dang's comments, particularly when I'm not logged in, as moderator comments are often made following moderator actions or where members have downvoted or flagged a comment.
I'm not sure that a fix is needed, but the behaviour is slightly unexpected and confusing.
Corrections:
* These URLs aren't public - you can only see them if you're logged in as $name:
https://news.ycombinator.com/vouched?id=[name]
https://news.ycombinator.com/flagged?id=[name]
* > Moderators occasionally unkill such threads if they see it in time, although it rarely sticks
Moderators sometimes turn off the flags on posts like this, in which case the thread will usually stay on the front page.
* > Hacker News allows users to see what the front page looks like at any point in time
This wording makes me squeamish because the /front pages don't show what the front page looked like at any point in time - they're a blended average of the frontpage stories from a particular day. At no point did the front page actually look like that, but that's because you can't get a 24 hour view from any particular snapshot.
Additions:
* /next (or /prev) link on comments jumps to the next (or previous) comment at the same nesting level
* /root links (on item pages) jump to the top-level GP comment (this may be renamed to /top in the future)
* /context on a comment (when not on the original /item page) links to the comment in its place on the original /item page
* in the RSS section, could include: https://news.ycombinator.com/bigrss maps the frontpage and up to 9 pages after that
* HN's software auto-edits titles to make them less linkbaity, but if it gets the edit wrong, you can change it after you submit (per https://news.ycombinator.com/item?id=38775366)
* the bookmarklet could probably be added, per https://news.ycombinator.com/item?id=38778787
Also, see https://news.ycombinator.com/item?id=38779156 because that's another undocumented aspect. How to sum it up in a sentence? Maybe: "If you only use HN to submit your own stuff, the software will eventually start filtering your submissions." But then I need a second sentence: "It's fine to submit your own stuff, but it should be part of a diverse mix of unrelated/interesting things."