Cloudflare: let's give the bots their own accounts so they can scrape harder.<p>Also Cloudflare: let's send normal humans who are trying to go about their daily lives into endless Turnstile spinner loops with absolutely zero recourse, grievance, or support infrastructure.
First you spread the disease, then you sell the cure.
I had similar thoughts: "let's convince everyone to outsource the decision on who can access their websites to us, because BOTS BOTS BOTS" and "let's make life easier for bots to do things".
It's a clean way to charge AI to read content too.
But think of the shareholders
Hot damn...<p>> Any agent can now run wrangler deploy --temporary and deploy a Worker to Cloudflare. This temporary deployment stays live for 60 minutes, during which time you can claim the temporary account, making it permanently your own. If you don't, it expires on its own.<p>Forget about agents, Cloudflare just provided free scratch deployments - ephemeral for 60 minutes - for <i>anyone</i>.<p>This is going to be amazing for things like PR previews and code review. Being able to deploy a preview to a <i>working URL</i> for free is a huge reduction in friction.<p>I hope it doesn't get abused so much that they turn it off again.
I just tried this out:<p><pre><code> % npx wrangler deploy --temporary
wrangler 4.103.0
────────────────────
You must accept Cloudflare's Terms of Service (https://www.cloudflare.com/terms/) and Privacy Policy (https://www.cloudflare.com/privacypolicy/) in order to continue. By typing "yes", you agree to these terms. Type "yes" to continue. … yes
Solving proof-of-work challenge…
Temporary account ready:
Account: Educated Celery (created)
Claim within: 60 minutes
Claim URL: https://dash.cloudflare.com/claim-preview?claimToken=CAVe7LzWiGad-redacted
Total Upload: 13.79 KiB / gzip: 4.12 KiB
Uploaded cloudflare-redirect-resolver (2.27 sec)
Deployed cloudflare-redirect-resolver triggers (0.50 sec)
https://cloudflare-redirect-resolver.educated-celery.workers.dev
Current Version ID: 5c12da7f-2749-4ccc-a8f6-79b85da98d10
</code></pre>
I'm amused that it made me accept the terms and conditions without any indication of who I am, but it did work - <a href="https://cloudflare-redirect-resolver.educated-celery.workers.dev" rel="nofollow">https://cloudflare-redirect-resolver.educated-celery.workers...</a> will be live for the next 59 minutes.
> I'm amused that it made me accept the terms and conditions without any indication of who I am<p>as far as i’m aware, that’s fully binding and often an accepted practise - take Minecraft’s server software, where you must accept the EULA with a text flag before running
You might want to claim the link or remove it
Wasn’t this case pretty much before?<p>The limits are 100 workers on free and 500 on paid.<p>And if need more then you can always go their platform which supports tenancy.<p>As long as you have a cronjob or similar to clean up the cost of having per PR preview is pretty much zero.
[flagged]
Lets keep in mind this is cloudflare workers runtime - it only makes sense to deploy small things there, maybe static sites. Unless the agent creates something for cf workers from scratch, asking it to „now deploy to cloudflare” will fail so bad.<p>This would only work if they would provision docker image deployment, similar to google cloud run, but the still, everything serveless has its own caveats…
> Make snail-game in Cloudflare Worker in TypeScript and deploy it using wrangler, don't ask me questions, do the best you can<p><a href="https://snail-game.solstice-barometer.workers.dev/" rel="nofollow">https://snail-game.solstice-barometer.workers.dev/</a><p>pretty cool.
If eastdakota/jgc are here.<p>- simply expose containers to the world directly - without having to go via workers.<p>- You have other amazing parts of the stack anyway (D1, durable objects, a great object store). These aren't considered "lockin".<p>- workers is "lockin" - not similar enough to lambda/cloud functions and so becomes CF specific.<p>Not having a simple container based compute piece has made me hesitate in taking up CF. (Fly or firebase won out)
I am here but I retired from being CTO of Cloudflare in March 2025 [1] and the current CTO is Dane Knecht (dknecht here). What advantage does decoupling Cloudflare Containers from Cloudflare Workers have?<p>[1] <a href="https://blog.cloudflare.com/three-chapters-at-cloudflare-programmer-to-cto-to-board-of-directors/" rel="nofollow">https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...</a>
>Not having a simple container based compute piece made me hesitate in taking up CF<p>Agreed. I wish CF had something like Azure's new fast-starting Express containers.
[dead]
Would love to know more about how Cloudflare plans to prevent abuse of ephemeral infrastructure to host malicious content. From elsewhere in their documentation, “Cloudflare limits how quickly you can create temporary preview accounts. If the Wrangler CLI cannot create an account because too many temporary preview accounts were requested too quickly, wait before retrying or authenticate the CLI with a permanent Cloudflare account,” and “Cloudflare applies additional abuse prevention checks to temporary preview accounts.”[1] This is a bit vague though. Creating a new account has never been a huge hurdle to overcome but this seems to reduce the barrier to entry even more.<p>[1] <a href="https://developers.cloudflare.com/workers/platform/claim-deployments/" rel="nofollow">https://developers.cloudflare.com/workers/platform/claim-dep...</a>
Wouldn't it make more sense to merge the temporary account into an existing one, instead of claiming it as a new account?<p>This could lead to people having a large amount of separate accounts.
Correct me if I'm wrong, but does Cloudflare still not have a "Create Account" button on the account listing page? I think you still have to sign up from scratch doing plus-code email tricks, then invite your original email address as an admin, juggling multiple accounts. They should consider fixing that first.
Cloudflare makes it really hard to spend money. I constantly have to talk to someone in sales to enable some feature after rounds of negotiating on price. I think they would have way more customers, spending much more money, if they just offered transparent pricing, and fully on-demand services.
If I want to onboard a client to Cloudflare, I have to ask them to create an account and then invite me, which is a lot of friction for non-technical people.<p>A “create account” button accessible to me would be so much better. Then, I create the account and invite the client to join as owner.
I know no one is writing copy anymore but i wish they tried to edit it a bit so it wasn’t so glaringly obvious. It just sours the product when it seems like so little effort was put into the message. And it’s not even hard - just change the prompt used!
posted yesterday as well: <a href="https://news.ycombinator.com/item?id=48598906">https://news.ycombinator.com/item?id=48598906</a>
I’m going to need a wrapper for all these services offering this service.
[flagged]
[dead]