Recent content by ramu420

usually the more unique IPs per request you can do, the better, you spread server-side rate-limits that way. You can also start thinking of TLS fingerprinting (e.g. JA3) to avoid getting flagged by some more enhanced WAFs/CDNs, there are plenty of open source http clients for that nowdays.

mobile IPs use CGNAT, gives you a little more wiggle room when it comes to abuse detection.

yes, proxies and a good anti-detect browser stack as javascript APIs expose quite a lot about your device. You could get partial/uneven language recognition if your proxy IP is from the US but your device/OS is using another language.

try more isp providers before ditching that route, those should be enough to stream without getting blocked as long as the overall IP reputation is decent, they are built on heavy dedicated infrastructure (most wholesale sellers use 10G/100G DIA ports), so you should be fine.

On your first idea, you can use ADB (Android) to mimic tap/swipe/keyboard/etc... events, but to be honest with you I have no clue how deep the "detection" goes on fabricated touch events, I would imagine the bare minimum checks are in place on e-commerce platforms (e.g. timing, positioning...

If your goal is to just get it done you will not have the time to learn programming from scratch. AI helps here, it works best for web apps (mainly React), prompt it to make a responsive website with mobile focused UI/UX. As for the backend logic, be careful using AI, it can introduce serious...

Then we agree: - Both rotating and static residential proxies are heavily probed and categorized based on their behaviour by the IP databases you use for your own service/infrastructure. - "Big tech" either by querying said databases or using their own assess the risk of an IP and still let...

You've mentioned KYC and client-side bot protections (Akamai, PX, Shape, DD, or whatever), we're talking about different things. Static ISP proxies can't be detected via an ASN check, the ASN is residential by definition, it's what makes them "ISP" in marketing terms. I mentioned what...

learning to program takes time, if you have no time but you're familiar with AI automation try to offer that as a service (e.g. automate companies manual workflow).

Yes and no, major proxy companies selling residential data are constantly pool scanned/probed and it's kind of known how big their pools really are and what IPs are in them. I would not say big tech is blocking all flagged traffic, they do let some through for whatever reason, false positives...

I imagine there's some demand if you've got two resellers asking for dongles to be setup. I'd give it a shot, just make sure these guys are not wasting your time.

Big brand VPNs = best pricing, worst IP reputation. Proxies = the IP reputation is more of a selling point compared to VPNs -> you'll probably get better IPs out of it. If you got blocked using a popular VPN on your target website chances are it'll happen again, try a decent static residential...

Yep, not the best for Vercel considering NextJS is their "flagship", I did check the dash though and they added a very straightforward auto-pull request feature to up the dependencies for GitHub linked projects. I'd also imagine their WAF is blocking most probing for R2S like Cloudflare.

SOCKS5 is just a protocol, instead of parsing HTTP requests and proxying them with biased logic it tunnels data back and forth transparently, this gave it a more "anonymous" reputation over the years as the software used to make HTTP proxies messed up headers (order was off, new ones were added...

Depends on your target audience, but both have a big place in the market. Price is at an all time low for both resis and statics, you've got unlimited resi pools (unlikely to have any decent IPs in them, but they work for some people) killing price per GB, then you've got shared ISPs marketed...