this post was submitted on 24 Jul 2024
1 points (100.0% liked)
Technology
59587 readers
5236 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yep. I block all bots to my instance.
Most are parasitic (GPTBot, ImageSift bot, Yandex, etc) but I've even blocked Google's crawler (and its ActivityPub cralwer bot) since it now feeds their LLM models. Most of my content can be found anyway because instances it federated to don't block those, but the bandwidth and processing savings are what I'm in it for.
Teach me oh wise one
Kinda long, so I'm putting it in spoilers. This applies to Nginx, but you can probably adapt it to other reverse proxies.
map-bot-user-agents.conf
Here, I'm doing a regex comparison against the user agent (
$http_user_agent
) and mapping it to either a0
(default/false) or1
(true) and storing that value in the variable$ua_disallowed
. The run-on string at the bottom was inherited from another admin I work with, and I never bothered to split it out.'map-bot-user-agents.conf'
Once you have a mapping file setup, you'll need to do something with it. This applies at the virtual host level and should go inside the
server
block of your configs (except the include for the mapping config.).This assumes your configs are in conf.d/ and are included from nginx.conf.
The
map-bot-user-agents.conf
is included above theserver
block (since it's anhttp
level config item) and insideserver
, we look at the$ua_disallowed
value where 0=false and 1=true (the values are set in the map).You could also do the mapping in the base
nginx.conf
since it doesn't do anything on its own.If the
$ua_disallowed
value is 1 (true), we immediately return an HTTP 444. The444
status code is an Nginx thing, but it basically closes the connection immediately and wastes no further time/energy processing the request. You could, optionally, redirect somewhere, return a different status code, or return some pre-rendered LLM-generated gibberish if your bot list is configured just for AI crawlers (because I'm a jerk like that lol).Example site1.conf
I've always been told to be scared about
if
s in nginx configsYeah,
if
's are weird in Nginx. The rule of thumb I've always gone by is that you shouldn't try toif
on variables directly unless they're basically pre-processed to a boolean via amap
(which is what the user agent map does).So I would need to add this to every subdomain conf file I have? Preciate you!
I just include the
map-bot-user-agents.conf
in my basenginx.conf
so it's available to all of my virtual hosts.When I want to enforce the bot blocking on one or more virtual host (some I want to leave open to bots, others I don't), I just include a
deny-disallowed.conf
in theserver
block of those.deny-disallowed.conf
site.conf
Okay yeah I was thinking my base domain conf but that’s even better.
I have two questions. How much do those bots consume your bandwidth? And by blocking search robots, do you stop being present in the search results or are you still present, but they do not show the content in question?
I ask these questions because I don't know much about the topic when managing a website or an instance of the fediverse.
Pretty negligible per bot per request, but I'm not here to feed them. They also travel in packs, so the bandwidth does multiply. It also costs me money when I exceed my monthly bandwidth quota. I've blocked them for so long, I no longer have data I can tally to get an aggregate total (I only keep 90 days). SemrushBot alone, before I blocked it, was averaging about 15 GB a month. That one is fairly aggressive, though. Imagesift Bot, which pulls down any images it can find, would also use quite a bit, I imagine, if it were allowed.
With Lemmy, especially earlier versions, the queries were a lot more expensive, and bots hitting endpoints that triggered a heavy query (such as a post with a lot of comments) would put unwanted load on my DB server. That's when I started blocking bot crawlers much more aggressively.
Static sites are a lot less impactful, and I usually allow those. I've got a different rule set for them which blocks the known AI scrapers but allows search indexers (though that distinction is slowly disappearing).
I block bots by default, and that prevents them from being indexed since they can't be crawled at all. Searching "dubvee" (my instance name / url) in Google returns no relevant results. I'm okay with that, lol, but some people would be appalled.
However, I can search for things I've posted from my instance if they've federated to another instance that is crawled; the link will just be to the copy on that instance.
For the few static sites I run (mostly local business sites since they'd be on Facebook otherwise), I don't enforce the bot blocking, and Google, etc are able to index them normally.
Thanks for the explanation and it was clear to me.