Post #2676130
2026-04-23 16:27 UTC
@jsstaedtler@mastodon.art ah okay. i imagine that probably limits you from any making any apache/nginx configuration settings changes (e.g. IP blocklists)
i'm not familiar with your site generation code - but if you wrote it yourself, i *think* the trick would be to have it 404 when an incorrect tag has been used
https://stackoverflow.com/questions/1381123/how-to-create-an-error-404-page-using-php
at least then the script can die() instead of yielding output. it's anyone's guess if the crawler will still continue to try generating tags when it has encountered a 404, but i *assume* they're built to avoid 404s
Replies (1)
-
@jsstaedtler@mastodon.art 2026-04-23 16:59
@vga256@mastodon.tomodori.net The server is managed with cPanel which provides a surprising amount of options, including IP blocking; and .htaccess files give me some good control over Apache. So I can certainly handle *known* bad actors. It does look like I need to pick a threshold of behaviour that will result in a 404 or some other dead end. I can imagine a human legitimately filtering on 2-3 tags, but more than that (as well as invalid combos) could be denied.