Earlier quoted context omitted.
FTPing files to `~/public_html` was the best... Miss those days.
It still works...
Cloudflare Drop
91–100 of 306 posts
Re: Cloudflare Drop
#92Congratulations 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…
Re: Cloudflare Drop
#93Wow 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.
[flagged]
Re: Cloudflare Drop
#94Wait, 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?
A minute ago I had an HTML doc I wanted to share with a PM. It was a Claude prepared demo of a hypothetical feature. Lots of screenshots. I ended up just embedding them directly in the HTML as base64 and sending him a 15mb file, but hypothetically this would have been a nice solution instead.
Re: Cloudflare Drop
#95Netlify made this 10 years ago... they even copied the name! https://app.netlify.com/drop
Re: Cloudflare Drop
#96Hmm, that's fun and useful. Here is snake game for 60 minutes. https://drop-e7e6d363-601.important-seat.workers.dev
Tried from two hosts, different countries.
Re: Cloudflare Drop
#97Re: Cloudflare Drop
#98Re: Cloudflare Drop
#99Re: Cloudflare Drop
#100Earlier quoted context omitted.
They already allow hosting static websites so I think the same guardrails are implemented.
I've never used CF so I could be ignorant in this matter. I assumed perhaps incorrectly that people had to verify their email address and delegate their domain(s) to CF including setting the glue records in the TLD servers meaning there is possibly a financial trail somewhere probably in the DNS registrars and perhaps a mail provider , whereas this is just drag-and-drop with no money trail. I have no idea what guardr…
They assign a subdomain automatically for uploads, same as cloudflare workers.
I don't know what they do, but implementing guardrails for this is possible nowadays with AI, but maybe they use a "mechanical turk"