← Back to context

Comment by dewey

6 months ago

What is the selling point over the very mature Syncthing? I’ve been using that for this use case for many years, with the additional benefit of also being able to sync it to my server, having a UI and being in all package managers already.

being fr, i never even knew about syncthing until now. it's (clearly) a lot better, but again, the reason I made this is because of my school's software whitelist. they only allow certain apps to run on my laptop, one of them being python due to out compsci class. since then, I've been using it to get around whitelists and make my own stuff. this allows me to sync up me and my friend's stuff (like projects, etc.) while we're in school and not have to worry about the whitelist :)

  • That’s perfectly valid. Maybe add it to the top of your readme explaining what problem it solves (need to sync files between machines and all you can use is python).

  • My initial thought was, man, your school is lame. But maybe it's genius? Creativity thrives in a constrained environment.

    • In high school they had a few information kiosk computers spread around the various buildings; two in the library, one in the main reception, one in the cafeteria, and one in the mostly unused hallway right outside the computer club room. They were locked down so you could only navigate some intranet pages using a rudimentary on-screen keyboard, with the rest of the hardware in a locked cabinet.

      Guess which one got digitally defaced a couple of times each semester. Guess which ones got left alone. Genius move by the IT guy. Every time it happened he would come talk to the club members about the difference between whitehat and blackhat hacking but other than that nobody ever got in trouble.

  • This kind of whitelisting does absolutely nothing. It's a straight up lolbin. Anyway, if python is allowed, then surely other languages can be added to whitelist. Ask them to whitelist go and use syncthing

Syncthing is the most confounding user-unfriendly software I have ever had the displeasure of using. It makes a process that should be pretty easy, pick some folders and share some keys remarkably painful and convoluted.

  • I have more mixed feelings about Syncthing than you.

    I personally think it’s a power user tool rather than an easy to use tool. The UI can feel intimidating but is actually pretty coherent once you understand how Syncthing works.

    I would compare it with Git in terms of ergonomics : a powerful tool with its own jargon that you must understand to be able to use it.

    Like git, Syncthing chose to expose its internals to the user rather than hiding it behind something magic. But like git, I don’t feel like there are unnecessary complexity. Once you understand it, it’s easy to make it work because it makes sense.

  • Syncthing is software where i think reading the manual is recommended. it is a fine manual and clears up a lot of the confusion. There's a lot of complexity "under the hood" and trying to just intuit it from the settings is... as you know... confusing.

  • to be fair, syncing is something that appears simple on the surface but which is a mess of complexity under the hood.

  • Oh no. What makes it so hard? I was happy with the syncthing and syncthingtray setup process.

  • resilio sync (formerly bittorrent sync) has a nicer UI and its probably easier to use. ive been using syncthing for 5+ years now though and can't think of the last time i had any issues with it. its probably just a bit more confusing if youre coming from something more polished and centralised like dropbox or those types

I especially like that Syncthing can do encrypted revision backups to untrusted servers. My workstation and laptop get synchronised. And in case I ever accidentally overwrite a file, there’s the past five revisions on an offsite server.

  • How does your setup for the backup look like? Won't you lose the data if the source of backup data gets lost together with the keys?

    • I printed out the keys. They’re only useful together with the offsite HDDs anyway, so someone would have to break into both houses to use them, which seems unlikely enough for me.

SyncThing's insistence that a web UI be how you do everything has caused me quite a few headaches. Especially when said UI regularly breaks accessibility tools.

(The team do tend to fix those accessibility problems pretty fast. But spending a couple days a month working around a tool is not my idea of fun.)

  • > SyncThing's insistence that a web UI be how you do everything

    It does have `syncthing cli ...` which -I think- lets you do everything but to call it obtuse would be an understatement.

99% less configuration and UI surfaces come to mind.

Syncthing is great, but it does include everything and the kitchen sink. That's often great, but not always.

  • Absolutely.

    Syncthing is great but I really wish for a syncthing-lite you could deploy and configure easily.

    The version we have today is really suffering from a lot of legacy.

    I remember they are working on a big v2 with a revamp of the API which is a mess but they had to give up on getting rid on that horrible XML config file because it was too much work.

    Be aware they also recently silently disabled the sync of symlinks on the android build, what can cause a lot of bad surprises.

    They did define some specs of their protocols [0] but i haven't seen a alternative implementation yet.

    - [0] https://docs.syncthing.net/specs/index.html