Ban based on post text

NateS

I'd like to automatically suspend users that post specific text. For example Temu coupon. Is there an extension that can do this?

If not, can you point me in the right direction for how I'd do it myself? I already have an extension that does a few things.

Cheers!

luceos

There's an extension to filter words but not to van users using these words:

https://flarum.org/extension/fof/filter

NateS

Thanks. The banning part is very important! Maybe I can use that extension as an example to add banning.

NateS

In my spamblock fork I permanently delete the user and all their posts:
EsotericSoftware/spamblockblob/master/src/Controllers/MarkAsSpammerController.php

As much as I hate Temu coupon spam, that's too heavy handed to do automatically, so I just want to mark the user as deleted (or suspended or whatever the right terminology is 😬 so they can't post anymore). The offending content should still be posted but marked as deleted.

That way the offensive content won't be seen by muggle forum users, the spammer won't be able to post more than once, I'll see the deleted post and then either delete the user and all their posts or if it was wrong I'll undelete and unsuspend the user. I can still get spam, but not for the same keywords at least.

My PostSaving listener:

class CheckBan {
	public function handle(Saving $event) {
		if ($event->post instanceof CommentPost) {
			$text = $event->post->getParsedContentAttribute();
			if (stripos($text, "temu coupon") !== false) {
				// How to suspend the user and mark the post as deleted?
			}
		}
	}
}

Thanks for your help!

NateS

I tried like the below, but it seems the post has no ID yet. Also regarding $actor, if it's the user posting I'm not sure they are able to "hide" their own post.

class CheckBan {
	protected $bus;

	public function __construct (Dispatcher $bus) {
		$this->bus = $bus;
	}

	public function handle(Saving $event) {
		if ($event->post instanceof CommentPost) {
			$text = $event->post->getParsedContentAttribute();

			if (stripos($text, "temu coupon") !== false) {
				$this->bus->dispatch(
					new EditPost($event->post->id, $event->actor, [
						'attributes' => ['isHidden' => true],
					])
				);
			}
		}
	}
}

Instead of this, for now I just exit;. That causes the user posting to stay at composing their post. That's not great, as it allows them to edit and submit until they get past my keyword filter. I'd like to suspend the user then exit; (or hide the post, if you can help with that).

To suspend the user, is it something like:

$this->bus->dispatch(
	new EditUser($event->actor->id, ACTOR, [
		'attributes' => ['suspendedUntil' => Carbon::now()->addYears(99)],
	])
);

What do I use for ACTOR? I guess the user can't suspend themselves. Should I look up an actor for an admin?

NateS

Alright! This works:

namespace Something\Stuff;

use Illuminate\Contracts\Bus\Dispatcher;
use Flarum\Post\Event\Saving;
use Flarum\Post\CommentPost;
use Flarum\User\User;
use Carbon\Carbon;
use Flarum\User\Command\EditUser;

class CheckBan {
	protected $bus;

	public function __construct (Dispatcher $bus) {
		$this->bus = $bus;
	}

	public function handle(Saving $event) {
		if ($event->post instanceof CommentPost) {
			$text = $event->post->getParsedContentAttribute();
			if (stripos($text, "temu coupon") !== false) {
				$nate = User::findOrFail(1234);
				$this->bus->dispatch(
					new EditUser($event->actor->id, $nate, [
						'attributes' => ['suspendedUntil' => Carbon::now()->addYears(99)],
					])
				);
				exit;
			}
		}
	}
}

And you need this in your extend.php:

(new Extend\Event())
	->listen(PostSaving::class, Listeners\CheckBan::class),

I would still prefer to hide the post, if possible. That way I see that this automatic ban happened and if it was a legit user, I can undo it. With just exit; the post never happens, the user is banned and I don't see it to check if it was a mistake.

clarkwinkelmann

NateS Saving is the event BEFORE the post gets created. Extensions get a chance to throw validation errors here and cancel the creation of the post.

To get access to the ID, you're probably interested in the Posted event.

In some cases where you really need to use data from Saving afterwards, you can register a $model->afterSave(function () {}) callback, but you probably don't need this for the use case you describe.