

Thanks for that detail!
I thought it was still “de facto” rather than “de jure” by this point.
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.


Thanks for that detail!
I thought it was still “de facto” rather than “de jure” by this point.


The need for “proper domains”, where “proper” nowadays seems to mean “Trump-approved”, is an important risk, because then the identity of your homelab depends on the DNS and SSL cartel. It’s one of the reasons I distrust the Gemini protocol and consider it a raw downgrade from Gopher (and from HTML, for that matter).
If home.arpa is the way to go local, then it’s the way to go local.


I get that, and I think it maps well. If no solid info is delivered on what the vulnerability is, or how to manually patch, then there is no gain all pain to me paying it more mind. It’s much like asteroid watch: if someone yells “there’s an asteroid coming!” and I ask where, when, what size, and nothing of that has useful actionable info, things are not different than if they instead had yelled “good morning!”.
I have to assume that the security measures currently in place will suffice for the platforms standing as-is, among other things because higher-ups have not approved for stricter measures or for technical debt solving or for paid overtime, etc.
Which does get me wondering - we have a mechanism to secure once the correction comes out: we pull from upstream. But is there any sort of similar mechanism (esp. for Docker / Podman) to distribute, pull and apply declared mitigations in the meantime? Such as changes to httpd.conf, etc.
EDIT: yes I know this is about enterprise or at least hired stuff, whereas this particular community is self-hosted. But IMO, that difference only makes things overall worse. In selfhosting I’m definitively not paid to over-care, nor to sacrifice my mental health. I already have enough with the world as-is. Get me UBI, and then we can start talking about how it feels to sit before a docker pull screen all day while sipping on a margerita.


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.


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.


What’s so wrong with XML? All web browsers use it (HTML is literally slightly-freeform XML), Libreoffice also does (XML is part of the Open Document format spec), Freedesktop… eeeh, let’s not mention them, and so far we are doing golden.


I’m unsure what’s the progress status over there so I’ll say “yes?”.
Which reminds me, I think there is a binding somewhere that lets XMPP send SMS messages, but dunno how if any is that related to phone call compatible audio.


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.


Hmmm, I’d… say… “get a better phone”, but there’s not much of a better alternative there.
Get a desktop / laptop computer?


Safari
Get a better browser? HTTP is as legit a transmission protocol as HTTPS and email are.


That sounds interesting. But then you have to convince your peers to install your certificate root, right?


HTTPS for everything means you have to buy into the cartel of “identity providers” that manage DNS and certificates, even if there are some mostly-good actors in there such as Let’s Encrypt, you still have the external dependency. As we have seen with cases such as Austistici, having that dependency can be a problem. It’s your call if it is in your case or not, but I wanted to raise this point because no one has pointed out that particular weakness vector so far in the thread.
In a very general sense, if your services are under a netbird or any sort of VPN where you control who gets account access or not, you “should not need” HTTPS. Might still be convenient to have.


¡Admittedly a fair point!


No one said the pedophile elite was any smart.


No, it sold us.


What is the target audience?
At these prices, the Pedophile Elite. Heck, the Trump Phone was half this price!


Just look at that Big, Beautiful Bill Pedophile Price Tag!
Yeah it’s one of the reasons why I madee the later edit comparing enterprise vs selfhosting. In enterprise, real damage to the shareholders is made if you disable your service. Won’t you please think of the shareholders? Whereas in selfhosting… well, the damage is lots lesser, although it does invariably include the potential that your users (family etc) willl turn tail towards the enterprise option.