# Watching / Tracking / Notifications for post edits for Moderators

**URL:** https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529
**Category:** Feature
**Created:** [2016年三月3日 19:12 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529 "2016-03-03T19:12:00Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [2016年三月3日 19:12 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/1 "2016-03-03T19:12:00Z")

</div>

There doesn’t appear to be a way to get notified for post edits…  
(both traditional post edits and Wiki post edits).

For post traditional post edits and Wiki post edits.

### As a user

For users this topic seems to be tracking this:

> [@Not receiving notifications for edited Wiki posts unless you are the author](https://meta.discourse.org/t/not-receiving-notifications-for-edited-wiki-posts-unless-you-are-the-author/24340):
>
> This is something strange. I have made one topic a wiki post and kept it open. Then inside another browser I login with a different user id. I edited the wiki post and then I checked the forum on my admin ID. I did not received any notification whatsoever that could tel me that someone actually contributed to the post and edited it? Am I missing something here or some setting is required. Why are we not receiving notifications for wiki post edits? Is the original author of wiki post the sole pu…

### As an admin / moderator…

Whilst moderation / approval prior to posts initially being displayed is not required, knowing something has changed so it can be reviewed is important.

**It’s important to be able to know when every content change occurs for moderation purposes.**

Some organisations require a “content review” for every piece of content on their site, even if occurs sometime later.

* * *

Is there any way of handling this currently?

Or list of posts recently “edited” outside of the initial ninja edit period…  
… and perhaps receiving notifications for these?

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [2016年三月3日 22:41 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/2 "2016-03-03T22:41:29Z")

</div>

The only way I know of to “catch” post edits is on Latest from the “.. updated topics, click to show”  
i.e. if there is no new or unread indicator, it’s an edit.

At SitePoint, we decided to compromise between having the convenience of member’s being able to edit their posts and the inconvenience of Moderators keeping track of post edits.

IMHO it is unrealistic to expect Moderators to “ride” Latest on the chance that a previously seen OK post has been edited into a Not OK post.

And I guess it is also unrealistic to expect Moderators to read every post. Though if for only for certain Categories, it could be a more acceptable approach.

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [2016年三月3日 22:43 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/3 "2016-03-03T22:43:36Z")

</div>

> [@Mittineague](#):
>
> The only way I know of to “catch” post edits is on Latest from the “.. updated topics, click to show” i.e. if there is no new or unread indicator, it’s an edit.

This only works for edits to the last post in a thread.

Any edits to posts above the last one I believe are un-trackable currently unless you are the author of the post that has been edited.

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [2016年三月3日 23:35 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/4 "2016-03-03T23:35:09Z")

</div>

> [@DeanMarkTaylor](#):
>
> This only works for edits to the last post in a thread.

Yes, and with our shortened post edit time limit this is usually good enough.  
Community Flagging helps some.  
But I think the fact that the post edit time limit is shorter than a typical visit cycle helps the most.

That is, if a Not OK edit happened, the chance of one of the many Moderators reading the post for their first time is almost certain.

We did try a post edit time limit more in line of what it was in vBulletin, but many wanted to be able to add “oh, I forgots”, fix typos, rephrase more clearly etc. so it was lengthened a bit.  
Personally, I have no problem with a later “oh I forgot” post, and I make so many typos myself I hardly give them second thought when others make them. But folks are different after all.

In any case, I strongly feel the default setting is way too generous. i.e.

Admin → Settings [Posting]

> post edit time limit 86400  
> The author can edit or delete their post for (n) minutes after posting. Set to 0 for forever.

That’s 60 days ![](https://global.discourse-cdn.com/meta/original/3X/d/f/df0b883d77019e0e80d6191082b5a471b10e6f58.gif)

If not already, maybe edited posts could be passed through Akismet?

Maybe the post\_revisions table could be used for a Moderator page?

Such a page would likely be mostly typo fixes, bu it would be easier than relying on Moderators to read / reread posts looking for the “# edit pencil”

---

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [2016年三月4日 05:35 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/5 "2016-03-04T05:35:45Z")

</div>

> [@DeanMarkTaylor](#):
>
> This only works for edits to the last post in a thread.

One workaround for wiki posts is to do the following:

1. Make the OP a wiki post
2. Link to another topic within the OP as the official ‘discussion’ topic for this post
3. Close the topic
4. Delete the “Moderator closed this topic” post.

Now the OP is the last post, and edits will make it bump to the top of the topic list.

Also, people entering the topic will always enter at the first post.

Discussion can happen in the separate topic if necessary.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2016年三月4日 06:30 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/6 "2016-03-04T06:30:45Z")

</div>

> [@DeanMarkTaylor](#):
>
> It’s important to be able to know when every content change occurs for moderation purposes.

We have a plugin for this which we built for @Bill_S at Western Digital:

[https://github.com/discourse/discourse-moderator-attention](https://github.com/discourse/discourse-moderator-attention)

Its designed for sites that need 1 moderator to read every single post or edit to a post.

---

<div class="post-metadata">

### Author: ![Bill\_S](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Bill\_S](https://meta.discourse.org/u/Bill_S)
#### Post date: [2016年三月4日 17:53 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/7 "2016-03-04T17:53:34Z")

</div>

And it’s working great for my team. I have had issues in the past with users coming back later and editing posts to add unsavory content. The moderation flags help us catch those things many times before others even see them. I’m sure that it’s what you’re looking for.

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [2016年三月6日 01:44 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/8 "2016-03-06T01:44:29Z")

</div>

In the same vain - “moderating all content” - is there anything for profile content edits?

---

<div class="post-metadata">

### Author: ![anon61128213](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@anon61128213](https://meta.discourse.org/u/anon61128213)
#### Post date: [2018年二月21日 16:23 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/9 "2018-02-21T16:23:02Z")

</div>

Lately we often get posts that look fishy, but don’t contain spam (yet). Us moderators are just waiting for the edit to include the spam-link. Bookmarks help, but it can be tedious work.  
And spammers are not dumb. They are waiting for someone to reply and then edit their first post so it won’t bump the topic.  
Maybe an adaption of the function to change ownership of a post could be the solution here. If a moderator could make themselves co-owner of a post (without OP noticing) then they’d get edit-notifications.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018年二月21日 20:09 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/10 "2018-02-21T20:09:59Z")

</div>

Why not set your allowed edit interval to something much smaller like 7 days? That seems like a far simpler solution.

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [2018年二月21日 20:34 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/11 "2018-02-21T20:34:14Z")

</div>

I haven’t noticed many late edit link additions on the forum where I’m a moderator.

What we have noticed at times is changing post content after it has received replies that make a mess of the discussion and aggravates participants. eg.

“I need help with ABC”  
“Try doing XYZ”

but after the edit, the topic reads as

“I need help with DEF”  
“Try doing XYZ”

making the reply incorrect.

\* it should be noted that this type of behavior has been limited to a handful of members and not a wide spread problem. moderator messages helped somewhat.

We have our edit time window low, hours _not_ days.

I think some type of “if replies disable edits to previous posts” might work. But the problem of allowing cosmetic edits (eg. to → too) while preventing substance edits can’t be solved by simple code.

---

<div class="post-metadata">

### Author: ![anon61128213](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@anon61128213](https://meta.discourse.org/u/anon61128213)
#### Post date: [2018年二月21日 20:39 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/12 "2018-02-21T20:39:57Z")

</div>

> [@codinghorror](#):
>
> Why not set your allowed edit interval to something much smaller like 7 days?

TBH I don’t know what it’s set to, but I believe this is true for our forum too:

> [@Mittineague](#):
>
> hours not days.

For now I’m using user topic timers, to check up on shady posts and I guess that’s a good enough solution. If I don’t catch a spam link right away, but a few hours later what harm can it really do?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018年二月21日 23:49 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/13 "2018-02-21T23:49:42Z")

</div>

Do you _really_ have users coming back more than 1 day later to edit spam into their posts? That seems.. unlikely. I’d need to see data on that.

In the meantime, we are adding a feature that prevents TL0 users from enjoying edit grace periods, as in every edit to their posts are tracked. This is because we have seen bamwar spammers abuse this, multiple times, across multiple sites.

---

<div class="post-metadata">

### Author: ![anon61128213](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@anon61128213](https://meta.discourse.org/u/anon61128213)
#### Post date: [2018年二月27日 18:16 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/14 "2018-02-27T18:16:11Z")

</div>

> [@codinghorror](#):
>
> Do you really have users coming back more than 1 day later to edit spam into their posts? That seems… unlikely. I’d need to see data on that.

Well it doesn’t happen often and it would be hard to find old deleted post where it did, but coincidentially it just happened again. A post from 4 days ago got edited to add a spam link:

 ![Screenshot%20from%202018-02-27%2019-06-20](https://global.discourse-cdn.com/meta/original/3X/7/5/75bdefcdabc66d1432fe0b2402fdc1bb5f3476d4.png)

Actually it was more than 4 days between writing and editing the post as it spent about 1 day in the approval queue. It was a bit shady from the beginning, so we didn’t know if we should approve it, but then we decided to “see how it plays out” since we didn’t have enough evidence to kick them right away.

Anyway I guess your suggestion of abandoning the grace period for TL0 users is probably a great solution.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018年三月14日 22:39 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/15 "2018-03-14T22:39:13Z")

</div>

> [@anon61128213](#):
>
> Anyway I guess your suggestion of abandoning the grace period for TL0 users is probably a great solution.

Per @sam the solution that was implemented is mandatory tracking of all revisions in the grace period greater than `{x}` characters. There are two site settings for this, one for low trust users and one for high trust. Check your site settings.

---

<div class="post-metadata">

### Author: ![md-misko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/md-misko/32/126315_2.png) [@md-misko](https://meta.discourse.org/u/md-misko)
#### Post date: [2020年二月1日 15:24 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/16 "2020-02-01T15:24:43Z")

</div>

> [@Bill\_S](#):
>
> 过去我曾遇到过用户事后返回并编辑帖子以添加不当内容的问题。审核 **标记** 功能帮助我们多次在其他人看到之前就发现了这些问题。

我的理解是否正确：此插件应在用户超出“忍者编辑”时间窗口编辑帖子时（至少针对 tl0 和 tl1 用户）触发审核标记？

如果是这样，引入新的审核队列后这一机制是否发生了变化？我使用的是最新版本，如果一个 tl0 用户创建了一个帖子，随后完全更改了内容（远超 100 个字符），却既没有触发标记，主题标题前也没有星号。

我之前从未使用过此插件，因此不确定我的预期是否合理。

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2020年二月3日 01:13 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/17 "2020-02-03T01:13:14Z")

</div>

At most 它会添加一个星号，快速浏览代码后发现，即使用户进行“复活编辑”，也不会重复添加星号。

我认为你需要采用不同的模式或对插件进行一些修改，以在插件中处理“复活编辑”的情况。

---

<div class="post-metadata">

### Author: ![md-misko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/md-misko/32/126315_2.png) [@md-misko](https://meta.discourse.org/u/md-misko)
#### Post date: [2020年二月3日 07:25 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/18 "2020-02-03T07:25:01Z")

</div>

> [@sam](#):
>
> 我认为你需要不同的模式或对插件进行一些修改，以处理插件中的“复活”编辑。

其他人是否也会觉得这个功能有用呢？至少为 tl0（或许还有 tl1）的“复活”编辑添加一个标记，可以提醒版主注意可能的垃圾信息编辑。

我不确定从技术角度来看实现这个功能的难度有多大？

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2020年二月3日 09:35 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/19 "2020-02-03T09:35:20Z")

</div>

为 tl0/1 上的每个“复活编辑”设置标记会非常嘈杂，不太可能有社区会使用这样的自定义设置。

通常，面临此类困扰的社区会直接禁用 tl1 的复活编辑功能（据我所知，tl0 已经禁用了）。

从技术上讲，开发一个在每次复活编辑时自动标记的插件非常简单。

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [2020年二月3日 10:56 UTC](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529/20 "2020-02-03T10:56:56Z")

</div>

为了不跑题，我想提个建议。

很久以前，我曾在本地服务器上测试过这个插件。它的表现并未完全符合我的预期（即无论帖子在主题中的位置如何，每次编辑都会发送通知）。我曾尝试研究如何对其进行改进，但最终放弃了。

现在我认为，更可行的方案可能是为版主设置一种特殊的“已读状态”条件或排序置顶功能。这意味着需要扫描主题列表以查找相关标识，但这样不会造成过多的干扰。而且，如果没有排序置顶，根据编辑发生的时间远近，查找过程可能会耗时较长。

[下一頁](https://meta.discourse.org/t/watching-tracking-notifications-for-post-edits-for-moderators/40529.md?page=2)
