> They all put up browser surveillance / captcha blockwalls to "stop bots" (even despite bots being legitimate shoppers these days!) that make the sites just straight up not work on most of my browser configs.
What do you mean by this? For example, we do escalating proof of work and I'm not sure how this would make a site not work, even for very exotic configs with high risk signal (e.g. spoofed user-agent, proxies, etc). It will definitely consume more CPU cycles, but I don't see how it would affect functionality.
What do you mean by this? For example, we do escalating proof of work and I'm not sure how this would make a site not work, even for very exotic configs with high risk signal (e.g. spoofed user-agent, proxies, etc). It will definitely consume more CPU cycles, but I don't see how it would affect functionality.
Disclosure: I work for Friendly Captcha.