aberrate_junior_beatnik (he/him)

  • 0 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle





  • Krasnov

    Wat?

    Wanting someone with disastrous mental health issues to not be capable of launching a nuclear strike isn’t ableism.

    Would you loan a gun to a friend who’s been really depressed lately? According to you, you should.

    Oh, I forgot that Truman, the only person in history to actually use nuclear weapons, famously only did so because he had depression. Or he was a perfectly mentally well person who was also a racist to the extent that he didn’t care about the lives of Japanese children. One of those. I always get it confused.

    Anyway, the answer to who I would loan a gun to and who should be capable of launching a nuclear strike is the same: no one. But I would trust your averaged depressed person with the nuclear codes more than I would Trump. To be clear: if Trump has a mental illness, that is not the thing that is wrong with him. What’s wrong with him is that he’s a fascist.




  • Follow the guidelines as mentioned in freedesktop

    Which guidelines are you talking about? Searching for “proxy” and “environment variables” didn’t pull up anything I saw that would be relevant in this case. I’ve been using linux for a couple of decades now and I’m not sure what rule is being broken here.

    It sounds like you didn’t have a proxy set in your environment variables, but you did have one set through another means. It’s somewhat standard practice to have fall-through settings, where if settings aren’t set in one place, a program looks in another place, then maybe another, etc. Now admittedly it would be nice to have a way to disable functionality entirely, but usually that kind of thing happens with command line flags.

    I get that it’s frustrating to deal with a problem like this, but ultimately your environment was misconfigured, and that’s going to break some software.












  • The meme text itself refers to “frequent” updates. Seems weird to compare apples to oranges, since release updates are not frequent. Even still, updating from buster to bookworm was relatively painless; certainly not 3 hours of reconfiguration. Before that, I was on Ubuntu, and the release updates were also painless; I remember multiple times not needing to do anything except uncomment the sources.list(.d) changes.

    [edit: Another quick point. Since Debian/Ubuntu manage configuration for you to some extent, you don’t need to fix configuration files as often as you would need to on Arch, hence not needing to do ~20+ config changes for two years of updates all at once.]