“Falsehood flies, and truth comes limping after it, so that when men come to be undeceived, it is too late; the jest is over, and the tale hath had its effect: […] like a physician, who hath found out an infallible medicine, after the patient is dead.” —Jonathan Swift

  • 1 Post
  • 110 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2024

help-circle


  • You do not need to soak your hands in oil before washing, not sure where you got that from. Soap and water works fine.

    I should clarify that my comment was assuming that, like in the OP, someone was handling a Carolina Reaper. Capsaicin being fat-soluble should mean that it dissolves into the oil and then gets carried away by the dish soap. I’ve never had to use this personally, since just dish soap and water has always worked fine for me.



  • TheTechnician27@lemmy.worldtoFunny@sh.itjust.works•Gardening Mishap
    link
    fedilink
    English
    arrow-up
    40
    ·
    edit-2
    10 days ago

    Okay, but ice isn’t good for this; it’s a chemical burn, and capsaicin is fat-soluble. You ideally want something like milk. Meanwhile, on your hands (assuming some of it got on those), you want to cover your hands in oil and then wash them with dish soap (and once those are clean, if there’s residual burning, you can use topical pain treatments).


    Edit: My understanding of the term “chemical burn” was mistaken. Thanks to @Nurse_Robot@lemmy.world for calling me out on this. I didn’t know it had to be corrosive or cytotoxic to be a “chemical burn”; I thought irritants generally were included.


    Edit 2: Actually, looking further into this, I’m not so sure I was technically wrong at the level of capsaicin you’d be exposing yourself to with a Carolina Reaper. Capsaicin can be cytotoxic. I wonder now if very minor nerve death occurs at this level of spice. Either way, that’s not the main problem if it’s even happening; my comment was wrong regardless of possible technical accuracy.






  • > “sounds like someone trying to push their preferred language onto others.”

    > didn’t even name Rust in the first comment

    I literally only talked about Rust when someone else mentioned it, because I’m not specifically talking about Rust.

    Whereas yes, Rust is relevant to the Linux kernel for obvious reasons (matching C’s speed and being easily interoperable with it), I said “a modern language” because I’m talking generally about the use of old, unsafe languages and major exploits surrounding problems that modern languages fix cropping up every 5 seconds.

    I’m not going to police my own tone about what are clearly negligent engineering practices. SWE should be treated with the same level of scrutiny as other engineering fields when its poor, outdated practices are constantly causing accelerating worldwide damage.



  • I mean yes, I do, given safe Rust inherently fixes seemingly every exploit listed in this article:

    • RCE from integer overflow (not possible by default in Rust, CVSS 9.0)
    • RCE from a race condition (not possible in safe Rust, CVSS 9.0)
    • An exploit of a buffer copy
    • An out-of-bounds write leading to local privilege escalation
    • Using an uninitialized resource
    • TCP query stack buffer overflow leading to local privilege escalation

    I feel like it’s the 1960s and I’m being told “we get it, you like seatbelts”.


    Edit: Sorry, re: the first one. I was misremembering based on a mix of a few things (see below). It does this in debug mode (which in itself is good to have), and it won’t compile if it can detect an overflow statically, but it’s not checking over/underflow at runtime by default. It can do this if you want it to, but that’s an inherent speed penalty from C. I was thinking of Swift, which does automatically detect integer under/overflow at runtime unless you explicitly tell it not to on a per-operator basis.

    In the spirit of not making you “trust me bro” since I was so wrong about the integer under/overflow one, here’s Rust’s overview of how safe Rust guarantees against data races.