Supportive, with one reservation worth stating in public: the change makes a common case slightly slower in exchange for making a rare case much better. That is usually right and it is not automatically right.
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.
Practical question on the rollout: will it be visible that a topic was created before or after the change? Six months from now nobody will remember the date.
Since moderation log format change keeps coming up, it should probably be a maintained page rather than a recurring thread. I am happy to draft it if someone with more direct experience will review it.
Picking up post #31: that is the part I would want checked first.
Summarising the moderation log format change thread so far, since it is long and the answer is buried: the first reply has the method, the fourth has the correction to it, and the rest is people agreeing at length.
I had written a reply contradicting post #31 and deleted it. Here is what survived.
One question about the transition rather than the policy: what happens to topics that are in flight when it takes effect? The announcement is clear about posts and silent about drafts.
That is the version I use. It may not be the version that is correct.
On moderation log format change I would separate what is worth knowing from what is worth acting on. The first list is long and the second is short, and conflating them is how threads get heated.
Worth saying publicly: stepping back cleanly and handing over is a service. Documents with an absent maintainer go wrong quietly, which is the worst way for them to go wrong.
I am not the right person to answer the follow-up to this.
Everything in post #35 holds. The case it does not cover is the one I have.
A note on how moderation log format change gets discussed rather than on moderation log format change itself: the confident posts get the replies and the careful ones get ignored, and the careful ones have been right more often.
Narrowing post #39, because the general version has more than one answer.
Thank you for announcing it in advance rather than after. The number of places that do the reverse is remarkable.
A guess, clearly labelled as one.
Collapsed as off-topic by two members at trust level 3 or above
My position on moderation log format change is current rather than settled. I have revised it once already and I expect to again, so treat it accordingly.
Nothing to add on the substance. Thank you for taking the question at face value.
Everything in post #41 holds. The case it does not cover is the one I have.
The rare case here is the one that costs somebody a week, though, and the common case costs everyone ten seconds. I think the trade is clearly correct.
The disagreement above is smaller than it looks once the terms are fixed.
Taking post #44 at face value and following it one step further.
The honest answer on moderation log format change is that it depends, and the useful part is the list of what it depends on. Four items, in rough order of how much they matter.
Most people get the first two right and then argue about the fourth.
I read post #46 twice before replying, because I had assumed the opposite.
Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.
It is a small point and it changes the answer, which is an awkward combination.
One question about the transition rather than the policy: what happens to topics that are in flight when it takes effect? The announcement is clear about posts and silent about drafts.
The strength of my opinion here exceeds the strength of my evidence.
Worth separating two things that post #46 runs together.
Supportive, with one reservation worth stating in public: the change makes a common case slightly slower in exchange for making a rare case much better. That is usually right and it is not automatically right.
The number is defensible. The precision I gave it is not.
Moderation log format change has been discussed here with more heat than it deserves, mostly because two definitions have been in play the whole time.
Narrowing post #49, because the general version has more than one answer.
Reading the changed pages: the diff is smaller than the announcement implies, which is reassuring rather than disappointing. A large change to a documentation page usually means the previous version was wrong.
A qualification I should have led with rather than closed on.
Noting appreciation rather than asking anything. Several years of unpaid work on something with no leaderboard and a public log of your mistakes is a peculiar thing to volunteer for.
I am confident about the direction and much less about the magnitude.
Two claims get bundled together under moderation log format change and they need separating. The descriptive one — this is what was observed — is usually well supported. The causal one — this is why — usually is not.
Almost every disagreement in threads like this one dissolves once you say which of the two you are making.
I came in to disagree and I am leaving without a disagreement.
Where I part company with post #53, and it is a narrow parting.
Practical question on the rollout: will it be visible that a topic was created before or after the change? Six months from now nobody will remember the date.
Flagging that the sources on this are thinner than the confidence in the thread suggests.
The moderation log will carry the announcement entry, so the date is recoverable. It will not be visible on the topic itself, which is probably the right level of clutter.
It is worth stating the boring hypothesis before the interesting one.
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. Collecting what is known about scheduled maintenance in one place, because…
|
+120 | 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. Trust level 3 requirements, and specifically the version of it that the documentation does not…
|
+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. Reading back through what has been written here about staff appointment, three…
|
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. Proposing that New subcategory deserves a maintained page rather than a recurring topic, and drafting…
|
+136 | 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? Two things I would like separated before anyone answers on Trust level 3…
|
+77 | 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. Posting the calculation with the inputs, so that somebody can disagree…
|
+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. Proposing that New subcategory deserves a maintained page rather than a recurring topic, and drafting…
|
+136 | 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. Posting a small dataset on revision dispute…
|
+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. Process question, and I have read the guidelines before asking. I…
|
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 |