• 0 Posts
  • 278 Comments
Joined 4 months ago
cake
Cake day: June 8th, 2026

help-circle


  • Christa Pike was sentenced to death. The sentence itself was already fairly controversial, due to some of the details of her case. And now the state has attempted to kill her twice, but they keep fucking up her lethal injection. She has been injured during both attempts, but not killed. She even requested a firing line instead of a lethal injection, because she has a heart condition that will likely prevent the lethal injection from properly stopping her heart. But the state has refused to back down, and keeps injuring her with bad lethal injections instead.



  • Yup, my watershed moment was when I found out my rapist had died. He was an older man who I had always brushed off as a bad teenage experiment. I didn’t even realize how much fear and anger I had for him, until I heard through the grapevine that he had died. Suddenly, I was staring at my Facebook feed, seeing some mutuals posting about his death, and had tears welling up in my eyes. Not tears of sadness, but of shame and anger.

    It was simultaneously emancipating and also enraging. I suddenly knew he wouldn’t be able to hurt anyone else, and he wouldn’t be able to hurt me again… Until then, I hadn’t even realized I was worried about that. I had been carrying an immense amount of shame as a result of the “he has probably done this to others, and will probably do it again in the future” train of thought. Everyone says victims should report so their rapists can’t hurt others, right? And since he was an openly gay older guy, I statistically would have had a higher chance of being believed, right? But reporting would require telling others about what had happened, and I couldn’t even imagine doing that.

    But I also knew that since he was dead, he would never see justice for what he did to me (and likely others before and after). He was very wealthy, very well-connected in my local area, and he died comfortably in his own bed. None of which he deserved. Knowing he would be feted his wake was absolutely enraging, because he only deserved a cardboard box underneath the local prison.

    It was also what eventually led to me realizing why I had historically been so homophobic. I was born and raised in a conservative area, so homophobia is just par for the course here. But I eventually realized that I had been projecting my fear and anger of him whenever I saw a gay couple in public. And that what he did to me wasn’t their fault. I had also been externalizing a lot of my own shame. Nowadays I’m a staunch ally, but it would have been extremely easy for me to simply dig my heels in and refuse to do any soul-searching. I was definitely the older lady in this comic for longer than I would like to admit. And I have an immense amount of respect for the victims who do come forward, because I know what kind of determination that would take.



  • Is Pizza Cake a controversial artist? Genuine question, because I personally haven’t seen any strips that would make me dislike her. But I also only see the ones that get upvoted on Lemmy.

    I guess there will be some chuds who dislike comics like this one, which clearly advocate for something. But that’s pretty standard chud behavior, not limited to any one specific artist.


  • Carl@anarchist.nexustoLemmy Shitpost@lemmy.world•BONNGGGG
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 days ago

    I can actually confirm that dropping a piano makes the characteristic BOOOOOONG sound that we all know. I’m not sure if they actually dropped a few pianos to record it… But I have personally dropped a piano off a ~10’ drop, (and was in the room when a second piano got dropped ~6’) and it sounded exactly like what you’d expect.

    All of this is to say that if they didnt drop a piano, (because that’s risky and very expensive just for a sound effect), those foley artists were really fucking good at their jobs.



  • Satan is a title. Before the King James Version, the title of Satan was used like a black hat in an old western movie. It’s not any one person or entity, it is whomever acts as the opponent for the specific story.

    The KJV wanted to make the Bible more approachable for the average person, because the Church of England had a very “it’s only for the rich and powerful” vibe that it was trying to shake. One of the ways it did this was by simplifying some concepts like Satan, condensing the multiple Satans into a single recurring entity.

    That’s also why the KJV leans so heavily into the thee’s and thou’s. That was informal language at the time, mostly used by the peasant class. And if you’re trying to make a book more approachable to the peasants, you write it in peasant-speak. Ironically, we tend to think of “thee” and “thou” as sounding extremely haughty, but it’s because the peasants always emulated the rich. The rich used “you” and “yours” instead, so that’s what the peasants eventually gravitated towards to try and sound proper. And now to modern speakers, “thee” and “thou” sound like they’re from an era of kings and queens, so we tend to associate them with royalty instead of the peasants who actually spoke it.

    You’re thinking of Lucifer, who is often God’s henchman before he rebels. His whole schtick was that God would tell Lucifer to go tempt some mortals, to see if they pass His purity test. And Lucifer, being God’s most perfect creation, was immediately disarming and charming. Nobody would be tempted by a dude who obviously looks like a devil. God basically sent Lucifer (the world’s most solid California 10 with a disarming personality) down to earth, to tempt the dirty mortals (who pulled teeth to try and cure the common cold, and had probably never seen anything above an unwashed Iowa 1.5).


  • Yup.

    For the unaware: modern hash algorithms have character limits, but it’s nothing that would ever interfere with a regular password. Even accounting for the salt that gets appended to the end of your password before it goes into the algorithm. Most of the popular hashes have a 128 character limit, and the site will also store a salt in your user’s database entry. That salt gets appended to your password before it goes into the hash. Basically, even if two users have the same password, the hash for each will see “password{Salt1}” and “password{Salt2}”. So they won’t show as the same hash in the database, even though they’re the same password.

    This salt is to prevent something called a rainbow table attack, where a hacker feeds a bunch of common passwords into a bunch of common hash algorithms, then compares with their stolen database. If they find matches, they now know which algorithm the database was using, and they only need to brute force the database once. So for instance, they feed “{common password}” into several hashing algorithms. One gives the result “1234567890”. They then check their stolen database, and find several users with the hash “1234567890”. They try using {common password} on those user accounts, and they work! Now the hacker knows which hash algorithm was used, and can brute force the entire stolen database at their leisure.

    By appending a salt to each password, “{common password}” actually becomes “{common password}{Salt1}” “{common password}{Salt2}”, etc… So even if the hacker tries to brute force it, they would need to brute force each individual password instead of brute forcing the entire database all at once. It’s still important to use strong passwords, because a weak password will still be broken in only a few seconds. But that will be a few seconds per weak password, instead of a few seconds for every user at the same time. This is why sites tell you to change your password after a breach. The idea is that salting the database makes brute force attacks take a lot longer, and gives most users time to change their passwords before the attackers manage to get anything.

    All of this is to say, you could have a 100 character password limit, and still have plenty of room for a 16-28 character salt. And the hashes will output the same length string regardless of what you feed into it. So longer or shorter passwords won’t matter, because they’ll all turn into a 64 character hash in the end.

    So putting a low character limit on a password is a site admin tattling on themselves, because it means they’re not hashing your password at all. If they were hashing it, the only upper limit on your password would be whatever the algorithm can accept (probably 128 characters) minus 20-30 characters for a salt.






  • they produce the stuff they do because there’s demand for those products. If nestle stopped bottling water and selling it at inflated prices while being shitheels… someone else will step in to meet the demand that exists.

    This is literally the origin of the term “the customer is always right.” Imagine you create the world’s most perfect product. It is truly revolutionary. It meaningfully improves your customers’ lives, it is easy to manufacture and get to your customers, it is cheap, and it is durable. It is all of the things that a perfect product should be. And you have a competitor. This is a bad imitation. It’s more expensive, it’s less durable, it’s worse at what it does, and it’s more difficult to manufacture.

    And yet, the competitor is consistently selling out, while you struggle to sell enough to make ends meet. Even though your product is better in every measurable way, you are selling the wrong product. The customer is always right, and in this example the customer wants the shitty (and more expensive) version. It doesn’t matter how good your product is in comparison. The customer is the ultimate driving force behind whether or not you’ll be able to sell anything, and is therefore always right. If you insist on selling your perfect (but unmarketable) version, it isn’t the customer’s fault when you go bankrupt. It is your fault for trying to defy the customer.

    And you know what companies like Nestle, Amazon, etc are really good at? Finding what customers want. And yes, the customer tends to be stupid and short-sighted. But the customer is always right.




  • It’s because you only need to take an oath if you’re testifying. And arguing isn’t testifying. Lawyers are already bound by ethics standards for things like lying. For instance, if a lawyer knows you killed someone, they can’t openly say you didn’t.

    They can argue that the evidence is lacking. They can argue that the prosecution hasn’t done enough to prove your guilt. They can find gaps in the prosecution’s case and start poking holes to provide reasonable doubt. But they can’t put a witness on the stand who they know is going to lie in your defense. And that includes themselves. Also, no lawyer would want to take the stand, because then the opposing lawyer would have a chance to cross-examine them directly while they’re under oath, and likely have them testify against their own client. It would be a very big can of worms.


  • No, she probably isn’t. ICE has intentionally operated in a way that makes filing lawsuits against agents nearly impossible. In order to bring a lawsuit against an agent, step 1 is finding out which agent harmed you. And ICE has intentionally made that as difficult as possible, with unmarked vehicles that don’t even have plates, masked agents without any kind of identifying marks, constantly shuffling agents around so the agent who hurt you yesterday probably isn’t even in town today, burying any kind of discovery behind mountains of red tape and then systematically refusing to fill valid requests for info, etc…

    Basically, unless your agent is unmasked via independent detective work, the chances of being able to file a lawsuit are near 0.