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