1. Ordered lists
- Unordered lists
Inline `code snippets`
Super^script
That's it. I totally get why HN wouldn't want tables, bold headers, etc. There's a danger of comments getting visually "noisy" with these. But for referencing code or mathematical concepts, or just listing things, the 4 things above would be really handy.
• like this
• using characters like
• U+2022 BULLET
‣ Or U+2023 TRIANGULAR BULLET
Similarly, you can do superˢᶜʳⁱᵖᵗ using Unicode as well (though I would only recommend it for numbers; Unicode doesn’t include all superscript letters, and most of the ones it does include look bad when used together). But yes, I agree that proper support for these things would be very good. (Especially code blocks!)
EDIT: Also, with native list support, you don’t get the wide line spacing. I like lists that aren’t paragraphs for each item.
Haven't worked with forum software other than Discourse, have you? They all still use BBCode.
I’ve worked a lot on our editors and content formatting pipelines. We support plaintext, markdown, HTML, BBCode, and a WYSIWYG editor with markdown shortcuts.
In reality is estimate the distribution is mostly the WYSIWYG editor nowadays for newer sites and BBCode for the older ones (some users on older entrenched communities really like their BBCode I guess).
This is an example of a code block, if that’s what you meant.``` https://www.youtube.com/watch?v=ab8GtuPdrUQ ```
</snark>Presumably, he's able to navigate HN since that's how we met.
I'm visually impaired but not blind. I have no problems navigating HN.
You are welcome to join the group and ask how other members navigate HN. Most of them joined via links found on HN.
The text is mostly illegible, but there are LOTS of other issues too, tap target sizing for example.
I guess everyone has to start somewhere? :P