darubramha

17 ms·

1.
by darubramha 1y ago
You can delete the curl request if created from a logged in account. Non-logged in curls are auto purged after 30 days.
2.
by darubramha 1y ago
The sandbox is a lightweight Alpine-based container, it runs as a non-root user for security, it has minimal dependencies installed (curl, bash, coreutils) The container has restricted outbound access—only HTTP/S requests are allowed.
3.
by darubramha 1y ago
Yes — executions are done server-side, inside a resource-limited, sandboxed Docker container. That’s why login is required: to prevent abuse, rate-limit usage. I have a feature working to allow users browser side execution, but as others ha
4.
by darubramha 1y ago
Hey, you can absolutely delete any curls created if done from a logged in user, for others it will get auto-purged in 30 days of non-usage.
5.
by darubramha 1y ago
You didn’t miss anything in the docs. Right now uncurl.dev only supports http/https (and technically ftp, though it’s untested). Protocols like dict://, smtp://, etc. aren’t parsed or handled correctly yet, which is
6.
by darubramha 1y ago
:) the curl command parser expects some flags of GET, POST, stupidly overlooked, will get it fixed!
7.
by darubramha 1y ago
Hey that is weird, can you file a bug report here with the curl you were trying? https://github.com/uncurl/uncurl-support
8.
by darubramha 1y ago
Haha love that you shared the curl with the uncurl.dev url! Yes, delete is unauthenticated as highlighted, will be working on a fix for this. And you can delete any API if it is created as a logged in user.
9.
by darubramha 1y ago
I have implemented auto-purge all curls that are created without login will get auto deleted after 30 days of non-usage. You can absolutely delete your curl if you have created as a logged in user.
10.
by darubramha 1y ago
Appreciate the kind words—and the comparison! uncurl.dev kind of grew out of that same spirit, but with the goal of making the output shareable and executable in a browser, especially for folks who might not have an IDE set up or are outsid
11.
by darubramha 1y ago
Fair. I appreciate the honesty — even if it's a bit brutal :) Security is a top priority for this project, and I'm actively working to tighten things up. This initial version was launched to validate the concept, and admittedly, t
12.
by darubramha 1y ago
Exactly — this was one of the core constraints I ran into early on. CORS was a blocker for client side requests, I have a separate branch where this is integrated, maybe will add it alongside server side execution to let the person creating
13.
by darubramha 1y ago
Totally with you on that—your use case is exactly what I had in mind when I built uncurl.dev. I kept finding myself sending curl requests in Slack or email, and it felt clunky—especially when non-devs or support teams needed to test somethi
14.
by darubramha 1y ago
Hey, thank you so much for catching this and calling it out , will take this up and fix it! Really appreciate you taking the time to look and let me know (even if it had to be in public). I have added a github repo for filing bugs ( https:&
15.
Show HN: Uncurl.dev – Convert curl commands to a shareable, executable UI(uncurl.dev)
115 points by darubramha 1y ago|59 comments
16.
by darubramha 2y ago
Looks awesome, and will help quick galleries to be created. I wanted to build something similar, but at that time photos did not expose APIs to get list of photos. What was your work around? Or have they opened up the APIs now?