• 0 Posts
  • 36 Comments
Joined 15 days ago
cake
Cake day: December 4th, 2025

help-circle

  • Sure, but with “current” I mean the current understanding of science. We know the earth is round, but not because we discovered it, but because it’s the general consensus that is taught, barely anyone doubts it. Trying to - let’s call it “rediscover” - the scientific status quo is something I do like because it might always be the case that the people before were wrong. This is how new discoveries are made and I think that is a great thing. As an example, nobody believed that continents did actually move, and Wegener was ridiculed because he had no sure way to proof it, but at some point, people had the way to proof that he was actually right.


  • You know, I really like it when people think twice about the “current” state of science. Thinking “I don’t think that’s true. So I will check and verify” is a great thing and most people should do that. Thinking the earth is flat is fine - if you then go to verify.

    The problem I have is if there is PLENTY of proof of things being a certain way that you just choose to ignore. Then you become an idiot.




  • The only thing why this is still the case is because microsoft is bundling everything in a single subscription and is also providing you with software that automatically keeps everything updated.

    The software is shit, but companies using the entire ecosystem probably save money. Sadly.









  • Retard was a legitimate word, then it became a slur so we invented “special needs” which is now also a slur, so we have “intellectual disability” (which isn’t even appropriate as you can be retarded without having an intellectual disability) which will inevitably be used as a slur at some point.

    I think most people are just getting tired by getting tone policed more and more.




  • So, first of all, I barely ever had to work with d-bus directly - I used it a few times and it was fine to use.

    Without any well-defined standards, a protocol is essentially useless and/or lawless

    When I look for “D-Bus Specification”, I get this: https://dbus.freedesktop.org/doc/dbus-specification.html. This LOOKS like a proper documentation of the standard to me.

    the general lax nature of how endpoints are intended to be defined … is a significant factor for why many applications are the way they are

    I feel like this is the same complaint people have about other things, like PHP for example. They see shitty PHP code (like wordpress) and are like: “Oh my god PHP is such a shitty language because this application is written like shit”. But I don’t blame a language, a framework or a protocol for the failures of the users. I don’t feel like an application that close to the system core has to be absolutely “dummy proof”. At some point, we should just expect that people know what they’re doing, and if they don’t, we should blame them, not the underlying technology.




  • How do you notify yourself about the status of a container?

    I usually notice if a container or application is down because that usually results in something in my house not working. Sounds stupid, but I’m not hosting a hyper available cluster at home.

    Is there a “quick” way to know if a container has healthcheck as a feature.

    Check the documentation

    Does healthcheck feature simply depend on the developer of each app, or the person building the container?

    If the developer adds a healthcheck feature, you should use that. If there is none, you can always build one yourself. If it’s a web app, a simple HTTP request does the trick, just validate the returned HTML - if the status code is 200 and the output contains a certain string, it seems to be up. If it’s not a web app, like a database, a simple SELECT 1 on the database could tell you if it’s reachable or not.

    Is it better to simply monitor the http(s) request to each service? (I believe this in my case would make Caddy a single point of failure for this kind of monitor).

    If you only run a bunch of web services that you use on demand, monitoring the HTTP requests to each service is more than enough. Caddy being a single point of failure is not a problem because your caddy being dead still results in the service being unusable. And you will immediately know if caddy died or the service behind it because the error message looks different. If the upstream is dead, caddy returns a 502, if caddy is dead, you’ll get a “Connection timed out”