Telegram and Signal are just as centralised and vulnerable as Meta (to censorship, political blackmailing, metadata collection to incriminate its users, …), just don’t? Federated is much more resilient, and with Matrix being essentially an indiscriminate metadata aggregation and replication engine, prefer XMPP.

Wow, as someone who has been hosting XMPP for family for 10+ years and only liking it, I’m amazed by the overwhelmingly supportive comments for it, it’s like people are recovering from a Matrix hangover and rediscovering the things they already had for their merit. So yeah that’s my +1: XMPP is really something dependable, it just works, and the sysadmin story is great too (my preference goes to ejabberd for the best “turnkey” experience, but you can’t go wrong with prosody either if you are willing to read some guide).

You don’t have to be on the NAS’ physical network to run some tests, if you can SSH into it, that’s enough to run some speed tests and latency tests to reference servers (e.g. Google, netflix, …), while doing the same from your PC simultaneously. Whenever you encounter “instabilities” you should be able to see which side of the connection is struggling more than usual. You should also be able to monitor the NAS itself for excessive IO or CPU using something like htop (even though that would be rather extraordinary if all that’s going on with it at that time is a Borg backup).

On the topic of Kopia, you can go the easy route of setting up a SFTP remote pointing to your NAS. All you need is SSH access to the NAS (so your current tailscale/borg set-up qualifies as is) and a folder where the SSH user can write. You can then compare backup times vs. Borg (in my use case, going from 18-25min with Borg down to 3-5min with Kopia). If you then want to try the HTTP repository server, there is a container for that, but the set-up is a bit annoying (the password to decrypt the repo needs to be stored on the NAS, you need to generate a SSL certificate pair and have the client whitelist the sha256sum of it, etc). Personally I haven’t found a substantial advantage to having the http repository server but YMMV.

Tailscale being merely a wrapper around Wireguard, which is pretty close to optimally efficient, I don’t think there’s much of an improvement to be expected by rolling your own or hopping over your VPS. You should probably start with investigating what’s causing the tailscale connection instability (is it your ISP? Is it the network on the side of the NAS?). If you are not bound to Borg, perhaps you can give a shot at Kopia, I found it to be much more performant for my use-cases, and it has a http “repository server” which you might be able to use with less protocols overhead than through your current setup.

Or plain old CalDAV

It’s there on the readme: https://hacdias.com/2026/07/28/filebrowser/

The project needs a rewrite from scratch, but the author had enough.

How does that compare to wallabag? (Does it?)

You seem angry. It’s just too bad you couldn’t funnel this energy into learning and configuring nextcloud to your needs. It is actually pretty lean when you set it up properly. Anyhow, happy you found something you liked eventually.

Prosody is a great piece of software, and so is ejabberd which offers some perks. I can’t speak for the other servers (mongooseim, openfire, tigase, …) which I haven’t tried in a long time,

All that’s to say that it’s amazing that we get so many well maintained and compatible servers (and clients) implementations in XMPP-land, and all the implications for its healthy future.