Every step is optional of course. There are ways to make curl work on my site but I choose to add friction as some botters abuse libcurl. I doubt anyone else will do what I do. They could spoof the user-agent but most botters seem to not know how to do that despite the myth that they all do.
For what it's worth if I had a site specific to sharing code artifacts or archives I would not block curl and I would also enable native rsyncd.
This has always struck me as dishonest, but recently I've been blocked from accessing the docs of a service I pay for.
Although @Bender's unique answer is better than my obvious observation.
Plenty of people would say that I shouldn't block residential proxies, but I would 100% block residential proxies if I could.
I think most people responsible for blocking traffic would actively manage their rules if it was costing them something valuable. If they don't notice, then, well no harm no foul.
Blocking vpns is the same kind of bad... with governments requiring you to show your ID or do a face scan just to jerk off, vpn usage will go up, and you'll be blocking all those people for no good reason.
Sure, you can block whatever you want, and i can and will hate you for that.