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.

[1] https://developers.cloudflare.com/workers/platform/claim-dep...

Wouldn't it make more sense to merge the temporary account into an existing one, instead of claiming it as a new account?

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.

If eastdakota/jgc are here:

- simply expose containers to teh world directly - withotu having to go via workers.

- You have other amazing parts of the stack anyway (D1, durable objects, a great object store).

Not having a simple container based compute piece has made me heitate in taking up CF. (Fly or firebase won out)

posted yesterday as well: https://news.ycombinator.com/item?id=48598906

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!

I’m going to need a wrapper for all these services offering this service.

[dead]