3 ms·

There's a special place in hell for people who block curl and wget, especially on sites with downloadable files (eg source code tgz's, media, etc.), basically a

There's a special place in hell for people who block curl and wget, especially on sites with downloadable files (eg source code tgz's, media, etc.), basically anything i might need to wget on a server.

Bender 3mo ago
A guy gets sent to hell. The demons guide him into the lobby. Satan jumps out and lets out a big evil roar to no effect. Satan then glances down and sees the spot on the mans finger where there was a ring. "Oh... well you've been through worse. The break room is down the hallway to the left, mail room is upstairs to the right..." Satan just walks away. 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.
- strken 3mo ago
  Huh. I should probably add a .curlrc file with a generic Chrome UA and see if it can get past the most annoying filters. This has always struck me as dishonest, but recently I've been blocked from accessing the docs of a service I pay for.
BLKNSLVR 3mo ago
There's this weird entitlement people have in which they think that the author of a site is not allowed to choose the method by which they protect their own site because it may be inconvenient to their specific, niche, use case. Although @Bender's unique answer is better than my obvious observation.
- inigyou 3mo ago
  saying you shouldn't do it is also allowed
  - BLKNSLVR 3mo ago
    So long as a some half-decent explanation of reasoning is provided. 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.
    - inigyou 3mo ago
      That's a long list of things you want to block. Can you even name what you don't want to block?
    - ajsnigrutin 3mo ago
      I gave my explanation, i sometimes have to download something to a server, and this means that I have to download it to my pc first and then scp it, sometimes over an extra server in the middle to get the file to where I want it. 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.

Bender 3mo ago

A guy gets sent to hell. The demons guide him into the lobby. Satan jumps out and lets out a big evil roar to no effect. Satan then glances down and sees the spot on the mans finger where there was a ring. "Oh... well you've been through worse. The break room is down the hallway to the left, mail room is upstairs to the right..." Satan just walks away. 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.

strken 3mo ago
Huh. I should probably add a .curlrc file with a generic Chrome UA and see if it can get past the most annoying filters. This has always struck me as dishonest, but recently I've been blocked from accessing the docs of a service I pay for.

BLKNSLVR 3mo ago

There's this weird entitlement people have in which they think that the author of a site is not allowed to choose the method by which they protect their own site because it may be inconvenient to their specific, niche, use case. Although @Bender's unique answer is better than my obvious observation.

inigyou 3mo ago
saying you shouldn't do it is also allowed
- BLKNSLVR 3mo ago
  So long as a some half-decent explanation of reasoning is provided. 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.
  - inigyou 3mo ago
    That's a long list of things you want to block. Can you even name what you don't want to block?
  - ajsnigrutin 3mo ago
    I gave my explanation, i sometimes have to download something to a server, and this means that I have to download it to my pc first and then scp it, sometimes over an extra server in the middle to get the file to where I want it. 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.