Hacker News new | ask | show | jobs
by lucideer 1599 days ago
I used to like Postman until it locked me out of my locally-stored data while I was offline (testing my own applications on localhost) for an extended period , I found out that it phones home constantly (cannot be disabled) & locks you out if it fails. The developers stating they had no intention of changing this for "security reasons" before closing the Github issue sealed the deal.
1 comments

This sounds unbelievable but it seems to be true? https://github.com/postmanlabs/postman-app-support/issues/10...
I don’t see anything in this issue that I’d characterize as

> The developers stating they had no intention of changing this for "security reasons" before closing the Github issue sealed the deal.

The issue is still open with no response from the developers that mentions security reasons.

There have been many tickets opened (and closed) on this problem. Searching their issues for the keyword "offline" should bring up some of them. This one is just the latest.
Its in issue in the sibling comment. The suggested work-around is to not sign in at all.
For further context: I'm not sure if this has changed but at that time signing in seemed* to be required (there's some discussions in the ticket about confusion in the UI about this so in retrospect UX dark patterns were likely at play). However, while it may have been possible to make ad hoc requests without an account, it didn't seem to be possible to save request collections locally without sign in.
That is incorrect. You can save requests inside Collections in the Scratchpad and send requests without an account.
Not sure what I said that's incorrect?

The original issues were from 2015 & 2017 - Scratchpad was only added to docs in Jun 2021 (before that was an undocumented feature for likely under 2 years I would guess).

Also, on the suitability of Scratchpad as a workaround for this bug, as quoted from person who created the linked issue:

> and no, scratchpad is not a solution to this.

The same sentiment is echoed through many of the more recent closed issues created in Github on this topic.

Either way: my comment above was mainly about dark patterns, which makes the existence of a workaround (not matter how suitable) somewhat moot. Even if this issue gets fixed "properly", the attitude of their devs over this long a period of time has been more than enough to turn me off using their software.