Hacker News Reader

Comment by dietr1ch | Hacker News Reader

I moved to Syncthing when they asked me to move to ext4.

I'm glad I did. Now my phone and tablet are first class citizens when syncing and I can have multiple roots shared between different devices. I wish I switched earlier.

View on HN

Syncthing is only for the sync component of Dropbox. If you have an always on node for syncthing and miss the web UI component of Dropbox along with the shared links and full text search, I've built Filestash: https://github.com/mickael-kerjean/filestash

Hey, awesome, dude! Been looking for something just like this, and will definitely try it.

The only thing that bugs me about my Syncthing setup is that it's annoying to find a file in one of my sync'd folders from my phone (which is iOS, so no Syncthing client).

I don't do that much, but every once in a while you really want to — and in modern times, we mainly want to find files via searching for file content.

This looks great, and I will definitely try it tonight!

I'm trying to understand what this is. So it's not storing any data? It is a web app that is capable of displaying data/files on other servers via the many listed protocols?

Syncthing isn't on the list of supported file providers, am I missing something here?

syncthing assume a filesystem, filestash connect to that filesystem with a Dropbox like interface. In its simplest scenario you probably want to connect to your syncthing instance via SFTP as it comes builtin with every server with the SSH package (deeper integration is in the roadmap)

this is great! installing tonight

Syncthing is great and has become a core part of my workflow. It's just really annoying that there's no iOS client. So I have this great sync service that only works across my Android phone, laptop and desktop, while my iPhone and iPad are stuck outside the loop. Which means I have to duplicate some of my workflow onto another service.

I moved away from Dropbox years ago, after it pissed me off on Windows (basically, the Windows client was ludicrously inefficient, and there were constant sync conflicts).

I switched to Seafile, backed by Azure blob storage - so much better than Dropbox. The Windows client barely uses any CPU, sync conflicts only occur when I'd expect them to, and of course you can sync files regardless of whether they are in a fixed "Dropbox" folder.

I have Seafile and Minio running in containers, so it was super-easy to setup, and is a doddle to upgrade too.

Haven't looked back!

Syncthing doesn't do symlink following at all which is really god damn annoying and stupid.

It also doesn't preserve creation time, which is really inconvenient for us Windows folks. I think that's optional metadata in POSIX, so Go doesn't support it and the devs are reluctant to use platform-specific code to implement it.

I recently switched from Dropbox and wanted to clean up a folder of some old one-off scripts in groups of year-created. I had to pack them in 7z archives and sync those in order to have the scripts available in multiple machines as I wanted them.

It's disappointing when a piece of software is almost perfect, except from that one little thing you need and completely ruins your workflow.

I'd love to contribute to Syncthing, but I'm tired of learning new languages, frameworks and paradigms for such trivial (IMHO) changes. I never thought I'd be missing the elegance and simplicity of plain old C.

Isn’t upgrading to ext4 trivial?

I won't be painting my house green if they decide to require that later.

Also, is it really an upgrade?

It’s a one character change to fstab...

Reply on news.ycombinator.com