Trust level 3 requirements: a clarification — does this still hold? posts 61–90
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Worth separating two things that post #58 runs together.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
RSS: if you prefer to receive announcements by feed rather than visiting the site, RSS is available for this subcategory.
post #64 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.
On post #62 — agreed on the reasoning, with one qualification.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
Collapsed as off-topic by two members at trust level 3 or above
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.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
post #68 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.
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.
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.
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.
Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
Coming back to post #77, because the follow-up matters more than the original answer.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
Collapsed as off-topic by two members at trust level 3 or above
Picking up post #77: that is the part I would want checked first.
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.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
On post #84 — agreed on the reasoning, with one qualification.
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.