The syncthing server only gives metadata (no files, only IPs) between the devices, so they can connect to each other. And it's self-hostable.
As to how, I'd probably use zfs send | receive, any built-in functionality on a CoW filesystem, rsnapshot, rclone or just syncthing. As to when, I'd probably hack something with systemd triggers (e.g. on network connection, send all remaining incremental snapshots). But this would only be needed in some cases (e.g. not using syncthing ;p)
Yes, it's subject to firewall
It would be great if it had some grammar of graphics embedded in the UX
FOSS thrives in options, and that's just great. There's a compromise between security (i.e. anonymity) and convenience (i.e. speed). This tool focus on the security side. Meanwhile, seedboxes strike a good balance to both. That's the current scenario, there are many ways to share. That diversity provides resilience to the communities ;)
Try checking out KWallet settings. It's the app in charge of saving passwords in KDE.
Edit: I was wrong. Dismiss the comment!
~~Was'nt this person transphobic? To me that's relevant. I wouldn't like people giving them support in that case.~~
I thought he was only prohibited entrance to the Postdam city (where the meeting with AfD and CSU happened)
Musify, it's on f-droid
I use git (without remote repo, but could be easily added). Actually this simple bare git repo technique is something I enjoy doing in lots of places where config files lie.
Basically, it's only: alias config="/usr/bin/git --git-dir=\${HOME}/.myconf/ --work-tree=\${HOME}"
Of course, a first time setup is required:
git init --bare $HOME/.myconf
config config status.showUntrackedFiles no
I got this setup from a comment on HackerNews long ago. OP comment was rather insightful: "No extra tooling, no symlinks, files are tracked on a version control system, you can use different branches for different computers, you can replicate you configuration easily on new installation."
But I never used any branches, prefer to keep it extremely KISS. I even avoid commiting, just staging area that I keep updating with each OS upgrade. Only this bit of extension I use... since I don't push to any remotes (prefer keeping dotfiles private), I needed a way to copy all of the tracked files (e.g. to have my settings on a work laptop, of course I then go ahead and clean any boilerplate before moving such an 'exported' folder)...
config_export() {
echo "Copying only staged files, it is recommended to run beforehand: $ config add -u ~"
mkdir -p ~/.config_export/
CONFIG_FILES=$(config status | /usr/bin/grep 'new file:' | cut -d':' -f2 | sed -E 's/^ +//')
printf "%s\n" "${CONFIG_FILES[@]}" | xargs -I {} cp --parent '{}' ~/.config_export/
ls -halt ~/.config_export/
}
Tmux starts a daemon the first time, it's quite opaque on that regard.