Hacker News new | ask | show | jobs
by qaute 2724 days ago
IIRC, Syncthing is decentralized P2P and synchronizes standard tree(ish) filesystems (like most similar projects). Perkeep does away with the filesystem and instead uses a blob-based merkle-tree-like system with good properties for very long term archival (and as a side effect, can also use P2P and multiple encrypted cloud backups easily). So Syncthing can copy preexisting file structures and fits in usual workflows, but Perkeep has some data storage benefits. I don't know how their performance compares.
1 comments

When you say P2P, it's only in a technical sense of not having centralized servers, right? I don't want to interact with nodes I don't own, for my particular use case.
If your nodes have direct network access to each other, no.

But if two nodes that have added each other's keys cannot reach each other directly (e.g. are in separate private networks/behind firewalls/etc) but both can reach an external relay server, it may act as a dumb pipe bouncing encrypted traffic between them.

https://docs.syncthing.net/users/relaying.html

There is a public pool of such relay servers (https://relays.syncthing.net/), and by default syncthing will reach out and connect/announce its itself there so other nodes looking for it could contact it via a relay.

You can host your own relay server and configure your clients to use it exclusively: https://docs.syncthing.net/users/strelaysrv.html#client-conf... or if you only want syncing when your nodes are on the same local network you should be able to just not configure any relays at all.

That's correct. It only syncs between nodes you configure.