I have a fairly unique architecture where i have actively tried to make it as "browser-based" as possible.

a year ago by xoron to c/experienced_devs

Creating webapps is easy enough, but in my app, im kinda going against the "best-practices".

For example, im using browser-based cryptography exclusively. while it can be easy advice to suggest to consider using a server to generate keys, i want to contrast it against a webapp that would be sandboxed within the browser.

I'd appriciate if you would be interested to share your thoughts on the approach. I'm aiming for this project to be the foundation towards the most frickin' secure messaging app in the universe. It might be too ambitious, but I'd like to set the bar high.

Lodra 1 point a year ago

If you want client side security and trust, then you may want to consider wasm.

save

path: 0 17193256, hotness: undefined, score: 1, children: 1

xoron 1 point a year ago

Thanks!

https://www.reddit.com/...

Tldr; I had that question before myself. It doesn't seem to introduce any improvement over WebCrypto API which itself should have gone through peer-review and auditing. ("Choose your browser wisely" could be considered the advice here.)

I'd like to still look into wasm for several other details of the project, but it seems the built-in browser cryptography functions are performant and generally pretty good if used correctly.

save

path: 0 17193256 17196387, hotness: undefined, score: 1, children: 0