Interesting article about Medhurst and his use of GrapheneOS. Apparently he failed to turn off his phone before UK police boarded his plane and seized it from him, but the auto reboot feature protected his data and sources. The article also mentions that he's now in the process of writing a massive guide to security and privacy for journalists.

LOL! 🤣

dudes rock

This is a longshot but maybe someone would be able to help me with this. I have a laptop that only has a single NVMe drive. I booted it up today to find "Checking media presence......." after the splash screen and then it booted into BIOS. The BIOS doesn't see the NVMe device. I don't understand how this could've happened because I didn't update anything or change any setting or physically damage or jostle the laptop between the last successful boot and clean shutdown and now. When I boot into an EndevourOS liveusb, the installer can see my entire drive and its associated partitions. I can't access them though, I think because they're encrypted, but even so I feel like I should be able to see them in the filesystem, as I've rescued files like that before (from non-encypted drives). So I can't really make heads or tails of this. If the liveusb is seeing the drive and the correct partitions, it can't possibly be physical damage to the drive itself, right? Or any of the connections? Yet BIOS can't see it for some reason and won't boot into it. If it's worth anything, the OS on it is Arch with grub as the bootloader. Obviously I've tried to reseat the drive, move it to the other available slot, I've toggled on and off all sorts of settings in the bios, and nothing makes any progress. If anyone has any ideas, I'd be grateful. Thanks!

Editting to add: I'm not entirely sure the BIOS doesn't see the device. The menu is fairly unclear. There's a series of lines starting with "NVMe Device", which the corresponding entry is just blank. Then there's two lines of "NVMe Controller", one of which has an entry that I can't select or see more of that says "SAMSUNG (5...", which makes me wonder because my NVMe drive is 512gb, and I wonder if it's listed there? But I can't see anything beyond the elipses so I can't tell. Then the other controller line just says "Empty". Not sure what to make of that.

Second edit: There's a section in BIOS for RAID disks, and in it there's a listing for "Non-RAID Physical Disks" in which my NVMe drive is listed correctly. So maybe it's a bootloader thing? I'm so confused.

Final edit: Thank you so much for the help everyone, even though I'm sure my post was a confused mess. I luckily managed to back up all my files, so it's just a matter of fixing grub or reinstalling at this point. I hate computer :)

https://xcancel.com/ratlimit/status/1965945538903421439

absolutely incredible snapshot of our current era

yet it still scrolls me to the comments. curious

I don't like the new icon with a dolphin on it and I want the old clean folder look back. Is there a way to do this? I looked around but couldn't find anything.

~~i feel like there's a bingo on the vertical right side but i don't know what counts for those two open spots~~ bingo!

i did not make this, i pulled it from the news mega at the beginning of the year

petition to rename the site infinitybear

Just over a year before United Healthcare CEO Brian Thompson was murdered this week in Midtown Manhattan, a lawsuit filed against the insurance giant he helmed revealed just how draconian its claims-denying process had become.

Last November, the estates of two former UHC patients filed suit in Minnesota alleging that the insurer used an AI algorithm to deny and override claims to elderly patients that had been approved by their doctors.

The algorithm in question, known as nH Predict, allegedly had a 90 percent error rate — and according to the families of the two deceased men who filed the suit, UHC knew it.

As that lawsuit made its way through the courts, anger regarding the massive insurer's predilection towards denying claims has only grown, and speculation about the assassin's motives suggests that he may have been among those upset with UHC's coverage.

Though we don't yet know the identity of the person who shot Thompson nor his reasoning, reports claim that he wrote the words "deny," "defend," and "depose" on the shell casing of the bullets used to shoot the CEO — a message that makes it sound a lot like the killer was aggrieved against the insurance industry's aggressive denials of coverage to sick patients.

Beyond the shooter's own motives, it's clear from the shockingly celebratory reaction online to Thompson's murder that anger about the American insurance and healthcare system has reached the point of literal bloodlust.

As The American Prospect so aptly put it, "only about 50 million customers of America’s reigning medical monopoly might have a motive to exact revenge upon the UnitedHealthcare CEO."

And the alarming cruelty of the claims around the company's AI algorithm — we asked the company whether it's still using it, but received no immediate reply — perfectly illustrates why they're so angry.

This was the obvious and, in my opinion, desired (by them) result of the deluge of lawfare against trans people by these Christofascists. It's just unbelievably brutal to see the real numbers. to every fucking monster even tangentially involved with this campaign.