You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using @localfirst/relay, it would be great to have the ability to use a storage peer that stores arbitrary automerge documents, given some documentId
The text was updated successfully, but these errors were encountered:
okdistribute
changed the title
Mailbox: Sending while offline with a journaled relay
Mailbox: Sending while peer is offline with a storage peer
May 17, 2021
for your purposes, I think the short-term options are:
encrypt individual field values before putting them in the automerge doc (this works as long as it's ok for the keys and structure of the document to be unencrypted, and only the field values to be encrypted); or
nest an encrypted automerge doc inside an unencrypted one. the inner document contains your regular unencrypted data; then you take the changes to the inner document, encrypt and base64-encode them, and then add those encrypted strings to a list of strings in the outer document. the outer document can then sync as usual. to decrypt the document, take all the strings in the outer doc, base64-decode and decrypt, and then apply the resulting changes to an empty doc
We are using @localfirst/relay, it would be great to have the ability to use a storage peer that stores arbitrary automerge documents, given some documentId
The text was updated successfully, but these errors were encountered: