This is a really solid breakdown of Scrapling's capabilites! The Cloudflare bypass section is particularly intresting because most libraries just throw their hands up when they hit Turnstile. The fact that Scrapling can solve it in headless mode using Camoufox is impressive since that's usually where most stealth approaches break down. I'm curious about the long term maintainability though, given that Cloudflare is constantly evolving their detection methods. Does the library have a regular update cycle to keep pace with those changes, or does the fingerprint spoofing aproach provide enough flexibility that it stays ahead naturally?
Thanks for all your kind words. Yes, I keep maintaining the solver since I released it, and it's actually now working better than when this article was published (updates and all).
The solver has been working since last December, even though I added it to Scrapling in v0.3 (I was using it in my daily job), but this shows that I have been maintaining it for nearly a year now, and I intend to keep doing that with the rest of the library :D
Quick question: would you be open to supporting Kameleo as a browser option as well? I can see how nicely you integrated Camoufox, but since it's no longer actively maintained by Daijiro, it may eventually hit limitations.
Kameleo is a paid solution, but that's precisely what allows us to continuously update our browser kernels and evolve our fingerprint masking, so we can reliably stay ahead in the anti-bot space - especially for serious web-scraping use cases.
Happy to chat anytime if you'd be interested in exploring this together.
This is a really solid breakdown of Scrapling's capabilites! The Cloudflare bypass section is particularly intresting because most libraries just throw their hands up when they hit Turnstile. The fact that Scrapling can solve it in headless mode using Camoufox is impressive since that's usually where most stealth approaches break down. I'm curious about the long term maintainability though, given that Cloudflare is constantly evolving their detection methods. Does the library have a regular update cycle to keep pace with those changes, or does the fingerprint spoofing aproach provide enough flexibility that it stays ahead naturally?
Thanks! Scrapling is definitely a fantastic library.
Regarding the maintainability aspects, I leave it to Karim, the author of the library.
Hello, Scrapling author here.
Thanks for all your kind words. Yes, I keep maintaining the solver since I released it, and it's actually now working better than when this article was published (updates and all).
The solver has been working since last December, even though I added it to Scrapling in v0.3 (I was using it in my daily job), but this shows that I have been maintaining it for nearly a year now, and I intend to keep doing that with the rest of the library :D
Hi Karim. amazing work on Scrapling.
Quick question: would you be open to supporting Kameleo as a browser option as well? I can see how nicely you integrated Camoufox, but since it's no longer actively maintained by Daijiro, it may eventually hit limitations.
Kameleo is a paid solution, but that's precisely what allows us to continuously update our browser kernels and evolve our fingerprint masking, so we can reliably stay ahead in the anti-bot space - especially for serious web-scraping use cases.
Happy to chat anytime if you'd be interested in exploring this together.