fair take - ZP lowered the barrier a lot, no argument there. My point wasn’t “ZP can’t do it”, it’s that scale + heterogenous platforms still means logic debt, you pay it either in code or in visual spaghetti. Proxies + network layer burn accounts faster than browser flags anyway, so people expecting any tool to be plug and play at 3k sites are setting themselves up for pain.
Trueplayer is someone who should be listened too. I do anti detect bots with proxy layers and all that and you shouldn't even share proxy pools on an anti detect layer, let alone any Saas platform.
Do it right, run your own, it's extremly naive to use shared proxy pools, there's a few days worth reading to do about how proxies work, what is dns and how to check them before starting any operation.
Proxy providers are the biggest scammers and liars by omission in this whole field, they are literally recycling rubbishware.
People think residential proxies with rotation are somehow a good thing, when it's an extremly end user hostile practice and a simple money grab which contaminates the pools at a velocity that's incredible.
The anti fraud tools, if a website uses them will know within seconds.
Residential proxies are nowadays required for scraping the golden era is long gone, they can't be used for serious operations.
Which brings us to static isp, which have a limited, but better life time of beand new and the asn and subnet isn't marked as "bad neighborhood".
The people are quick to blame anti detects which they do not really understand to set up either, but the worst offender and pitfall is always the proxies.
I was asked to rest some provider and they had internal dns leaks.
Some providers assign the same ssl cert to tens of thousands of ips.
Mobile proxies kinda require a mobile interface emulator, which are brittle. What ifnthe website tries to trigger open web console, what if Google asks you to open an app on your "phone" etcetera.
