I know this is from ‘07, but I wish that in the browser on mobile the karma point location and logout button location were swapped. I always accidentally hit the logout button when I mean to hit my username, super annoying.
Also wish for notifications of comment replies but I understand that maybe this isn’t done for minimalism purposes.
> Also wish for notifications of comment replies but I understand that maybe this isn’t done for minimalism purposes.
You might be aware of it, but in case others are not there's the unofficial https://www.hnreplies.com which does exactly that for many years already. Works great!
The front page ideally would only have links to upvote, read the story, and read the comments for each story, at least on mobile. Having big targets for sausage fingers on small touch screens would be even better.
It's too easy to tap the wrong link and end up flagging, hiding, or searching for stories from that domain, as you point out.
It's fine on desktop (up until 500%, but that's excessive), on mobile the "magnify" is just a "zoom" (past 125%).
The difference being in "magnify" the text will be larger but the "page" stays the same width, so text wraps at the screen boundaries and you don't need to pan back and forth with your finger. Whereas when "zooming", the page's virtual width increases with the zoom level, so you need to constantly be panning while reading, which is an awful experience.
Because it's a folkloric tradition instead of a proper feature documented under comment syntax, not everyone knows about it. So half the people use code blocks instead which break on mobile, or double quotes, or use italics, or don't do it at all.
Blockquote exists in HTML, why not have syntax for it on HN? Its a 2 line change to the comment processing code + 16 bytes of CSS for arguably one of the most important tools in civilized written discussion forums.
It would actually seem the code block line wrapping was "fixed" on mobile which means now code blocks line wrap (I don't think they should) so quotes don't look bad anymore if you use code blocks, but code does :shrug:
But it doesn't! Your comment kinda proves my point :) See my other reply to another commenter which proposed the (more widespread in practice) use of > signs.
> Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.)
https://news.ycombinator.com/formatdoc
Like a lot of people, you misunderstand what MLK was about and the context of that quote[0]. He very much would have been on the side of the "radical hateful narratives" you're against, and you "compromising your morals."
I have felt something like that would be advantageous for the member's thread page - but I would be simply happy with the number of comments in brackets after the thread tittle ... it would be at least of all be useful for those when their reply was amongst the first handful of replies to the subject or those who have a good memory of how many comments was there the last time they visited.
I'd like to know when there's a new reply to a comment I made in an article, without having to click my username, then comments. So basically a notifications icon/link at the top right.
I don't want to rely on a 3rd party service, and I think the change would make HN better.
I'd also like to be able to follow users that I think are interesting, to be able to see their posts/comments. But that would be a much bigger change, and is closer to a Twitter-style design. I wouldn't want this to be the default view, but it would be really interesting as a link on the top left.
If anyone here is a telegram user, here's a Hacker News alerts bot I'm developing for such kind of notifications: https://github.com/lawxls/HackerNews-Alerts-Bot (reply alerts is still in To Do stage)
None. All the niggles and lousiness here serve well to keep a critical mass of people away who will be the eventual ruin of this place. It's an unignorable trade-off.
* A distinct environment for blockquotes, distinct from preformatted code blocks.
* Fenced code blocks, rather than two-extra-spaces-before-each-line code blocks.
* Allow a to be entered with a link submission, but have it separated to form a summary comment. A summary comment would be like a regular comment (and submitters often submit them separately now), but now such a comment would be labelled explicitly as a submitter summary, and treated differently for placement: unless a summary comment (entered as such with the link) was net-downvoted (probably by more than a few points, or for an extended period of time), it would remained pinned to the top of the thread. If it did reach a sufficient net downvote status by points and/or time, it would either float normally or be demoted to the very bottom. This would preserve the advantage that no text with submissions has of preventing editorialized summaries getting a durably privileged placement, but would also recognize that having more of a summary than a headline does have a value.
ACTIVE DO NOT WANT:
Things that make HN more like "mainstream" social media: Followers, especially visible and promoted to others, Notifications, any kind of algorithmically personalized feed. (On platform DM's might be okay, though)
- Better documentation, on relevant pages (e.g. list formatting help link on this page and not only the editing page; list the meaning of all fields in the user page on that page; etc).
- Chronological display mode (which ignores all voting and karma numbers).
- NNTP.
- Search function without JavaScripts.
- Make votes up/down labeled, similar like Slashdot does indicating "informative", "interesting", "funny", etc. Possibly get rid of unlabeled votes, since they are problematic.
- When doing flag, allow to specify what it is a duplicate of (if any). (I currently don't use "flag" at all, but might occasionally do so if it had this function.)
- Support URI schemes other than "http" and "https" (e.g. "telnet"), but not "file".
- Perhaps increase limit of titles a bit.
- Don't automatically change titles and then complain that they are too long even though the original title was not too long.
- Display comment form on all pages, not only the first one.
- "Dead conversation mode" that does not restrict replying to anything (regardless of age and flagged/dead); such messages are automatically hidden to anyone who is not using such mode. (Perhaps restrict this to NNTP, and disallow such a thing in the web interface. Furthermore, even then such comments should be blocked when they are flooding too much (in order to avoid denial of service, wasting disk space, etc).)
66 comments
[ 2.8 ms ] story [ 134 ms ] threadAlso wish for notifications of comment replies but I understand that maybe this isn’t done for minimalism purposes.
You might be aware of it, but in case others are not there's the unofficial https://www.hnreplies.com which does exactly that for many years already. Works great!
But I'd like a link to the archive.is version of a page, if available. To bypass paywalls and for sites that have been hugged to death.
It's too easy to tap the wrong link and end up flagging, hiding, or searching for stories from that domain, as you point out.
Trying to click comments into a new tab or something is a struggle without zooming massively.
The difference being in "magnify" the text will be larger but the "page" stays the same width, so text wraps at the screen boundaries and you don't need to pan back and forth with your finger. Whereas when "zooming", the page's virtual width increases with the zoom level, so you need to constantly be panning while reading, which is an awful experience.
Blockquote exists in HTML, why not have syntax for it on HN? Its a 2 line change to the comment processing code + 16 bytes of CSS for arguably one of the most important tools in civilized written discussion forums.
Edit: quick example off a frontpage article I randomly clicked (open in mobile to see what I mean) https://news.ycombinator.com/item?id=35015639
Another: https://news.ycombinator.com/item?id=35012745
It would actually seem the code block line wrapping was "fixed" on mobile which means now code blocks line wrap (I don't think they should) so quotes don't look bad anymore if you use code blocks, but code does :shrug:
Edit 2: Yep https://news.ycombinator.com/item?id=29835072
> Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.) https://news.ycombinator.com/formatdoc
NOT wanting to discriminate against people based on their race and gender, I would hope is not only a right wing position.
Unfortunately, radical hateful narratives have become the norm in HR throughout our industry and it's making the industry toxic.
Pretty soon I'll have to choose between my morals and food though, and it'll be interesting to observe how that goes.
[0]https://www.forbes.com/sites/colinseale/2020/01/20/mlks-i-ha...
I'd also like to be able to follow users that I think are interesting, to be able to see their posts/comments. But that would be a much bigger change, and is closer to a Twitter-style design. I wouldn't want this to be the default view, but it would be really interesting as a link on the top left.
Full markdown, ``` for code blocks.
Zulip supports:
But on HN, it's still: HN could implement two spaces at the end of a line creates a <br> like Markdown, so that it could be this:* Fenced code blocks, rather than two-extra-spaces-before-each-line code blocks.
* Allow a to be entered with a link submission, but have it separated to form a summary comment. A summary comment would be like a regular comment (and submitters often submit them separately now), but now such a comment would be labelled explicitly as a submitter summary, and treated differently for placement: unless a summary comment (entered as such with the link) was net-downvoted (probably by more than a few points, or for an extended period of time), it would remained pinned to the top of the thread. If it did reach a sufficient net downvote status by points and/or time, it would either float normally or be demoted to the very bottom. This would preserve the advantage that no text with submissions has of preventing editorialized summaries getting a durably privileged placement, but would also recognize that having more of a summary than a headline does have a value.
ACTIVE DO NOT WANT:
Things that make HN more like "mainstream" social media: Followers, especially visible and promoted to others, Notifications, any kind of algorithmically personalized feed. (On platform DM's might be okay, though)
Also an unreserved +1 to more formatting options. I'd just suggest a (reasonable subset of) markdown.
They are upvoted by the hyped fans of the language regardless of the value of the link content.
- Chronological display mode (which ignores all voting and karma numbers).
- NNTP.
- Search function without JavaScripts.
- Make votes up/down labeled, similar like Slashdot does indicating "informative", "interesting", "funny", etc. Possibly get rid of unlabeled votes, since they are problematic.
- When doing flag, allow to specify what it is a duplicate of (if any). (I currently don't use "flag" at all, but might occasionally do so if it had this function.)
- Support URI schemes other than "http" and "https" (e.g. "telnet"), but not "file".
- Perhaps increase limit of titles a bit.
- Don't automatically change titles and then complain that they are too long even though the original title was not too long.
- Display comment form on all pages, not only the first one.
- "Dead conversation mode" that does not restrict replying to anything (regardless of age and flagged/dead); such messages are automatically hidden to anyone who is not using such mode. (Perhaps restrict this to NNTP, and disallow such a thing in the web interface. Furthermore, even then such comments should be blocked when they are flooding too much (in order to avoid denial of service, wasting disk space, etc).)