Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 24 Comments
Joined 2 months ago
cake
Cake day: June 9th, 2024

help-circle

  • If the root commentor is being serious, then I think it might be a trauma thing. Their profile specifically calls out being queer, and I can imagine many scenarios in someone’s past where conversations about being “masculine” or “manly” were… un-fun, let’s say. I know I felt some uneasiness as I initially read the headline and article summary due to my own childhood experiences. I’ve been told to “grow a pair” and “be a man” too many times for conversations around masculinity to be easy, and that’s as a bi cis man (I can sometimes appear to conform to the societal norms while being true to myself). I’m sure that it’d be much harder for someone who is gay, nonbinary, or a trans woman.

    I dunno. I see trauma in so many things nowadays. Maybe it’s there in this case, maybe it’s not, but I figured I’d call it out. Their trauma and the responsibility for managing it and healing from it belongs solely to them if it exists. If they’re being a bad faith actor, then they can fuck off.




  • Badabinski@kbin.earthtoLemmy Shitpost@lemmy.worldOlympic casual GigaChad
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    edit-2
    10 days ago

    Your eye is still open under that flap though, no? I dabbled in Olympic pistol shooting back when I was doing across-the-course service rifle, and I was told to always keep both eyes open by the dude teaching me. Same for service rifle (and later palma). I always found that closing one of your eyes fucks up your focusing. If you don’t have the little flappy dealy, you just do your best to defocus/deprioritize the view out of your non-dominant eye. I actually went for quite a while without any sort of cover because it helped me avoid cross firing (which is probably more of an issue with across-the-course than with Olympic pistol).

    You’re absolutely right about the lack of spectacles though. This guy is one hell of a marksman.


  • They need to do what MacOS and Linux have done. There are safer ways to interact with and inspect the running state of the kernel in those operating systems (eBPF for Linux, a bunch of APIs I don’t know much about for MacOS). Software needs a way to do the shit it’s doing, you can’t just turn it off and provide no alternative.

    If Microsoft provides a safe API, then Wine can translate calls to that API and approximate the same degree of protection for Linux boxen.

    I also agree with the other person, you should still be allowed to fuck around with the kernel on your own box. Major software vendors should be discouraged from writing shit that directly runs in ring 0, but end users should be allowed to do whatever.


  • The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

    I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

    EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

    EDIT: Erasure coding is deffo implemented, however.


  • Badabinski@kbin.earthtoLinux@lemmy.mlHyprland is now fully independent!
    link
    fedilink
    arrow-up
    62
    arrow-down
    4
    ·
    edit-2
    17 days ago

    What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

    My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.





  • The other person may have responded with a fair amount of hostility, but they’re absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you’re powerless to fix it unless you’re willing to debug the app and fix the leak. It’s better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.



  • For blood (and especially old dried blood), I’ve found that oxiclean in cold water works well. Fill a bucket with a small amount of the hottest water you can and put some oxiclean in. Give it 30 seconds to dissolve, then fill the bucket up with cold water (follow the instructions for quantities of oxiclean and water). Then, put your bloody garment(s) into the cold water and let them sit for about 6 hours. Remove from the water, gently press some water out, and immediately launder your clothing as you normally would. If there’s still blood, do another cycle before washing.

    Don’t do this if the care tag specifically excluded any form of bleach. In my experience, it works especially well on period stains.




  • Eh, I have a low tolerance for this kind of bullshit. I know what I like and what I don’t like. I went through their posting history before blocking them, and I found that the subjective quality of their contributions failed to outweigh my irritation towards them. To me, it’s better to just block them and never risk seeing comments like this from them again. There are a bunch of people on this site who I’d rather interact with.

    As a bonus, they’ll only ever have one shitty passive aggressive comment from me to deal with.