raphael10-collab

I removed node_modules/ yarn-error.log yarn.lock (there was no package-lock.json) and then installed dependencies again, and executed electron-rebuild. ( https://www.electronjs.org/docs/tutorial/using-native-node-modules ) . But the problem persists: (base) raphy@pc:~/Raphy-Template$ rm -rf node_modules/...

Hi Peter! Thank you for your kind reply. If someone I collaborate with is able to see who are the other people I've shared documents with, it cannot be a...

Your kind and with heart description of the current situation is really appreciable. Actually my objective is to incrementally build a collaborative system suitable for holding legally sensitive information. If...

At this stage, I have more questions, than answers. in the OmniboxWorkspaceListMenu.tsx's offerDocumentToIdentity function I mixed your proposed solution with my comments and questions, and tried to sketch a beginning...

The sodium's sealed boxes seem to be the the right tool, because they encrypt a message in a sealed box using a throw-away keypair, that is overwritten during encryption, hiding...

Thank you Matt for this in-depth examination of my very first attempt to encode some sort of privacy around the receiver-sender "channel". It seems to me that the sealedBox tool,...

@pvh @mjtognetti Did I say something wrong or unfeasible?

@mjtognetti I created an object containing the recipientUrl and the recipient public key: const recipientObj = {rUrl: recipientUrl, recipientPKey: recipientPublicKey} const recipientObjStringified = JSON.stringify(recipientObj) Based on the signatures of `box`...

Thank you @mjtognetti for re-bringing me on track. I'm almost done, apart from a last bit, for which I'm circling around... : OmniboxWorkspaceListMenu.tsx const recipientObj = {rUrl: recipientUrl, recipientPKey: recipientPublicKey,...

Thank you for your kind explanation It looks that the second option, A browser extension that interacts with the daemon to enable/disable the proxying/archiving functionality, might be simpler to use