RU version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
61% Positive
Analyzed from 1520 words in the discussion.
Trending Topics
#cloudflare#file#drop#html#https#something#web#please#don#feature

Discussion (68 Comments)Read Original on HackerNews
But that won't stop people doing bad stuff for an hour I guess. Vibe code up some on-demand thing that you ping...
I honestly miss those days of deployment simplicity.
https://drop-e7e6d363-601.important-seat.workers.dev
Also it seems to me that this is a good way to exfiltrate data, rubber stamped by cloudflare themselves.
Is this a product or what? What's the purpose? Is there an API?
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.
Here's the instructions my agents have:
> Shareable Deliverables → jlnk.us (default) The jlnk MCP server is configured machine-wide for all team agents. It publishes disposable public links: create_link(content, ttl) returns an unguessable URL anyone can open without logging in; it self-destructs after its TTL (4h/24h/72h, default 4h, max 5 MB). Also list_my_links() and delete_link(id).
> When handing a human (Founder, CEO reviewer) something to look at — QC screenshots, prototypes, reports, before/after comparisons — default to a jlnk.us link instead of a repo file path or local path. Use 72h for Founder review, shorter when the review window is same-day.
> Content must be ONE self-contained HTML file: inline CSS/JS, embed screenshots as base64 data URIs ().
> Downscale images to stay under the 5 MB cap.
> Links are public to anyone holding the URL. NEVER publish secrets, API keys, credentials, or private client data.
> Links expire — they are a viewing convenience, not the system of record. Durable artifacts still go to the repo and issue attachments as usual.
However, I see the appeal of this. Kind of surprised it hasn't happened yet to be honest.
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.
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...
I have a few qualms with this app.
"Something went wrong An unexpected error occurred. Please try again or contact support."
"Please upload a screenshot of the error by dragging a zip of the png file."
(https://x.com/BraydenWilmoth/status/2074894829616509358)
Desktop mode doesn't show any more information either
And then sell its denizens malice protection services.