@fluffy @icedquinn oh wow really? That's a shame. I used it for years with zero problems across over half a dozen different machines with different architectures. All of them ran Linux though. It still runs on two of my machines but I'm holding off on adding it to my newest one because I don't like the memory consumption, I just haven't found a replacement.

@swiley @icedquinn i suppose i was using it to sync between two people. i think for your use case i would just use rsync

@fluffy @icedquinn rsync doesn't go both ways. for stuff it does work well with git is better anyway.

@swiley @fluffy synkron does go two ways. and of course git. bit if your app stores stuff in sqlite, RIP.

@swiley @fluffy if i listen to an hour of one audiobook here, and twenty minutes on another machine, just shoving the config file will obliterate (not merge) these points.

it needs to either store each record in its own file (which is fine, though noisy) or use CRDTs. for instance in GunDB you just store a timestamp of the last change to a record, and latest write wins.

@icedquinn @fluffy I don't think syncthing looks at the contents, I'm pretty sure it just does newest version wins and maybe writes the old version under a different name. That's why I can't just replace it with git, I have 8Gb of random binary files (PDFs, pictures, mod, xm, elf binaries etc) and don't want to keep that in git.

@swiley @fluffy git-lfs would be nice if there was just a microservice for it and not having to install gitea or some shit

@icedquinn @fluffy Yeah, really ipfs would be perfect if there was an easy way to communicate newer roots for the tree and automatically pin them.

@swiley @fluffy i wish ipfs used rabin fingerprints instead of naive chunking.

@swiley @fluffy rabin and rsync chunking are the magic that makes it so if only part of a file changes, or if two files have commonality, then those common chunks are stored only once. aka. deduplicated backups.

for example i am an old blender person so revisions consist of a folder of sequentially numbered .blend files, representing marker points in the project history, but those are all basically the previous file with some new stuff changed, and they can add up to 20mb per file or more.

as long as you don't compress them they can deduplicate well.

ipfs doesn't exploit this.

@fluffy @swiley i have a draft in my head of a version control system for artists which is just based around this concept. it hasn't been a priority to make though.

@icedquinn @fluffy TIL, that's a neat idea!
Most of my stuff that isn't text files doesn't change much though.