There is no dedicated native mobile app yet (though there is a bounty for it), so the mobile experience happens via a PWA that is decent for browsing and quick editing, but lacks offline support

If you need semantic notes with typing and structure, nothing beats https://triliumnotes.org/ IMO/E

The pace of the project is moreover very high these days

For the record, it seems the project moved on, just without its previous maintainer, to github: https://github.com/tt-rss/tt-rss

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.

I disagree. You are just entertaining the idea that servers must always and forever be oversized, that’s the definition of wasteful (and environmentally irresponsible). Unless you are firing-up and throwing-away services constantly, nothing justifies this and sparing the relatively low effort it is to deploy your infrastructure knowingly.

Precisely what pre-devops sysadmins were saying when containers were becoming trendy. You are just pushing the complexity elsewhere, and creating novel classes of problems for yourself (keeping your BoM in control and minimal is one of many others that got thrown away)

Self hosting doesn’t mean “being wasteful and letting containers duplicate services”. I want to know which DB application X is using, so I pool it for applications Y and Z.