whatgotdone VS syncthing-android

I wrote a tool specifically for this, mostly inspired by the Snippets tool at Google. I've been publishing my weekly log in it every week for almost three years:

https://whatgotdone.com/michael/2021-12-03

The code is all open source if you're interested in playing around with it:

https://github.com/mtlynch/whatgotdone

I had the same objection to SQLite, and then I heard about Litestream, and it won me over.[0]

Litestream watches your SQLite database and then streams changes to a cloud storage provider (e.g., S3, Backblaze). You get the performance and simplicity of writing SQLite to the local filesystem, but it's syncing to the cloud. And the cool part is that you don't have to change any of your application code to do it - as far as your app is concerned, it's writing to a local SQLite file.

I wrote a little log uploading utility for my business that uses Litestream, and it's been fantastic.[1] It essentially carries around its data with it, so I can deploy my app to Heroku, blow away the instance and then launch it on fly.io, and it pops up with the exact same data.[2]

I'm currently in the process of rewriting an open-source AppEngine app to use SQLite + Litestream instead of Google Firestore.[2] It's such a relief to get away from all the complexity of GCP and Firestore and get back to simple SQLite.

[0] https://litestream.io/

[1] https://mtlynch.io/litestream/

[2] https://asciinema.org/a/I2HcYheYayeh7aHj23QSY9Vyf/embed?size...

[3] https://github.com/mtlynch/whatgotdone/pull/639

We use syncthing to share files between our machines. It avoids is having to use dropbox / OneDrive etc. You just choose a folder and it automatically syncs it in the background.

https://syncthing.net/

This very hn entries is bust contradicting your statement.

Also what about syncthing[1] (for recurrent/permanent sync) and croc[2] (for one time copies) ?

I have used both for a number of years already.

[1] https://syncthing.net/

[2] https://github.com/schollz/croc

I would use syncthing, which is open source at https://syncthing.net/.

After minimal setup, it just works(tm).

You have a normal directory in your filesystem, that is synced to the other peers (which you set up in the "minimal setup").

I have been using it for years, and it works well. It has no problems crossing os'es (i.e. windows -> linux, linux -> mac)

For windows I usually recommend https://github.com/canton7/SyncTrayzor, but vanilla syncthing works fine too (but don't try to mix them!)

Do consider Syncthing particularly if you are using Android. If using apple iOS you'd need the möbius sync client.

https://syncthing.net/

https://www.mobiussync.com/

One thing that it beats the cloud / centralized sync on is because the connection is direct between devices when the initial transfer is completed the file is completely there on the other device. With a cloud type of sync you do the transfer twice. I've seen stack up on large media or with the structure of cloud services pricing making it expensive depending on how your workflow is setup with inside and outside parties. For example, Dropbox deduction from all parties' storage limits not just the sharer.

You can also point Syncthing at a local sync of Dropbox or Google drive and then forward the files to other recipients from that for some purposes.

I think sync is a non-feature, as you can just ride on your existing solution.

For example, I use syncthing [1] with Obsidian to sync files off-cloud.

https://syncthing.net/

When I was 14 and just getting started, I used Notepad. Upgraded to Wordpad when I realized I loved putting italics in every other sentence, moved to Google Docs at around 25 when I started writing on my phone and wanted to sync with my computer, finally moved to Obsidian a few months ago (with Syncthing for syncing) when I decided I don't want to live in Google's house where they can burn my stuff down whenever they want.

Pick it up again an use cloud syncing this time! Is worth! https://syncthing.net/