关于新的审核队列(2019)的反馈

The delete user action is found under different top level buttons depending on the type of flag. It would be nice if the Delete button always had a delete user sub action.

And btw, URLs are added to the screened list if you delete from a manually flagged review, just not from user posted too fast reviews.

I just had some odd things happen relating to flagging of a post in a personal message. Two people are in the message (myself and a new moderator I am in the process of onboarding). We were testing out flagging, and she flagged one of her own posts. Both of us received the notification that our message was flagged as spam and that we should edit and fix it, and neither of us could directly reverse the flagging action directly in the post. It also did not show up in the review queue.

While the post was hidden, I selected the post admin wrench but was unable to use it because it was somehow behind the post content. See screenshot.

17%20AM

Only when I edited the post did it get unhidden.

So… several issues:

  • post admin wrench menu not working properly
  • both of us got the moderator warning
  • post did not land in the review queue
  • we were both moderators but neither able to reverse the flagging action
  • should it be possible to flag a moderator post as spam? should a moderator be able to flag their own post as spam? Should anyone be able to flag their own post as spam?
2 个赞

I’ve been loving the improvements here - I’ve finally had a chance to collect my thoughts and accumulate a bit of feedback about this:

  • Assignment filters - Would be good to have additional filters for assignee, if enabled. Reporter might also be useful to add, too.
    • Currently the “user” filter is filtering on the author of the flagged post, but this is a bit ambiguous because of :point_up:
  • Related, this might need a bit better integration with the assignments plugin. Assigning review items do not make them appear in the “assigned” topic list in the plugin.
  • Reports - one item that might be good here is being able to filter by a date range, or export review items across a date range. This might be useful to get a feel with past history of how reviews are handled for new mods.
11 个赞

另一个我们应该添加的功能:让被重新标记的项目除非帖子内容被编辑或以某种方式更改,否则不会重新出现在审核队列中。这应自动忽略新的标记项目,并且无法通知或隐藏该帖子。

这里的想法是,某处的版主已经看到了该标记并进行了处理——任何新出现的(同类型的)项目都应以相同方式处理。

上述内容有一个注意事项:我们可能应该忽略任何新标记,而不是以与标记实际处理方式(例如“同意”)相同的方式自动解决可审核项目,因为这可能会产生意想不到的副作用,即让恶意标记者能够通过标记版主已用“同意 + 保留”处理过的项目来提升他们的标记分数。

9 个赞

很好的观点。补充一点,我定期批准帖子,但随后这些帖子却被 Akismet 标记为垃圾邮件。这种情况也不应该发生。

4 个赞

没错——如果有必要,插件应该仍然能够覆盖上述建议,但我同意 Akismet 在这种情况下不应这样做。这或许更多是 Akismet 插件本身的问题,但这确实是个很好的观点。

5 个赞

这是一个插件问题,我会提交修复。

我已经在着手研究这个问题了。我同意我们应该忽略新的标记,而不是自动解决它们。我在考虑当有人尝试重新标记已审核的帖子时,显示一条错误消息。

我还认为,出于同样的原因,用户应该等待大约 24 小时才能重新标记帖子。

12 个赞

由于所有最新的待处理项目都在“查看全部”菜单中,“审查”标签页应重定向到该菜单,而不是“按主题分组”菜单。

5 个赞

您是否设置了可审查的默认主题?这会导致默认显示主题而不是所有项目,而默认情况下应该是所有项目。

6 个赞

我们刚刚合并了这个功能:

https://review.discourse.org/t/feature-users-cannot-reflag-recently-handled-items-using-the-same-reason-unless-the-post-was-edited-or-it-was-reviewed-more-than-24-hours-ago-8969/9113

7 个赞

根据 https://meta.discourse.org/t/discourse-2-4-0-beta11-release-notes/141548:

可疑用户被发送至审核队列

可疑用户(即查看过少于一条帖子和一个主题,但已自定义个人简介的用户)现在会被发送至审核队列。这类用户很可能是垃圾信息发送者,因为大多数用户会在浏览网站后才会花时间填写个人简介。

我们这里并未出现此情况:新的可疑用户仍会如常出现在 /admin/users/list/suspect 中,但不会出现在审核队列中。这是否取决于某些设置?

1 个赞

是的,该功能依赖于“批准可疑用户”设置(默认禁用)。

9 个赞

太好了,现在可以正常工作了(或许这类信息应该添加到发布说明中)。

不过我有个小请求,希望能帮助我们加快审核流程:能否为网站字段添加链接?目前我们需要手动复制/粘贴,这大大拖慢了我们的进度。

1 个赞

这看起来像是您添加的一个用户字段。很遗憾,我们无法确定这些是否为网址。

“网站”字段?那不是自定义字段(和 Meta 这里一样)。另外两个是,但我不需要它们的热链接。

2 个赞

标准网站字段设为可点击是合理的。如果还能跟踪点击次数就更好了。

我认为你应该能够通过主题组件使自定义字段可点击。

双击、Ctrl+C、Ctrl+T、Ctrl+V、回车

1 个赞

我的错!我在 Meta 上查了一下,我看的那个用户没有网站。再加上我被他正下方的其他用户字段搞混了。这会链接到网站以便更方便地审查:

12 个赞

再仔细想了想,24 小时的冷静期对小型站点来说听起来不错,但我担心在大型站点上,用户仍可能淹没版主。

您认为是否可以将“不可标记”窗口设为可配置变量(或至少在插件中可设置)?任何能减轻版主潜在负担的措施,我都认为是胜利。

另一个不相关的问题:高度受信任的用户可能被视为拥有“版主”权限,能够通过单次标记隐藏帖子。保留旧版隐藏帖子所需的最小标记数量选项可能仍然可取,以防止任何单个社区成员充当审查者。

8 个赞

是的,经过多次反复讨论,我其实并不反对重新设置最小数量。不过,我希望确认 @featheredtoast 的客户已经尝试过其他调整方案,并确定这样做确实会有帮助。

@Roman,我们能否将那个 24 小时的时间窗口设置为可配置的?

7 个赞

已完成:

https://review.discourse.org/t/feature-admins-can-configure-the-reflag-cooldown-window-and-if-posts-flagged-as-spam-by-tl3-users-get-automatically-hidden-9010/9262

可通过 high_trust_flaggers_auto_hide_posts 设置启用或禁用。

可通过 cooldown_hours_until_reflag 设置进行配置(默认为 24 小时)。

6 个赞