Curious - do you have any concerns around storing potentially sensitive information in local storage? My understanding is that any app can view what is in local storage.
Postwoman is a 100% client side application. PW just works even if you download the entire web page to system and opened from there, there's no client-server data transfer ever happening, except on Proxy mode, which is optional.
We uses localStorage for storing the History entries and the current state of request section. We stay compliant on Same origin policy throughout our implementation. Moreover, there's always an option to Clear/Disallow cookies.
When I first started working PW, I never wanted to have a Sign-up flow because it somehow seemed to decrease my testing flow. But as the project gained such traction & grew tremendously, having a Sign-in with GitHub/Google and storing data on a GitHub repo is pipelined for future with prime priority.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Curious - do you have any concerns around storing potentially sensitive information in local storage? My understanding is that any app can view what is in local storage.
Postwoman is a 100% client side application. PW just works even if you download the entire web page to system and opened from there, there's no client-server data transfer ever happening, except on Proxy mode, which is optional.
We uses
localStoragefor storing the History entries and the current state of request section. We stay compliant on Same origin policy throughout our implementation. Moreover, there's always an option to Clear/Disallow cookies.When I first started working PW, I never wanted to have a Sign-up flow because it somehow seemed to decrease my testing flow. But as the project gained such traction & grew tremendously, having a Sign-in with GitHub/Google and storing data on a GitHub repo is pipelined for future with prime priority.