85 comments

[ 3.0 ms ] story [ 90.2 ms ] thread
There must be some really good protection on this. If I enabled such a thing on any of my servers it would be full of warez, porn, malware, CSAM and who knows what else within minutes. Curious how they manage to keep it clean.
Makes sense. It plays nicely with the vibe code kids who don’t know how to do GitHub or don’t know to ask their LLM about it.
From FTP to CI/CD to drag and drop, society is going backwards
It is cool to see not sure why you would use it.

Also it seems to me that this is a good way to exfiltrate data, rubber stamped by cloudflare themselves.

Tried uploading a ZIP and got:

"Something went wrong An unexpected error occurred. Please try again or contact support."

Wait, my first impression was that it points a local browser to your local browser. Now it looks like it uploads your folder to Cloudflare and temporarily serves it over the web. But is that different from what we used to do with FTP? Are there any databases or anything like basic PHP hosts supply? It's just static sites?

Is this a product or what? What's the purpose? Is there an API?

Netlify made this 10 years ago... they even copied the name! https://app.netlify.com/drop
Isn't this what we used to do with Geocities a quarter century ago? And with most other websites that offered FTP upload? You didn't have to be very technical -- there were windows FTP clients where you could just type in the IP, username, password and see an explorer-like view, onto which you could just drag and drop your HTML and image files.
>Something went wrong An unexpected error occurred. Please try again or contact support.

I have a few qualms with this app.

Congratulations on launching!

I tried uploading a git repository that I have previously successfully published on Github pages. This is a "no build" website I have built with the help of Claude. It should just work but I keep getting an error. Who can I reach out to give them steps to reproduce? The website repository is public and I feel like anyone at Cloudflare who wants to reproduce my problem can quite literally clone my repo and upload it to cloudflare drop.

Please drop your cloudflare email address and I will reach out to you with my repository information.

Hah! This is exactly how I’m serving the vestigial remnant of my blogging in the early 2000s from a ZIP-backed Cloudflare Worker today. Should I rebuild my site with Drop+Claim or is it fine as-is? I kind of feel like ‘if what I have works, don’t change it’ is the best path.
Cloudflare is really good at launching features that facility low-friction deployment of malicious content (such as phishing) on the Internet, piggybacking on their hosting reputation and the fact that you can't easily block their ASN or domains.
It would be nice if we could see some information such as file size limitations, demos, link structure, management, etc. Am I expected to upload a random HTML file and see how it works?
I remember doing this in 2006. FTP. Good times.
Cloudflare has the astonishing ability to make me hate them more as a company every new feature they launch.
Cloudflare folks: Please consider supporting WARC archives for deployment.
Wow the people in this thread are a huge bummer. This is much cooler and I doubt this is a real safety issue. You can already sign up for a free cloudflare account and deploy it for free, on your own, on a free workers.dev domain. The friction removal here isn't going to meaningfully change the security / amount of malicious content.
Oh poor you, bummed by people WHO ACTUALLY care about the web.
After my hoster started asking me for 700€ for a year of hosting a static website of like 100Mb i moved to CF worker and github. I would selfhost but thats not allowed without license
Yet I can't drag and drop a plain old HTML file without putting it in a folder or a ZIP file first.
The internet will soon be flooded with even more scam landing pages.
Dropped a folder with a small HTML project, and after 20 seconds got "Something went wrong. An unexpected error occurred. Please try again or contact support.".

Note how the error has zero information.

Looking in the network tab, a POST request to /upload returned 403 and an HTML page starting with "Sorry, you have been blocked", and to "email the site owner to let them know you were blocked".

I'm very tired of this adversarial approach to software coupled with vague errors.

EDIT: it was the file './git/hooks/fsmonitor-watchman.sample' created by default on git init. Maybe because it's Perl. Worse-than-useless "please try again" and "you've been blocked" for committing the sin of uploading a folder that's a git repository. Sigh...

(comment deleted)
Reminds me of web development in the 1990s.

I honestly miss those days of deployment simplicity.