• 1 Post
  • 65 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Full disclosure: Haven’t read the article yet.

    Working in corporate IT, this most likely is targeted toward enterprise customers who either take a long time to roll out OS upgrades or can’t due to technical limitations within their environment. In those cases, paying the cost of extended support is more palatable to troubleshooting or rushing mass OS upgrades. This is a fairly common practice with enterprise software vendors.

    Edit: Okay, just skimmed it. Looks like this is actually a new program for non-enterprise consumers, which is interesting. First I’ve heard of that.





  • Hmm…interesting. I would have figured it would be more akin mechanically speaking to being suffocated, as those scenarios also deprive the body of oxygen. Maybe the difference is that the action of breathing out and then breathing back in would be expelling any remaining oxygen from the lungs without replacing it with more oxygen?

    I am having a hard time following how it renders immediate unconsciousness though, given that one could simply breathe out to empty their lungs and then hold their breath for a short period of time without being rendered unconscious, and in theory that should be comparable. Sounds like I might be missing something key here that likely accounts for the disconnect.


  • I’m going to say that while everything I’ve read on the matter supports the “it’s one of the more pleasant ways to go” argument, I’d be more interested in reading expert opinions on the matter before coming to a concrete conclusion.

    The lawyers on both sides of the case should be consulting with doctors and medical researchers to understand what the experience would consist of, how long it would take, the efficacy, side effects if it fails, etc. This is the information that I think should be the deciding factor for proceeding or not.

    I will also say that while oxygen deprivation is quick, it’s not instant. It does take up to a few minutes in some cases before brain death to occur, and something to the order of 30 seconds to a minute for unconsciousness to set in.

    My personal opinion based on the information so far, assuming that everything I’ve read is factual, would suggest that of all the execution routes available so far, this one is likely the least awful. I won’t say most humane, as I don’t really believe there is a humane way to approach it. If we do have to use the death penalty though, I think this is the approach I would have the fewest objections to.






  • Hmm…this should work but I do have a concern on it based on my experience with AWS. Maybe this is different with minio though.

    In AWS, S3 bucket names are globally unique. Not just to your AWS account, but across ALL S3 buckets period. So let’s say you have a username of “test” and use that policy. If that user attempts to create a bucket and that bucket name is taken, well that user is out of luck.

    Obviously if minio doesn’t require globally unique bucket names you’re probably fine, but otherwise this could realistically become a problem.








  • Yep, this is key. If you’re getting a bunch of malicious traffic from one source, that’s easily fixed. Just drop the traffic.

    But when that traffic is coming from hundreds or thousands of sources, that becomes much harder to address. Can you just drop traffic from those sources? Sure! But then you also risk dropping legitimate traffic.

    There are also services that can automate the detection and prevention of DDOS attacks such as CloudFlare and Akamai, but these can get expensive very quickly, so it can significantly increase the cost to running the instance in question.