zlacker

>>levmis+(OP)
Beautiful. Is it E2E encrypted?

>>dwa359+9l4
Does it matter? They'll surely wouldn't implement a local/client-first E2E encryption, so in the end they'll be holding the keys anyways.

If you want something private, don't put it on other people's platforms, it's very simple.

>>embedd+Er4
> Does it matter? They'll surely wouldn't implement a local/client-first E2E encryption, so in the end they'll be holding the keys anyways

Yes it matters, there are use cases if not only for privacy focus people. Why would the hold the keys? I actually have found a good example of one that I am working to verify.

>>bileka+SL4
Because currently they have search and they do user-to-user messaging, good luck implementing that over the web in a reliable and scalable way with E2E encryption.

>>embedd+m15
I'm not sure you understand the e2e encryption, the search can be ran on client side after decryption, there's no need to run it on the server side.

The chat is a bit more transient but you're transferring messages encrypted again over websocket for example, then decrypted on client.

I'm not seeing what the blocker is, or even issues with scale given its the client side doing the work.

Working example : http://securinote.com/#/notebook/bf528a8d-bf34-4f49-8cb9-e63...

key : embedding

Open up a second tab, make a change, check the network you'll see its sent over the wire encrpted via websocket.