Live data from Hacker News

Postman which I thought worked locally on my computer, is down

status.postman.com

231–240 of 300 posts

Re: Postman which I thought worked locally on my computer, is down

#231
post #166

Question: Do I miss something by not using Postman? My alternatives for development are "Edit and Resend" of a request (in Firefox) and plain old curl scripts for reusable examples.

No, but you probably miss something for not using HTTPie

Re: Postman which I thought worked locally on my computer, is down

#232
post #36

This could have been a 10 Megabyte TUI app in your terminal tab. Boggles my mind how even this kind of app manages to bring in Electron and the cloud. Edit: Ah, so here it is: https://posting.sh

Because enteprise type devs love this shit

Re: Postman which I thought worked locally on my computer, is down

#233
Ah, yes, the cloud-dependent tool that forces you to pay per seat and log in for any type of collaboration is down when their cloud provider is.

Anyways, the folks have spoken, no need to double down. There are more than a dozen alternatives to it, and new ones are coming up.

I'm helping build a new one.

- Completely offline.

- Gives the ability to build reusable blocks (headers, query params, etc)

- Let's you document everything in Markdown.

- Imports your collections and cURLs.

https://voiden.md/

Re: Postman which I thought worked locally on my computer, is down

#234
post #125

Just use cURL. It will never disappear, enshittify, or let you down. It's already modern, and has a great UI. It's available everywhere. It supports every protocol and feature under the sun. Those fancy features you think you need: you don't. Whatever you're missing can be easily added via simple shell scripts or aliases.

> It will never disappear

They started hardening our images and curl went poof.

Re: Postman which I thought worked locally on my computer, is down

#235

Earlier quoted context omitted.

> could have been a 10 Megabyte TUI app Wow, in a world dominated by gigabytes of electron application, people thinks 10 MB is the optimal size for a simple utility TUI app. As a reference, (from archlinux repo), vim’s install package is 2.3MB, curl is 1.2MB, lua (the complete language interpreter) is 362KB

640K ought to be enough for anyone.

- Bill Gates.

And:

The world does not need more than 4 computers.

-Ken Olsen, or someone (in the mainframe days).

(Both are alleged / apocryphal quotes. :)

Re: Postman which I thought worked locally on my computer, is down

#237

Earlier quoted context omitted.

It is unmaintained. This is the cost of devs focusing on corporate gains and not their craft.

Why you and other devs say Insomnia is unmaintained? There has been a release in september, issues has been solved within last month, and multiple pull requests has been managed (merged and rejected) also recently. Maybe you refer to issues specific to a platform? Thanks in advance.

Insomnium

Re: Postman which I thought worked locally on my computer, is down

#238

Earlier quoted context omitted.

In case you aren’t familiar (and with apologies for my verbosity if you are): VSCode Remote can be best understood as a sort of hybrid of a local text editor and a remote web-based or X11 view of an editor for a remote session. When you use a remote, the code is on the remote and all your editing functions (search, version control, terminal, extensions) happen in the remote via a worker process. So in a remote sessio…

Wrote this late at night and didn’t explain what I meant by X11 view. I was thinking back to running X sessions on remote machines, sending for example a text editor view back across the network to my desktop. VSCode remote feels to my fiftysomething brain to be logically quite like that, only you are sending the display back from the remote worker using web techniques, and rather than to a display manager, you are s…

Maybe I’m misunderstanding, but I think what you want already exists as VSCodes remote SSH tunnel port forwarding (not the one that makes it publicly accessible).

Startup a dev server on the remote machine and forward the port to localhost. It should now be accessible via http://localhost:[port] on your local machine in the browser or any application, as if it’s running locally.

I find it’s very useful for also for interacting with DBs/Redis. Just forward the port your DB communicates on and use whatever client on your local machine to interact with it.

As far as I know this works with any service that communicates via TCP

Re: Postman which I thought worked locally on my computer, is down

#239
I highly recommend checking out the postman forum for posts about the scratchpad being removed, it's a fascinating and frustrating read.

It would be so much faster and easier for the postman reps to just shut down the conversation. And yet, for some reason, they keep it going for very long while still being extremely evasive when it comes to any concern raised about data sovereignty.

Re: Postman which I thought worked locally on my computer, is down

#240
post #76

Earlier quoted context omitted.

Don’t encourage snap.

Why not? Personal feelings aside, snap is working fine. It's maybe a bit slow on startup, but that's it.

Every single time I’ve installed anything with snap I’ve regretted it. It causes all sorts of annoying issues, including e.g. preventing integration between apps because of its supposed security model. This is typical of consumer operating systems, like Windows, but not what should be encouraged on Linux.

On top of that, Canonical is pushing snap very hard. Try to uninstall the Firefox snap - e.g. because it doesn’t integrate well with password managers - and install it using apt from the Mozilla repo. Ubuntu will later just silently replace it back with the snap version.

I’m about to switch away from Ubuntu as a result of this.

Post reply on HN