

Eh, the cronjob on podman image pull && podman compose up will take care of it. I’m off to get a margerita.
I write English / Escribo en Español.
Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.
This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.


Eh, the cronjob on podman image pull && podman compose up will take care of it. I’m off to get a margerita.


“we”? XD


fire 20% of their personnel
slopify
things fail
Sounds like a closed case to me.


Self-hosted messaging was solved decades ago, it’s called XMPP or Jabber depending on who do you ask. There are a number of services for it, such as Prosody or ejabberd, and there are both client apps (eg.: Conversations for Android, Gajim or Dino for PC) and a number of webclients (such as converse.js which can actually be shipped via a ejabberd install).
That said you could just set up an alternative Signal client that allows for custom servers, since the centralization of Signal only really exists at the level of the client only connecting to Signal’s servers… Signal’s people have pointed this out themselves, when offering bridge setups so that people could connect from Iran or other countries where those countries blocked Signal’s endpoints.
I really like their take on, essentially, “don’t drop everything just because there’s yet another CVE”. There being vulnerabilities is the “normal” under our current development of technology. The core is making it a non-tiring normal. When I hear there’s a new CVE I give a quick read to the minutes. If it can’t pass the test of working beyond “requires a user already logged running a specific program from /tmp instead of $PATH, with the computer facing left and the brightness of the monitor set to 72.3% o a Tuesday”, then I leave it for the nightly cronjob to upgrade the container, and even if that somehow does not work then I would be checking tomorrow anyway. The higher-ups are not assigning a fair paid overtime for this, or even any at all, so.