Andres

@yestalgia I will say that the configuration is not the most intuitive. Part of it is just that the web UI is, imo, not that good. There’s a lot of confusing stuff exposed to users that isn’t really important for like 99% of use cases.

(who cares whether compression is metadata only or all data or none? wtf is “introducer” vs “auto-accept”? why do I need to see a random hash for device or folder id in addition to a device or folder name?)

@yestalgia So I set up syncthing between a server and one client. Share folders between them. Figure out how you want the folder data replicated; for my phone pics, for example, the sync is one way from (phone) -> (syncthing server). For kids’ health stuff, it’s a two-way sync; because the sync might be (my laptop) <- (syncthing server) <- (my wife’s laptop), or vice-versa. Then add another client to the syncthing server, following the same process. Never sync client-to-client; always via server

@pixeldaemon I used to use Seafile, but it is clunky and annoying, and it will also never ever be in debian due to upstream copyright sketchiness.

@pixeldaemon Syncthing. We have one “authoritative” fileserver running syncthing, and then a bunch of “clients” (laptops, phones) that sync up to the fileserver. This doesn’t work for, say, terabytes of movies/music, but for important stuff like photos/tax records/whatever, it means we can make changes on any “client” and it gets synced to the “server” and all the other “clients”

For more traditional cloud, I recently installed copyparty (https://github.com/9001/copyparty) w/ https://github.com/romaan7/white-gold-theme-for-copyparty

@Bazoogle @1hitsong First of all - when it comes to creating programs, you want the output to be deterministic. Stochastic program output is a serious problem, as you _will_ get unreproducible bugs. Second, plain language is _not_ easy except for the simplest of tasks. Actual programs need to handle all kinds of corner cases and hardware weirdness and human weirdness. Your “plain language” goes from “do a thing” very quickly to “do a thing. but not that thing. or that other thing. and and and…”

@GreenKnight23 I don’t see that behavior. Rebooting into a new kernel and then running dist-upgrade, it always _always_ keeps one older kernel around. Bookworm and trixie.

@GreenKnight23 @oong3Eepa1ae1tahJozoosuu I’ve never seen that behavior in Debian. Is that some different type of configuration?

@djdarren @frongt That’s not how SyncThing is designed. It’s intended to be a full mirror.

I kind of emulate what you’re talking about with restic’s mount command. It’s a lot less intuitive than what you’d get from a cloud storage platform, but it’s Good Enough For Me. If you want to match cloud storage, you probably want nextcloud or seafile or something.

@IratePirate @eightys3v3n Snapraid offers scrub/bitrot protection - check out ‘snapraid scrub’.

@IratePirate Combine this with restic (or borgbackup, if that’s how you swing) for a bombproof selfhosting solution.

@PancakesCantKillMe @gedaliyah Okay, you’ve piqued my curiosity. What does your playlist for pets look like?