-
i wish SyncThing was a library that could be embedded in anything, rather than an app
-
there's so much potential there. if your different devices could run different applications, all operating on the same folder of files, but also the folder is kept synced between them.
-
which is kind of possible now! if you just have Apple devices and you use iCloud, then that can work. or you use Dropbox. maybe. but all of these things are kind of fussy to set up, and have to be set up outside of the software that uses them.
-
and, of course, all of these things require that you put your data onto a large company's servers, and probably pay them some money to keep the data safe. maybe it's just because i'm rich & online, but i usually have a device online already. i don't really need the central server
-
the other limitation of Dropbox/iCloud, and Syncthing as is - is it only works if you actually have a folder of files to point to. what if you wanted to edit these files from a webapp? no technical reason you couldn't pull the files down, edit them, and sync them up.
-
why make a website that talks Syncthing rather than one that just has a backend service, like a normal website? sure, sure, own your data & all that. but more: because that way, the hosting costs become nominal @v21/1482332073553801217
-
sidenote: oh my god the thing web twitter does where it steals focus from the text input box to show you a popup about sending the previous tweet!! i hate it!!
-
anyway, the other, much more petty and fanboyish way of phrasing this is: stop writing your cool peer-to-peer web services in Go, and write them in Rust instead!