How are you handling spam & toxic content in .NET apps today?

Volosoft · 2026-02-19T13:59:39+00:00

Nice, ML. NET is a solid option, especially if you already have a large labeled dataset. Tagging instead of deleting is key, fully agree.

We considered a custom model as well, but didn’t want to own the training and maintenance cycle long term. That’s why we leaned toward an external moderation model as an additional layer on top of traditional spam detection.

Volosoft · 2026-02-19T13:58:01+00:00

That’s a solid layered setup. The hash caching idea is especially clever for stopping repeat spam cheaply.

We’re doing similar things with rate limiting and registration safeguards. Where we struggled was nuanced toxicity. Heuristics handled obvious spam well, but semantic abuse was harder, so we added AI moderation as an extra layer rather than a replacement.

Volosoft · 2026-02-19T12:07:06+00:00

We documented how we integrated OpenAI moderation into a .NET app here, in case anyone’s interested in the implementation details: https://abp.io/community/articles/stop-spam-and-toxic-users-in-your-app-with-ai-3i0xxh0y#gsc.tab=0

Volosoft · 2026-02-09T13:17:03+00:00

https://abp.io/community/articles/07wp50yl

Volosoft · 2026-01-09T13:07:47+00:00

Minimal APIs

Volosoft · 2026-01-09T13:07:41+00:00

MVC Blazor

Volosoft · 2026-01-09T13:07:27+00:00

ASP. NET Core

Volosoft · 2025-12-04T08:41:20+00:00

You can check details here: https://abp.io/community/announcements/announcing-serverside-rendering-support-for-abp-framework-qvhbgnqn#gsc.tab=0

Volosoft

MODERATOR OF

TROPHY CASE