was not super impressed by it in 1.x.
but also i have to keep a recommendation on hand for normies/corpos. currently that recommendation is XWiki, but that is very hefty (~2gb RAM). very normie and corpo compatible though.
my non-normie recommendations are pmwiki or dokuwiki. which tend to be ugly but incredibly cheap to run.
@icedquinn The best "non-normie" wiki is probably aciidoc or tex2page fed from a git repo.
made me think for a few minutes about how piss poor the sync situation is on computers these days.
@icedquinn @fluffy I mean if you just want to sync stuff there's syncthing, that works extremely well.
@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.
@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.
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.
@icedquinn @fluffy TIL, that's a neat idea!
Most of my stuff that isn't text files doesn't change much though.
