71–80 of 171 posts
So we are once again in the - please give alternatives. No clouds, no syncs, no other bullsit ... Postman is dead, insomnia seemed like good alternative.
So we are once again in the - please give alternatives. No clouds, no syncs, no other bullsit ... Postman is dead, insomnia seemed like good alternative.
Self-hosted and open source.
So we are once again in the - please give alternatives. No clouds, no syncs, no other bullsit ... Postman is dead, insomnia seemed like good alternative.
* good old tools - curl, Emacs plugins (restclient.el is pretty nice), Vim plugins;
* and Postman/Insomnia alternatives - restfox.dev, hoppscotch.io and httpie.io (my personal preference so far) and I found this group to be the most volatile (I personally has moved from Postman to Insomnia).
Seems it has (accidentally) at least happen once before (https://github.com/Kong/insomnia/issues/5559) so probably worth switching to a different client regardless if this time was on purpose or not.
Had to migrate away from Thunder client once they announced their pricing and stopping freemium.
I have moved to bruno and its pretty refreshing to use a simple tool without the cloud bloat
open-source a tool
build userbase
VC funding
rugpull
repeat
open-source a tool
build userbase
VC funding
rugpull
repeat
- Work for some time
- Do the same shit as Postman
- ...
- Profit? Really?
I don’t know even. Why does it have to be the same story all the time? It’s become so tiring.
Earlier quoted context omitted.
Probably not a question you like to hear - but right now if I decide to jump from offline postman or insomnia - which will be the biggest pain points that I am to expect? Edit: And good luck, I have looked quite a bit for project like that.
Oauth2 flow is missing (which should be released by tomorrow), Otherwise you shouldn't encounter any pain points. The app has been in development over 2 years, and community (early adopters) has been using it for over year. It's fairly stable except the occasional blip. I built the tool for myself, I wanted my collections to co-exist alongside my backend code and be able to version it via git. So I ended up creating…
- Is there a way to handle secrets outside of this flow? - Can we set/reference variables between collections? collection A sets a variable, collection B uses it.
also, a small bit of feedback from someone that briefly played with Bruno this morning.
- moving requests in a collection via drag/drop isn't obvious and it's actually a pain if you're trying to replace the top item. - if I duplicate a request I want the new request highlighted and I would personally prefer if the same tab was opened