BarbecueCowboy

This doesn't work because no matter how many potions you have, you have to save them for when you really need them. Then, you end up finishing the game having never touched any of them.

It sounds like you're getting into the keeping it running phase.

First, going back to your previous comment, self-hosting email is difficult. It's not hard for a small provider to end up blacklisted and you're probably kind of just done at that point and it will feel very unfair. I get that it's a fun set of technical challenges, but you couldn't pay me enough to help someone self-host email.

Second, guessing, but it sounds like you may be trying to expose your services directly and doing a lot to make that work which goes against what most would recommend for hosting your own services. Big companies don't expose their intranet like that, follow their example. Almost every guide or system is going to warn against that. If you're going to host more than one thing, highly recommend focusing on minimizing entry points and looking into a VPN-like solution for accessing most if not all of your services. Still spend time on securing your intranet, but most of your risk is going to come from how hard it is for people to get past the front door (or doors).

We already have that, the first problem is we have like a dozen of them, a few are even well supported. The second problem is that usually the technical knowledge required to set up the systems are still lower than the technical knowledge required to keep it running.

My friend, if you don't think that's scummy then I think you're a little bit too acclimated to marketing scams.

Fucking podman... Oh man. I have lost way too many hours dealing with podman.

It's frustrating, because they've put so much into it. It's close enough that vendors think they can get away with saying their containers are compatible and they've probably really honestly tested for brief periods and it really usually is close enough that you don't discover the differences until you're already very well established, but then it's just a little different and it takes you FOREVER to find out why but then the only option once you do find that out is to completely start over from scratch with docker. And, almost no vendor is going to treat them differently because if we talk to redhat, the first note we'll get back is that everything we're trying to do should be fully compatible and there should be no need to worry about that. And, then eventually after a few weeks, it's docker's fault that IT WORKS IN DOCKER AND NOT IN PODMAN. Docker needs to go fix it so it's broken for them too, it's not a bug for podman, the problem is with the one that's working.

I'm a bit traumatized, not always the same, but this isn't a singular occurrence.

I'll thank them when they stop remaking perfectly fine utilities over minor issues then doing a shitty job with compatibility.

Aww, the AI almost figured out how to give the boat a real name. Look how hard it was trying.

Man, the arms on some of those people are nightmare inducing though.

You're not wrong, but if we want companies to keep doing things for good PR, we need to reward them for it.

They're basically giant badly trained dogs that happen to control every aspect of our lives.

"Women are my favorite Guy"

https://x.com/kylegordon101/status/1684963728427462656?mx=2

I am mystified as to what this says about me.

They work, but it's expensive and POC stage. They're mostly just not scaled to the level that we think we can take them to.

Not wrong, but they fucked up due to incompetence, not just some random preventable accident.

From the technical details I've seen, just having a basic testing process/environment should have easily prevented this. That should be the bare minimum.

Man, it took me a while to figure out you were on about the dude's username. I was real confused.