|
|
|
|
|
by josephg
359 days ago
|
|
> The problem is that there's no way for the server to compress any of the updates; if a peer is offline for an extended period of time, they might need to download a ton of data. There are ways to solve this, using deterministic message chunking. Essentially clients compress and encrypt “chunks” of messages. You can use metadata tags to tell the server which chunks are being superseded. This is fast and efficient. Alex Good gave a talk about how he’s implementing this in automerge at the local first conference a few weeks ago: https://www.youtube.com/watch?v=neRuBAPAsE0 |
|