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.

Agreed, I think this is what is being suggested.

Flaming poisoning raging sword of doom.

I am just now starting through Fallout 4. I’ve had it in my library for a while but never got around to it.

I’m not sure that this is a “game” idea so much, but I’ve had this idea I haven’t been able to wrap my head around the implementation of.

Think a digital audio workstation such as Ableton Live or Logic, but gamified. Complete various musical objectives to pass levels, have a creative mode for just making music and maybe even a multiplayer mode for collaborative or competitive music making.

I tend to go back and forth between Go and Python. Typically for work stuff I am writing AWS automation utilities though so I’ll opt for Python because Boto3 is lovely. Go is typically for my personal projects.

I’ve also been itching to try my hand at Rust, but haven’t brought myself to start yet.

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.

My SO just had something similar pop up yesterday. She was running into weird errors on her Chromebook, so I had her change her user agent to Chrome on Windows. Everything magically worked. Hmm…

I’m lucky in that my employer went the opposite direction. Downsizing our local office and just letting us all be 100% remote. We’re a geographically distributed group so it doesn’t make sense to enforce office requirements.

Wait. I can automate my meetings too? I dig it.

I recognize the irony of this, but sometimes I like to fall asleep to the No Sleep podcast.

“It has awoken, and it is coming.”

This is why I personally am looking forward to fully self-driving cars. We’re a long way off, but when self-driving cars can completely replace the human element, I think the world will be a much safer place.

As much as a lot of that hate it warranted, I’d say the install location isn’t so much a Teams issue as it is a Windows issue and how it handles user-level vs system-level installs. Obviously still a Microsoft problem, but important to note.

Yeah, I’m kind of torn on this one. On one hand, having a drive replaced for an issue, then having that replacement fail with the same issue (or at least same effect) reeks of problems. That probably warrants merit.

On the other hand, it does show they likely have poor data backup practices if losing a single hard drive is costing them 3TB data loss. Either they were recording a day’s worth of video and lost it, in which case that sucks but it happens, or they had a ton of other data that likely should have already been backed up elsewhere in which case I have little sympathy.

Is it just me or do crabs always look so dainty when they eat?

Ah, neat! Yeah that would work then. I’d hope that your usernames are unique in your self-hosted setup, so that should work just fine. Very nice!

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.