4 ms·
> Furthermore, the client-side javascript on private.sh encrypts any query done on private.sh so that only Gigablast can read it. Therefore, no single party has
by bigyellow 5y ago
> Furthermore, the client-side javascript on private.sh encrypts any query done on private.sh so that only Gigablast can read it. Therefore, no single party has access to both the IP address and the query. This is something that is truly unique and truly powerful, and, right now, only private.sh can supply this level of privacy.
Run proprietary Javascript for privacy - what a fallacious concept. Going to assume this service is a honeypot or run by incompetent staff - pass.
- gbmatt 5y agothe javascript is run by your browser, so you can fully audit it.
- bigyellow 5y agoIt's still served by the site and I doubt most are interested or capable in auditing software to perform routine online tasks.
- rasengan 5y agoThere's an extension as well [1]. This means that the code is not being served by the server in this use case. [1] https://private.sh/extension.html https://private.sh/extension.html
- eftychis 5y agoI am not sure there are good solutions besides going off browser. P.S. I was involved in user authorization, attestation and privacy flows for a particular product recently and the browser was always where shit hit the fan. The web features are just not made with simplicity and privacy in mind. Then again we had more complex constraints.
- mrtweetyhack 5y agoOnly Gigablast can read it means it is not private