3 ms·
You don't stricly need a server 24/7, but you need the peers with changes to be connected at the same time, which is inconvenient (that's why a server 24/7 is u
by pizza234 7y ago
You don't stricly need a server 24/7, but you need the peers with changes to be connected at the same time, which is inconvenient (that's why a server 24/7 is ultimately needed).
If one applies changes on a machine, then switch to another, they must ensure to leave them on for a brief time to allow syncing, then turn off the previous one. If they don't do this, they'll (likely) get conflicts.
If one's requirement is not to entrust a 3rd party with one's own data, of course, cloud/proprietary solutions are excluded, but to expect open/local solution to be as convenient as the former, is just false.
- OJFord 7y agoIt completely depends on use case, you're only going to get conflicts if you modify the same files on different devices before they've had time to sync. If you're using it to collate photos from different sources for example, that's fine. If you're trying to collaborate on a document, yes, of course, it's the wrong tool.