Moderator Logs MAJOR IMPROVEMENTS are now LIVE!
Mod Logs v2 is live
I built tagVotes around one idea: moderation should be verifiable, not trusted. If a mod removes your post, you should be able to see who did it, when, and why, and if something feels off, you should be able to check their whole record, not just take our word for it.
The first version of the mod log gave you the basics. v2 goes a lot further.
Here's what just shipped.
What's new
Search mod logs by moderator
Every tag's mod log now supports keyword search on moderator username. Want to see every action a specific mod has taken in a tag? Type their name into the filter. Combine it with date ranges and action types to narrow further.
Public RSS and JSON feeds
Every tag's mod log is now subscribable. Paste the RSS URL into any feed reader or point a script at the JSON endpoint and you'll get every new mod action as it happens.
You don't need to trust us, and you don't need an API key. Audit in real time, build a bot, mirror it elsewhere. It's yours.
Per-user mod history on every profile
Visit any user's profile and you'll now see a Mod History tab showing every action a mod has taken against them, removed posts, removed comments, bans, warnings, reversals. With running totals. Including the count of how many of those actions were later reversed.
This cuts both ways. If you think a user's getting targeted, you can verify. If a mod claims "this user has been warned before," you can check.
Tag settings changes are logged with before/after diffs
When a moderator edits tag rules, description, or settings, the mod log now stores a diff , what it was, what it became, who changed it, when. If a rule quietly appears to justify a removal, it's on the permanent record.
Reversal chains stay visible
When one mod reverses another mod's action, both entries stay in the log, the original action and the reversal. Neither gets hidden. If reversals happen multiple times ("ping-pong"), each step is preserved separately.
You see the full argument play out. We don't rewrite history.
Private-tag logs respect membership
Logs inside private tags are only visible to members of that tag. But inside the tag, the moderators can never hide their own actions from their own members. Same rules as every public mod log, scoped to the people who live there.
A few smaller things I fixed along the way
Ban-modification actions are now correctly attributed to the moderator who changed the ban, not the user who was banned. (Embarrassing bug; good catch.)
UnbanUser actions now appear in the "ban appeals granted" aggregate, not mixed in with generic reversals.
Dismissed-report logs no longer expose the reporter's custom reason text. That was a privacy leak; it's gone.
Comment-restored and post-restored notifications are now separately opt-in-able in your notification preferences (previously bundled under the "removed" toggle).
Why this matters
On most platforms, moderation is a black box. The mod acts, the content disappears, and "the decision is final." That's fine for companies that want plausible deniability. It's not fine for a community.
Every feature in this update exists so you can verify rather than trust. Search what happened. Subscribe to what's happening. Check the record on any user, including yourself. Read the diffs. Watch the reversals.
Mods aren't going anywhere, every community needs them. But on tagVotes, the condition of the job is that your work is on the record, in public, by default.
Questions, feedback, bugs? Drop them in the comments or the meta Tag. The mod log is itself open. If you spot something the tool should show that it doesn't, I want to hear it.
— Spring
)
