You could switch some of the problems with perf in switching away from the Python implementation server as well as Element clients but these support the most up-to-date features & the majority of users are now relying on these features that often don’t degrade graacefully.

The bigger issue is eventual consistency. Eventual consistency will not scale for small self-hosting. Every message & every attachment for every user in every chatroom they have joined must be duplicated to your server. This is why joining rooms sometmies takes 10 minutes. Even if you make this async from the client side instead of the current long wait, your server & storage are still taking the hit. A lot of small collectives had to drop their servers for performance & cost (read about yet another one today on the Techlore thread at c/privacy where now only Discord is used for realtime coms). This model is required to copycat the ability to search the entire history like the big, proprietary chat apps such as Slack/Telegram/Discord, but they are centralized so it is easier to manage—but its overuse for all announcement & trying to replace forums turns it into a black hole for information. Your small community probably does not need persistent chat like this—persistent info is lighter & easier to crawl as feeds & forums. With medium-sized servers shutting down, only the biggest & smallest hosts are still kicking with most metadata is largely centralized around Matrix.org who also hosts some of the other larger instances.

If you agree that chat can be chatter as well as ephemeral there is lightweight centralized chat in IRCv3 with TLS has most of the features you need with a longer legacy & massive choice for clients & XMPP for lightweight decentralized chat with a long legacy, client options too, & can be self-hosted in a bedroom on a toaster in comparison which increases the chances of self-hosters & decentralization. These were built in a time when we didn’t have such wasteful taste in tech since they needed to be efficient & only sip power/data in comparison both for clients & servers & storage. The bigger question IMO is what are fundamentally wrong with these two mature options that we need a new option built on unextensible JSON & Israeli Intelligence money?

Exactly. Our words matter & the sooner we stop using Google to mean search or MS GitHub to mean code, the sooner we can start shifting the narritive towards entities that better respect our privacy or even gasp self-hosting. Word choice for social change is just as important for spreading the message.

Hardening aside, I like that LibreWolf actually lets you turn on JPEG XL.

They will say “it’s just Git so we can easily switch whenever” but 90% of the time the start buying into the platform-exclusive features & say it will be too difficult to move later. I can have sympathy for legacy projects before the buyout, but now you 're purposefully buying in despite knowing better.

client or server that doesn’t support the same encryption protocols

Outside of TLS which most any server uses by default, XMPP or not, the server is not responsible for E2EE. Conversations Compliance & Are We OMEMO Yet have existed for a long while & I never see anyone recommending a client not on these lists so while certain features may be fragmented, the communication essentials have been more or less established for years now. XMPP is an extensible format, and some applications that aren’t for chatting with your friends/family, don’t need many of these features which allows the protocol to morph into something stripped down for the task… which is why the base spec is basically barren, & community XEPs are what folks get behind for adding new features for different use cases.

The best is to not trust the centralized server of either of these platforms. Set up your own XMPP server & gives these the boot.

A little less lock-in is literally a little bit better

These support UnifiedPush, not just ntfy. UnifiedPush is an open protocol whereas ntfy is an implementation of UnifiedPush. I use my Prosody server to deliver my UnifiiedPush notifications.

Libera.chat & OFTC exist for this purpose to do chat for open source without needing to set up a service.

You can use something like Nix + home-manager & take your environment with you.

Obsidian’s fork of Markdown. Don’t expect compatibility.

I get why soulless corporations do this, but why do regular folks choose to publish their content on Medium, Substack, Devto, etc. when this is the shitty UX they’ll be forcing on their readers.