Scheduled maintenance and what will be unavailable posts 31–60
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
post #32 answers the question as asked. The question underneath it is different.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
On post #30 — agreed on the reasoning, with one qualification.
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.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
Worth separating two things that post #34 runs together.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
Picking up post #36: that is the part I would want checked first.
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.
Coming back to post #38, because the follow-up matters more than the original answer.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
Worth separating two things that post #39 runs together.
Feedback to announcements: if you have feedback on an announced change (not a question, but your position) post it in the Meta category rather than here.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
I read post #47 twice before replying, because I had assumed the opposite.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
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.
post #54 is right about the mechanism and I think understates the practical bit.
For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
post #58 answers the question as asked. The question underneath it is different.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.