Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.
Moderation log format change posts 31–58
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
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.
On post #31 — agreed on the reasoning, with one qualification.
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.
Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.
Worth separating two things that post #35 runs together.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
post #39 is right about the mechanism and I think understates the practical bit.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
Collapsed as off-topic by two members at trust level 3 or above
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
This follows post #40 rather than contradicting it.
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 #42 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.
post #44 answers the question as asked. The question underneath it is different.
Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.
Coming back to post #46, 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.
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.
Worth separating two things that post #46 runs together.
Questions welcomed: if an announcement is unclear, asking for clarification is welcome. Staff will explain their reasoning.
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 #49: that is the part I would want checked first.
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.
When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.
Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.
Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.
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.
This topic was referenced in
- Trust level 3 requirements: a clarificationMeta › Announcements · 14 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Scheduled maintenance and what will be unavailable
Scheduled maintenance and what will be unavailable Writing it up because I had to work it out twice and would rather nobody else did. Nominating something for promotion into the documentation commons. The…
|
+121 | 128 | 25k | 15mo |
|
Trust level 3 requirements: a clarification
Trust level 3 requirements: a clarification — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps…
|
+10 | 14 | 7k | 9mo |
|
Revisiting: A staff appointment, and what the role involves
Revisiting: A staff appointment, and what the role involves — setting out what I have, and where I think it stops being reliable. Process question about how this site works. I have read the guidelines and the…
|
2 | 1k | 22mo | |
|
[2026 update] New subcategory: rationale and scope
New subcategory: rationale and scope — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps being…
|
+142 | 163 | 1.8k | 18mo |
|
Trust level 3 requirements: a clarification — does this still hold?
Asking directly, because I could not find a straight answer: Trust level 3 requirements: a clarification — does this still hold? Process question about how this site works. I have read the guidelines and the…
|
+76 | 90 | 57k | 9h |
Related topics — sharing the tags trust levels, guidelines, site feedback
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Follow-up: Bug report: the reconstitution calculator and a rounding edge case
On the subject in the title: Bug report: the reconstitution calculator and a rounding edge case Working notes rather than a conclusion. Working through the identity arithmetic and I would like it checked.…
|
+58 | 63 | 24k | 5mo |
|
[2026 update] New subcategory: rationale and scope
New subcategory: rationale and scope — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps being…
|
+142 | 163 | 1.8k | 18mo |
|
A revision dispute resolved on the topic rather than in the history — a second dataset
On the subject in the title: A revision dispute resolved on the topic rather than in the history — a second dataset Working notes rather than a conclusion. Process question about how this site works. I have…
|
+45 | 50 | 33k | 20mo |
|
Request: show the solution author in the topic list
Posting this under the heading it deserves: Request: show the solution author in the topic list Everything below is what sits behind that. Nominating something for promotion into the documentation commons.…
|
2 | 2.4k | 10mo | |
|
Coming back to: A newcomer's list of things that confused me, and the fixes
Posting this under the heading it deserves: A newcomer's list of things that confused me, and the fixes Everything below is what sits behind that. Question in the title. Context below, and I have tried to…
|
+4 | 8 | 57k | 23d |