People editing posts into spam

AI-generated summary

A discussion is taking place about how to handle users editing their posts into spam on a customer support forum. bombledmonk shared an instance where a user edited their post eight days later with a Vietnamese gambling site, which wasn’t caught for nearly two months.

Suggestions to combat this behavior include limiting the time allowed to edit a post pfaffman, dax, and setting a time limit through the post edit time limit site setting. DeanMarkTaylor recommends using the Discourse Moderator Attention plugin, which highlights modified posts for moderators.

Others suggest running edits through Akismet, especially if the edit occurs after several days and the user has a low trust level cpradio, codinghorror. eviltrout mentions that implementing this change might not be too difficult.

However, codinghorror notes that instead of implementing this change, trust level based edit time limits were introduced, with lower trust levels having shorter allowed edit windows. Stephen and bombledmonk share concerns that wiki edit spam is still a problem, but codinghorror questions the severity of the issue due to a lack of evidence.

So this is a “How would you handle it?” question.

I have a customer support forum and had a person come on the forum and post a very legitimate question, the question was promptly answered and the post was buried as is natural. Eight days later this person came back and edited his post replacing the contents with a Vietnamese gambling site, but it wasn’t caught for a nearly 2 months. Since this wasn’t the last post, the thread didn’t get bumped and brought to anyone’s attention. Does anyone have ideas on how one might combat or keep on top of this type of behavior?

That’s a very clever and devoted spammer!

You might reduce the time allowed to edit a post.

The simplest thing that comes to mind is limiting the number of minuts available to edit your post by modifying the site setting post edit time limit.

There is a specific plugin that would handle this situation:
https://github.com/discourse/discourse-moderator-attention

I believe it works like this:
Modifications / new posts on the end bump the visibility of the topic in the topic list and once a moderator has read the post it would return to it’s original position and no longer be highlighted for moderators.

Regardless of me perhaps being incorrect about the movement in position at least it’s highlighted with an asterisk for moderators.

Official description:

Discourse Moderator Attention

This plugin was designed for heavily moderated sites, once installed we track which moderator read which post and when.

Any unmoderated topics (topics with at least 1 unmoderated post) will be displayed in the topic list with and asterisk for moderators only.

Food for Thought:
Do edits run through Akismet? Should they? Especially if the edit happened after several days and the User is TL 1 or less?

Good question! @eviltrout I think TL0 edits should go through Akismet but this might be a big change?

I took a peek at the code I wrote and it seems like it wouldn’t be an awful amount of work to add a new state of edited and have it go through Akismet. The time consuming part is testing it to make sure it all works as expected. I’m a bit busy right now but probably someone else on the team could handle that.

Это изменение уже произошло? Спам правками в вики всё ещё очень актуален.

Нет, вместо этого мы внедрили временные ограничения на редактирование в зависимости от уровня доверия. Таким образом, пользователи TL0 и TL1 по умолчанию имеют гораздо меньшее окно для редактирования — 24 часа. Пользователи TL2 получают 30 дней.

Хорошо, есть ли сейчас какие-либо меры против спама при редактировании вики?

Это серьёзная проблема? Я имею в виду, у нас нет доказательств того, что это действительно происходит. Я не принимаю решений, основываясь на слухах или теориях.

Да, я уже сталкивался с этим.

Кроме того, я ранее сообщал о том, что это происходит с постами вики здесь, на meta.

Но, с вашего позволения, вы — лишь одна точка данных.

С нами это случалось как минимум в 4 разных случаях. Серьёзно? Нет. Сложно отследить? Да. Мы наткнулись на это случайно, так как правки не поднимаются вверх списков активности. Возможно, есть и другие случаи, которые мы ещё не обнаружили. Думаю, установка TL0 на 24 часа — неплохой вариант. Я давно этого не замечал, так что, возможно, это решило бы наши проблемы, если бы такая настройка стала стандартной ещё некоторое время назад.