<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>举报系统 on PlumePHP</title><link>https://plumephp.com/tags/%E4%B8%BE%E6%8A%A5%E7%B3%BB%E7%BB%9F/</link><description>Recent content in 举报系统 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Thu, 23 Dec 2021 19:37:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E4%B8%BE%E6%8A%A5%E7%B3%BB%E7%BB%9F/index.xml" rel="self" type="application/rss+xml"/><item><title>游戏服务器玩家举报证据流水线架构设计</title><link>https://plumephp.com/game-server-player-report-evidence-pipeline-architecture/</link><pubDate>Thu, 23 Dec 2021 19:37:00 +0800</pubDate><guid>https://plumephp.com/game-server-player-report-evidence-pipeline-architecture/</guid><description>&lt;p&gt;玩家举报系统如果只是一张表，很快就会变成没人信的摆设。被举报者质疑处罚依据，举报者看不到反馈，审核员面对一堆缺少上下文的文本和截图，运营只能靠经验判断。游戏服务器侧要做的不是替代人工审核，而是把关键证据在正确时间采样、关联、留存，并让处罚执行可追溯。证据流水线架构关注三个问题：举报发生时能拿到什么证据，审核时如何还原上下文，处罚后如何支持申诉。&lt;/p&gt;</description></item></channel></rss>