esbeeb

Yep, everyone has forgotten the term "TCO", it seems

"linux+nginx+postgres+favourite-lang" - I agree here. Yes, don't over-complicate things.

I too have that same Dell Optiplex 3060 micro. I love it for experimenting also. Also use wireguard for remote access. I use incus for my Linux containers, preferring it to proxmox.

People complain about how they hate to use the command line in Linux. But they don't similarly complain about these ultra obscure, ugly commands. When Microsoft necessitates commands, somehow it's different.

This is a flex!

Every narcissist will love this, and I'm not kidding. This is their catnip: attention itself.

MS Edit in the house! /s

DoH is the enemy of all self-hosters. When port 443 is used, you can't discriminate on it - to perhaps monitor it, work towards debugging it, block it, re-route it, etc. DNS shouldn't be a stow-away within some other protocol like HTTP, hiding from network-level scrutiny and control.

DoT is the friend of all self-hosters. Self-hosters need to control their own DNS if they want to use SSL within their LANs, within their self-hosted VPNs, and within their own self-hosted VPN subnets especially (I use Wireguard subnets a lot). Secure DNS with TLS, sure, but this control-ability, at the port level (853), is what a self-hoster needs to keep their life sane.

WebRTC is very, very hard to code for. But if FFmpeg abstracts that complexity away, then WebRTC becomes much easier to add to a software project wishing to benfit from that which WebRTC offers.

Gajim, the XMPP client, has been awaiting this for a long time! Their Audio/Video calling features fell into deprecation, and they've been patiently waiting for FFmpeg to make it much easier for them to add Audio/Video calling features back again.

"If I type the @ symbol in a group to mention a participant Meta AI is in the list." - I just tried it myself in a group chat, but I don't see it. Maybe it's just starting to be added? or was made invisible to being listed by "@"?

actually, push-to-talk voice memos do work Gajim. An underrated feature!

Prosody allows voice and video calls - I have a TURN server all set up with it - but QOS rules (which are beyond my control, and are the fault of the ISPs I use) can sometimes squash calls made.

Gajim 1.9.3 (Flatpak) seems support voice and video calls to Conversations, but then it doesn't work. One Conversations smartphone can make voice and video calls to another Conversations smartphone.

I run Prosody XMPP server on a cheap VPS, and appreciate how it's a stock Debian package, greatly simplifying security updates. It's delightfully lightweight on the server.

I use Conversations as a client in Android, and Gajim in Linux.

The basics like OMEMO, file attachments, push-to-talk voice memos (in Conversations, but not Gajim) work well. All comms are at least client-to-server-encrypted, and the OMEMO-protected comms are end-to-end encrypted.

I agree the slowness is a deal breaker. (Note: I tested it out a few years ago, but never went beyond that prototyping phase)