3 ms·

security is a big reason to go local first in general (not necessarily with crdts but they are a strong option), less data over the wire to central servers, you

security is a big reason to go local first in general (not necessarily with crdts but they are a strong option), less data over the wire to central servers, you can avoid even needing to know about user data if it stays on their device(s) collaboration software benefits a lot from this approach because people can just use it and know it won’t get out of sync Also, anything where you might need data offline at a specific moment. Like if the internet goes down but you still need the thing to show to the guy at the place, you’ll be glad if they used crdts because you’ll automatically have a copy Also, cheapskates who don’t want to pay cloud bills

WolfOliver 2y ago
> and know it won’t get out of sync but will you ever be able to trust the automatic merge? Imagine a complex document with a few collaborators which work in parallel offline and make significant changes (that is the use case of automerge?). You will have to proofread the entire document after every non trivial automatic merge, or how good does this work in practice? Would it be easier to just wait for a wifi connection and do the changes in real time?
- WolfOliver 2y ago
  now you can compare it to pull requests in software development, but in software development we have compilers, linters and tests which point out merge bugs.
WolfOliver 2y ago
> Also, cheapskates who don’t want to pay cloud bills You will have to store it in the cloud eventually, otherwise it is just local software, not local-first
- nanomonkey 2y ago
  Not quite true, you can utilize peer to peer (p2p) storage options, where only the individuals that are allowed to edit and view the document/media/file do storage. Really you only need one peer that has an IP address to do NAT traversals, that peer need not do any storage, but just passes transactions along to the end users. With IPV6 and Torr onion routing NAT traversals is almost becoming a non issue.

WolfOliver 2y ago

> and know it won’t get out of sync but will you ever be able to trust the automatic merge? Imagine a complex document with a few collaborators which work in parallel offline and make significant changes (that is the use case of automerge?). You will have to proofread the entire document after every non trivial automatic merge, or how good does this work in practice? Would it be easier to just wait for a wifi connection and do the changes in real time?

WolfOliver 2y ago
now you can compare it to pull requests in software development, but in software development we have compilers, linters and tests which point out merge bugs.

WolfOliver 2y ago

> Also, cheapskates who don’t want to pay cloud bills You will have to store it in the cloud eventually, otherwise it is just local software, not local-first

nanomonkey 2y ago
Not quite true, you can utilize peer to peer (p2p) storage options, where only the individuals that are allowed to edit and view the document/media/file do storage. Really you only need one peer that has an IP address to do NAT traversals, that peer need not do any storage, but just passes transactions along to the end users. With IPV6 and Torr onion routing NAT traversals is almost becoming a non issue.