Author here. I submitted this a few days ago but seems like it was added to the second chance pool so now it’s on the front page. Anyways, I have received a report from a user that this solver did not work for them with European proxies but did with US proxies… so they may be serving different versions for different regions. I will fix that soon. I’m not at my computer right now but it was working when I tested it a few hours ago (Cloudflare constantly changes things).
My understanding is that there is some sort of rate limiting around PATs per Apple ID (that’s why they require you to be signed in). Also if you want to scale to millions per day you don’t want to have to use headless browsers.
the actual value comes from having a solution which tracks cloudflare, a full LLM pipeline for pulling the most recent obfuscated code, reversing it and updating the current solver. without it, users aren't going to have confidence in the continuity of the solver to build around it.
that said, most of the people who really need it roll their own in-house. don't think I have seen someone post it to github yet.
> the actual value comes from ... [a whole bunch of automation] ... without it, users aren't going to have confidence in the continuity of the solver to build around it.
You're talking like this is a paid service that's attempting to get customers.
This is an MIT-licensed library on Github that's being offered free of charge. Sometimes people just offer what they've been working on up as a gift... one that is "...provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement.", yanno?
for a standalone project that's fine, but when the project's entire purpose is to track and be an adversary to another project...
the problem is that to someone who can't maintain (realistically, get an LLM to do it without running into refusals) this project on their own, any time they spend utilizing it will end up a waste of time.
Even if it just ends up being a base to throw and llm at to update, isn't that still useful? Sounds to me like it'll probably skip the whole part where my agent would have to give me 4 different plans, searches the internet, argues that it's impossible, works out subtools to generate, etc.
For the last few builds released by Cloudflare, I basically just told an agent “Hi they changed something. Please fix.” And waited for a few hours (mostly spent in Rust compilation) until it came back fixed. Keeping the codebase clean while doing that long term is honestly the harder part.
Yes, that was my goal. I will update this for the next couple of weeks, but probably not forever. However I think this is a pretty good foundation for future efforts.
Just out of curiousity, which model did you use and what did you say to convince it to help? I'm pretty sure Claude would have told you to kick rocks.
Author here. I submitted this a few days ago but seems like it was added to the second chance pool so now it’s on the front page. Anyways, I have received a report from a user that this solver did not work for them with European proxies but did with US proxies… so they may be serving different versions for different regions. I will fix that soon. I’m not at my computer right now but it was working when I tested it a few hours ago (Cloudflare constantly changes things).
Is it that difficult? Use a warm Safari profile on a real Mac. Then Turnstile becomes Apple's problem, ie, solved, because they use PAT.
My understanding is that there is some sort of rate limiting around PATs per Apple ID (that’s why they require you to be signed in). Also if you want to scale to millions per day you don’t want to have to use headless browsers.
the actual value comes from having a solution which tracks cloudflare, a full LLM pipeline for pulling the most recent obfuscated code, reversing it and updating the current solver. without it, users aren't going to have confidence in the continuity of the solver to build around it.
that said, most of the people who really need it roll their own in-house. don't think I have seen someone post it to github yet.
> the actual value comes from ... [a whole bunch of automation] ... without it, users aren't going to have confidence in the continuity of the solver to build around it.
You're talking like this is a paid service that's attempting to get customers.
This is an MIT-licensed library on Github that's being offered free of charge. Sometimes people just offer what they've been working on up as a gift... one that is "...provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement.", yanno?
This is tech startup brain rotting on display. People aren’t allowed to just make things anymore.
for a standalone project that's fine, but when the project's entire purpose is to track and be an adversary to another project...
the problem is that to someone who can't maintain (realistically, get an LLM to do it without running into refusals) this project on their own, any time they spend utilizing it will end up a waste of time.
Even if it just ends up being a base to throw and llm at to update, isn't that still useful? Sounds to me like it'll probably skip the whole part where my agent would have to give me 4 different plans, searches the internet, argues that it's impossible, works out subtools to generate, etc.
For the last few builds released by Cloudflare, I basically just told an agent “Hi they changed something. Please fix.” And waited for a few hours (mostly spent in Rust compilation) until it came back fixed. Keeping the codebase clean while doing that long term is honestly the harder part.
Yes, that was my goal. I will update this for the next couple of weeks, but probably not forever. However I think this is a pretty good foundation for future efforts.
And the inevitable switch to GLM :)
Or it's just an experiment to share, I get what you're saying but not everything needs to be feature complete to share.
I actually vastly prefer people show me their broken demos. Let's me understand how difficult the problem is than I think initially.