4y5k, have some self-respect. you could have cooked on this for a little bit longer than: yesterday. there is one commit! this is ... quite possibly, but I'm unsure, the first "show hn" with a single commit, lol
you can do that with full git history, the first commit is "upload files" or something like that, which I assume is via the UI because that is def not dev speak
Posting works well for making outbound HTTP requests; the only part it doesn't handle by default is locally capturing and replaying webhooks.
While testing TradingView alerts, exchange execution callback handlers, or cryptocurrency payment webhooks for our trading software, we always find ourselves running `posting` (or `curl`) in one terminal window while having an additional tunneling/receiving script running in another one just to catch and retransmit the tricky JSON payloads.
I'm excited for CLI/TUI since 2016. It's just easier to use and automate. Other than a web browser, all the software I spend significant time in are CLI/TUIs. This includes most image editing.
Absolutely unwarranted gatekeeping and bashing in this thread for the most benign reason. I think it looks neat. The API client space definitely needs some new FOSS entries after postman, insomnia, bruno all followed the same free -> freemium bait and switch way too common in dev tooling. Paywalling features that are already or previously implemented is a gross move, and feels especially egregious in the tooling space because developers integrate them as part of their flow and to get a random (albeit important) cog in that flow rugpulled or kneecapped adds undue annoyance and burden in whatever random project you happen to be working on at the time.
Nice work OP, I love these TUI tooling, and we need more options in this space in particular. Hopefully, next time you'll use git from the beginning (for your own organizational sake) but I'm honestly baffled people will disregard a whole FOSS project because of how you chose to make it public. Do better HN populace.
Feels odd to me to put TUI in the about section first, and then a few words later use no electron as a selling point - if I’m using a TUI I’m not expecting electron!
I don't see it the same way. People are building these things for themselves because it solves a specific problem they have, and that means it's crafted just to their liking. And it will only become easier to maintain these because of LLMs constantly advancing (for now). So if this is also a match for what you want out of a tool, then you can easily adopt it, or even fork it to your own liking. If it's not a fit for you, that's fine, there are plenty other options that may be.
I've seen several projects like this, where there is a flurry of activity for a few days, maybe a couple of weeks, and then it is abondoned and doesn't see any more updates. Maybe they got bored of it, maybe the code wasn't actually maintanable (which can easily happen with vibed code), maybe they were just trying to get attention and didn't actually care about the project.
Sure, but projects need to start somewhere. You can't go from one user to hundreds+ without first having two users. This is how they're deciding to share it the first time, and that's fine. Use it if you like, don't if you don't. Simple. If they stop maintaining it, then since it's open source and MIT license, you can do what you want with it to fix the issues you have.
example: https://news.ycombinator.com/item?id=47492202
I recall sub-10m, but don't care to search has any harder
https://github.com/darrenburns/posting
Exists, its from on of the co-devs of textual the framework this uses anyway..and more mature I would wager to say.
While testing TradingView alerts, exchange execution callback handlers, or cryptocurrency payment webhooks for our trading software, we always find ourselves running `posting` (or `curl`) in one terminal window while having an additional tunneling/receiving script running in another one just to catch and retransmit the tricky JSON payloads.
Would love to see OpenAPI support at least for import
Nice work OP, I love these TUI tooling, and we need more options in this space in particular. Hopefully, next time you'll use git from the beginning (for your own organizational sake) but I'm honestly baffled people will disregard a whole FOSS project because of how you chose to make it public. Do better HN populace.
> No cloud accounts. No 1GB Electron bloat. 100% Local-first.
This would make me want to use Postman (Electron) over this, since I know that this will absolutely be unmaintained in the a few years.