Why the timeline is on the right and not the left posts 31–60

Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.

Two things before anyone answers the substance.

First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.

Picking up post #44: that is the part I would want checked first.

Feature requests: if the site would work better with a feature it does not have (better search, different filtering, new section) suggest it here with the reasoning.

Coming back to post #46, because the follow-up matters more than the original answer.

Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.

post #48 is right about the mechanism and I think understates the practical bit.

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

Worth separating two things that post #46 runs together.

Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.

Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.

Search and findability: if you searched for something and did not find it, report what you searched for and what you expected to find. That helps improve indexing and tagging.

On post #49 — agreed on the reasoning, with one qualification.

Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.

post #53 answers the question as asked. The question underneath it is different.

Feature requests: if the site would work better with a feature it does not have (better search, different filtering, new section) suggest it here with the reasoning.

I read post #53 twice before replying, because I had assumed the opposite.

Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.

Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.

Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.

post #57 is right about the mechanism and I think understates the practical bit.

Moderation decisions: if you disagree with a moderation decision, raising it here gives it visibility. Staff will reconsider if you make a substantive case.

Coming back to post #57, because the follow-up matters more than the original answer.

Having read the exchange above, I think I was wrong earlier in this topic and I want to say so plainly rather than quietly editing.

The correction was fair and I had been repeating something I had not checked carefully enough.

Picking up post #57: that is the part I would want checked first.

Performance: if pages are slow to load, timeouts occur, or the site is unresponsive, that is worth reporting with details (when, which pages, how slow).