I agree with the general concern about the JS crypto, however that could easily be solved with a native front-end to the website, and a systematic compromise co

I agree with the general concern about the JS crypto, however that could easily be solved with a native front-end to the website, and a systematic compromise could easily be detected. My bigger concern is that, even assuming uncomprosied client side code, the server can still access the decrypted content when someone access it, becuase the nessasary password is still sent to the server in the url.