- Issue created by @ressa
- 🇬🇧United Kingdom scott_euser
Hmmm yeah I can see small overlap, though I personally have no problem with AI going wild on cached pages (great: better training for LLM + more likely to get AI Overview traffic), really this module is specifically for views exposed form which Protect Form Flood Control doesn't cover per ✨ Add support for views-exposed-form Active .
Do you have a suggestion for what text could go on the homepage? I haven't used crawler rate limit because I'd normally do that via Cloudflare
- 🇩🇰Denmark ressa Copenhagen
Thanks for a fast answer, and just to be clear, I do think this module is a great addition - the other module works very differently.
It could be something like this?
There's a slight overlap with Crawler Rate Limit → , but it requires more configuration, where this module is simpler to set up.
Some block aggressive IP's manually via .htaccess → , where this module could serve as an automated alternative.
- 🇬🇧United Kingdom scott_euser
Thanks! In the end I modified what you wrote to fit in the alternative/complementary approaches section of the module homepage: https://www.drupal.org/project/protect_views_flood_control#module-project--alternatives →
Thank you
- 🇩🇰Denmark ressa Copenhagen
That's a great method, laying out the multitude of options available to solve this challenging task, thanks!
Though I did add a caveat about blocking via .htaccess, so a link to the main doc page https://www.drupal.org/docs/administering-a-drupal-site/security-in-drup... → could be considered instead? I will attempt to keep it up to date, with the latest developments in this ever evolving space:
- [...]
- Using other modules or strategies to block or throttle bots →
- Or considering further approaches based on this blog post from @smustgrave