Now for comparison's sake, try snikket, or even barebones ejabberd on a (featuresfriendliness) vs (admin overheadserver resources) basis. Mix in some https://mov.im/ if you must.

I've said that before, but the O(N²) issue with E2E encryption only exists in an ideological sense. If your group chat is large enough that the overhead is unbearable, you don't have a private and secure group chat to begin with, just because a group chat of this magnitude is very much public by definition.

With that said, you can keep server logs encrypted while avoiding the payload/key rotation explosion by using static keys (available since forever with PGP in XMPP) or wait the decade (but most probably, the eternity) that it will take for MLS to be bolted on top of Matrix (and the new protocol design that this entails due to the absence of guarantee about messages ordering)

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.

Some might call it overkill or old fashioned, but my LaTeX CV versioned in mercurial as branches and hard linked clones has worked wonders for me for decades, now.

Not trying to convince anyone or to rationalize my own irrationality here but I'd rather have a working laptop to transfer from than a dead one, and with the fast increasing prices of components, the best time for a new laptop is either yesterday or after the AI bubble eventually pops and the market re-adjusts (I wouldn't bet the latter to take less than a couple years neither my current laptop to survive this long).

Buying second hand also means passing on Panther Lake, and LPDDR5, so a fast laptop is one thing, but with the goal of keeping it 8 years or so like the current one, efficiency is as important if not more. Efficiency figures are quite striking (and in the 60%): https://arstechnica.com/gadgets/2026/07/framework-laptop-13-pro-review-much-better-battery-much-worse-price/

I won't deny that, I'm rocking a ThinkPad T from 2019 which I love. But I'm on the market for a new one just to get back some peace of mind as it may run out of life at this point, and it would be silly not to see the advantages of lunar lake and LPDDR5 for battery life. Only the price be damned.

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.

It's 2026, you need to win the lottery to buy a laptop.

haut-vote parce que c'est vrai, et my bad, mon lien inclue en effet le scope 3. Si on se restreint à Scope 1+2, on trouve les mêmes majors du pétrole, entourées de quelques cimenteries, aciéries, et entreprises étatiques de production d'électricité crade. Sauce.

On peut dire que Total est responsable d’énormément d’émissions, mais les émissions sont surtout faites par les clients qui font plein.

Non, de la façon dont c'est comptabilisé, Total est responsable d'énormément d'émissions, parce qu'ils émettent énormément. Les émissions des clients ne sont pas prises en compte. Un exemple.

This data is used to quantify the direct production-linked operational emissions and emissions from the combustion of marketed products that can be attributed to these entities.

Un argument tout à fait recevable est de dire que la production d'hydrocarbures relâche nécessairement des hydrocarbures dans l'atmosphère, c'est vrai en pratique, mais ce n'est pas une fatalité, ou en tout cas pas dans les proportions actuelles, faisant que les majors privilégiant le rendement financier de leurs installations au profit du rendement climatique (une unité de production qui capte et stocke le CO₂ coûte plus cher à fabriquer et à opérer, les premiers temps de mise en opération relâchent énormément de CO₂ à la torchère, un système de re-pressurisation du puits par les gaz indésirables est souvent possible mais complexe, etc) est in-fine un choix politique.

Vrai.

Quels comportements ? 100 entreprises sont responsables de 70% des émissions, 32 entreprises (souvent étatiques, dans les énergies fossiles), de 50% des émissions. Je me déplace en vélo et mange beaucoup plus de légumes que de viande, mais à un moment il faut arrêter la déconne, qui est de faire porter le chapeau aux individus, excepté si l'on parle des milliardaires et groupes d'influence qui lobbient contre l'action climatique.

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

If you want notes "sometimes on the web, sometimes local first", and possibly more than just notes (with the tools to extend into an actual knowledge base), you might be better served by https://triliumnotes.org/

I'm holding off on Fluxer until they decide how they're going to implement federation

Seems wise. They seem competent in the front-end/client space and complete amateurs in the (difficult) protocol space. There is no example of successful tech (that I know of) that successfully added federation/P2P after the fact. It's not an afterthought, it probably won't ever happen.

Don't do Element, Matrix is a nightmare (and a significant commitment) to self host. Other servers (recently, continuwuity) are a bit better on that front, but then you run into compatibility issues and edge cases as a forever second-tier citizen.

My advice is to just go with XMPP and ejabberd, and you will find clients for all kinds of usages and people (a free-er WhatsApp takes you to Conversations/Quicksy/Cheogram/Monocles/Monal, a better banquet/IRC-style rooms takes you to gajim/fluux, social networking and group calling takes you to Movim, etc).

Personally my needs are covered by Monocles on Android, Gajim on the PC, and Movim on occasions. Using multiple clients around the same protocol and account is a strength, not a weakness.