# Bloquer la récente vague de spam

**URL:** https://meta.discourse.org/t/blocking-recent-wave-of-spam/314867
**Category:** Support
**Created:** [Juillet 3, 2024, 10:43 UTC](https://meta.discourse.org/t/blocking-recent-wave-of-spam/314867 "2024-07-03T10:43:09Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![juanjosegzl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/juanjosegzl/32/511141_2.png) [@juanjosegzl](https://meta.discourse.org/u/juanjosegzl)
#### Post date: [Juillet 13, 2025, 6:09 UTC](https://meta.discourse.org/t/blocking-recent-wave-of-spam/314867/17 "2025-07-13T18:09:17Z")

</div>

Bonjour à tous 👋

J’ai une preuve de concept de cela, si vous voulez y jeter un œil

> **[GitHub - juanjosegzl/discourse-geo-blocking](https://github.com/juanjosegzl/discourse-geo-blocking)**
>
> Contribute to juanjosegzl/discourse-geo-blocking development by creating an account on GitHub.

> [@Blocking recent wave of spam](https://meta.discourse.org/t/blocking-recent-wave-of-spam/314867/12?u=juanjosegzl):
>
> FYI my [Geo Blocking plugin](https://meta.discourse.org/t/geo-blocking-plugin/227824) can deny access to Discourse based on the source AS network. Indeed a lot of this kind of spam seems to originate from those networks, especially AS45609. If you don’t want to block half of India then it might be worth investigating how hard it would be to reuse some of the functionality in that plugin to add network or IP based rules to the approval logic (“require approval for new posts from networks”)

---

_[View the full topic](https://meta.discourse.org/t/blocking-recent-wave-of-spam/314867)._