Guidelines revision: what changed and why posts 61–90
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
Picking up post #61: that is the part I would want checked first.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
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.
I read post #65 twice before replying, because I had assumed the opposite.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
This follows post #65 rather than contradicting it.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
On post #65 — agreed on the reasoning, with one qualification.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
post #69 answers the question as asked. The question underneath it is different.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
Coming back to post #70, because the follow-up matters more than the original answer.
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.
post #72 answers the question as asked. The question underneath it is different.
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.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
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 #76: that is the part I would want checked first.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
I read post #79 twice before replying, because I had assumed the opposite.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
Collapsed as off-topic by two members at trust level 3 or above
post #83 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.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
On post #83 — agreed on the reasoning, with one qualification.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
This follows post #87 rather than contradicting it.
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.