• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • Lemzlez@lemmy.worldtoLemmy Shitpost@lemmy.worldWelcome to petty lane
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    12
    ·
    8 days ago

    I agree it’s safer to let them pass, but a medical (or personal) emergency does not give you the right to endanger other people on the road by driving fast and/or recklessly. That’s why they paint priority vehicles in bright colours and put flashing lights on them - to make it safer for everyone.

    If you have a medical emergency, you call an ambulance. Yes, they will have to drive to you first, but care starts when they arrive. If the emergency isn’t big enough to get an ambulance, there’s no reason to drive fast either.




  • Nuclear is subsidized? I think you’ve got that backwards. Renewables are HEAVILY subsidized in many places (rightfully so), nuclear isn’t.

    Nuclear would be, in fact, the cheapest form of generation if you factor in storage which is a requirement for a functional grid based on renewables, and aforementioned regulatory handicaps weren’t in place.

    A grid based on nuclear for the base load (the always-on stuff like various industries) + renewables is a far better solution than dragging on fossil fuels for longer and longer, or trying to make 100% renewables work with gigantic amounts of expensive storage.


  • The difference being that when you’re 10 billion into a renewables project, you usually have SOME generation already, whereas your nuclear reactor isn’t doing shit until it’s fully completed.

    I don’t mind nuclear, but the fact is that the reactors take decades to build, whereas renewables can be deployed far quicker. Going all-in on nuclear, and then twiddling your thumbs for 10-15 years while the reactors are built doesn’t sound like a great idea.


  • I don’t think programming language is a good metric for security. I assume everything I host has issues, and then try to mitigate from there.

    IMHO, a better approach is to vet the project beforehand, looking at whether it is still actively maintained. I usually use things like commits, issues, etc to try and gauge whether a piece of software is actively maintained so that when an issue arises, it can be fixed.

    You can mitigate much of the risk by using some basic best practices, like isolating all apps from each other (using docker, for example), using a reverse proxy, tools like fail2ban or a web application firewall, using proper database permissions for each app, etc

    What I also do is add another layer by making certain applications accessible only over vpn. That won’t work for some tools, obviously, but also reduces the risk for tools you are only using yourself.