- Lacks basic responsiveness (would not be difficult to make links/buttons larger on phones while impacting nothing for desktop; as it stands they are very hard to hit on mobile)
- Long threads become unreadable due to shifting right with no end as replies come in, occasionally becoming comical
- Supports just enough markdown (asterisk italics, indented code blocks) to lead people to think they can use all of it (want bold, or in-line code? You lose.)
- Code blocks are unreadable on mobile since they cannot be scrolled
- Despite being an obvious design choice, breaking accessibility by reducing the contrast of unpopular comments is a deficiency.
As with others, I'm not sure what you mean by pagination.
The lack of response notification is a feature, though yes, it can be annoying, and I find the degree to which comments or questions go unresponded is ... disappointing. That said, notifications abuse by modern Web / App systems is rampant. I'd like some sort of middle-ground, perhaps a responses / notifications link which would consolidate these. "Threads" is the closest there is to that, though it includes all a person's comments whether (newly) responded to or not.
Mobile experience is pretty poor, agreed, though it's sufficient for reading logged-out (my preferred mode). Composing text on mobile devices is a category error.
Deep threads (and greyed text with downvotes) is a very intentional site design. pg's discussed that in the past, see:
I'm pretty sure this is intentional in order to avoid shallow discussions and not grab too much attention. I actually like this, but I agree with you that it can make it harder to get answers sometimes and you do miss some replies, on especially older comments.
Not sure what you mean by this, the lists of posts are very obviously paginated, as (admittedly a bit awkwardly) are larger comments threads. Maybe you mean auto-scrolling pagination?
> No notifications on reply, so it's difficult to get answers to clarifying questions (/threads helps but isn't it).
