Yes, without a doubt, for me it is the most balanced client, a pity that there is not for Android, but well, in mobile Element does not give problems either.

They are very focused on development and therefore the documentation is a bit sparse (maybe).

The truth is that it is not very complicated to install. It is simply to download the binary (it is statically compiled so it has no dependencies) place it in /usr/bin and execute it (the best is to create a user in the machine with the home in /var/lib/conduit and then launch it with systemd).

Another option is to simply launch it with docker.

In any case, if you have problems, comment it here and we will look to see what could be happening.

I recommend Matrix with the Conduit server. This server requires almost no resources and even runs on a Raspberry Pi.

Cinny works perfectly as a desktop client (in case you want to escape from the ubiquitous Element). And for mobile I would use Element for Android/iOS although FluffyChat also works very well.

Excuse me, but on what authority do you say it doesn’t suck? The comparison in the readme seems to be written by a resentful kid.

If you have an NVIDIA card don’t upgrade before see here, here and here.

Synching is currently the fastest and lightest you will find, but the concept is different from Seafile or Nextcloud. With Synching there is no central server, you have resources (folders) shared between nodes on a peer-to-peer basis. This has several advantages, the most obvious one is that if a node goes down the rest continues working, but also that if a file is available in two or more nodes when a new node enters it will download that file from all the nodes in which it is available. As a disadvantage we could say that there is no web server where to see the shared files, so you will not be able to enter a URL with username and password and browse the files and upload or download. You will not be able to share files with third parties through a URL either.

About that I have made the simplest possible implementation of a syslog server in Rust. I use it to collect OpenWrt logs and store them on my server. ;-)

LessPass has the possibility to connect to a database (via its API) to store the configurations made for each site. This API can be used from any of the clients (either the browser extension, the mobile application, etc.).

You set up the DB server wherever you want. If you want something light you can use this implementation. And if you are interested, there is also a command line client.

In my view, both a password file (vault/database) and LessPass are potentially attackable via brute force. I don’t see that one is safer than the other.

Before using borg I would recommend you to take a look at restic. In my opinion it is better in everything than borg.

As for how to backup the database, my advice is to export the database to a SQL file and backup that file. That will always be easier than having to deal with agents that connect to the database.

As for the number of repositories, if you use restic, a single repository is enough. Besides, as restic does deduplication, if you have the same files between your machines, they will only occupy the space of one. ;-)

I hope I have helped you with some of my ideas.

Best regards.