zlacker

Nice! I worked on something that seems similar to this (https://redact.ws). Unfortunately there are a lot of challenges with adoption that seem difficult to overcome. One of the big challenges is that most people do not understand the nuances of privacy and encryption, and they aren't willing to jump through hoops to protect their data.

>>cracke+(OP)
This is fascinating, I was thinking about doing something in a similar space. Does past tense "worked" mean you're not still working on it?

>>pcthro+W5
Not actively. It's open source so feel free to poke around our code and docs, and you can find a contact form on the site as well if you want to chat.

>>cracke+(OP)
I like the intent of this! My main question is, how do we know redact.ws won't suddenly serve different Javascript one day, to certain clients, which send unencrypted payloads somewhere?

>>EGreg+DI
The redact server is an open source application that runs locally on the client.

>>cracke+oJ
How does a server run on the client? It runs on localhost! Right?

It can show the user their own info back to them in iframes?

>>EGreg+V81
I'm not the creator of redact, but it sounds like you're under the impression that the iframe src is redact.ws in which case I'd understand your concern.

My assumption is that the iframe src would be the local redact server, which would keep things as secure as the package the user installed (though there could be compromises at the network level I suppose)

>>pcthro+kf1
Exactly. This section on the website should explain it with some more detail: https://redact.ws/how-it-works#client