Oof, yeah, that sounds painful. It does sound like some kind of hardware-related issue, maybe the default settings in the Fedora kernel are seriously aberrant when mixed with one or more of your hardware components? Given the broad range of issues (GPU, network speed, audio), I'd be inclined to suspect the problem was related somehow to something core/common like CPU or mobo. Almost certainly not a pure hardware fault, given the problems didn't follow the hardware when you changed distros.
Sorry but I just don't like it. Not to say I think it's a bad distro it's just clearly not one for me.
I totally get it. Doesn't take much of that kind of frustration to leave a bad taste in your mouth. I had some perplexing intermittent lockup issues years ago that turned out to be BTRFS, or at least the issue went away when the VMs were rebuilt with a different root FS. I'm still leery of BTRFS, even though it was a fairly esoteric stack (SLES, ESX, NFS datastores served from a ZFS-backed storage server), so entirely possible the fault didn't lie exclusively with the filesystem. But I still avoid it, just because I've been burned once.
GrapheneOS aims to maintain update support for at least 5 years (from their FAQ). GrapheneOS still supports Pixel 5 for example (released 5 years, 8 months ago), Google stopped updating that model in Nov. 2023. GrapheneOS likely won't maintain support for older models forever, but for older devices they can extend the life a good few years past Google's end of support.
ETA: In fairness to Google, their support window on newer models is a lot better. From https://endoflife.date/pixel, for Pixel 8, 9 & 10 series they've committed to 7 years of Android updates. My Pixel 7 is only getting 4 years of updates, hence my interest in GrapheneOS.
I know, but... The opportunity cost of her occupying that position! Imagine if we'd had someone actually willing to exercise power to rein in Trump, instead of someone making tut tut noises while conducting massive insider trading. She deserves all the dragging we can muster.
This is it. A 2006 Ford F150 has a hood height of 51 inches, or just over 4 feet. Getting hit by one of these would be bad, but for many people it wouldn't likely result in a head injury. A 2026 Ford F150 has a hood height of 75 inches, or more than 6 feet tall. Getting hit by one of these as a pedestrian is practically a guaranteed head injury.
I'm sure there are other factors. Higher speeds, lack of investment in infrastructure, political unwillingness to make any changes that might increase congestion or slow down drivers. But I believe hood height is playing a huge role in the type and severity of pedestrian injuries in the US and Canada.
I think that part kinda makes sense. The lid is domed, which increases its strength. The seam where the lid meets the walls would tend to be the weakest point. I'm more surprised there was such a violent explosion in the first place, usually they just burn. Could be that tank was partially empty and the area beneath the lid was a highly combustible fuel/air mix. Drone hits the tank, vapour ignites, and pop.
Why would you even do that?? Props to the medical team, and I'm happy the victim healed so well, but seems like something that just shouldn't have happened in the first place.
I was gonna make the same comment but you beat me to it. Article title kinda buries the lede here, the "trained to bite" part seems so much more incriminating to me.
Likely reversed because whoever edited these clips together wanted the camera to be moving consistently forward. If they didn't reverse the middle clip it would give the impression that the camera was moving forward, then backward, then forward again. Editor probably figured most viewers would likely focus their attention on the waving flag and not notice the backwards walking. I didn't notice until I saw your comment and rewatched the clip!
Edit: but then there's a backwards camera move at the end, so now I'm questioning my own theory...
Definitely that, but also, are those pins not recessed or guarded?? That seems like really poor engineering. There could have been some kind of physical keying between the charger and the controller to prevent other metallic items from inadvertently bridging the contacts.
You're 10-ply bud!
Oof, yeah, that sounds painful. It does sound like some kind of hardware-related issue, maybe the default settings in the Fedora kernel are seriously aberrant when mixed with one or more of your hardware components? Given the broad range of issues (GPU, network speed, audio), I'd be inclined to suspect the problem was related somehow to something core/common like CPU or mobo. Almost certainly not a pure hardware fault, given the problems didn't follow the hardware when you changed distros.
I totally get it. Doesn't take much of that kind of frustration to leave a bad taste in your mouth. I had some perplexing intermittent lockup issues years ago that turned out to be BTRFS, or at least the issue went away when the VMs were rebuilt with a different root FS. I'm still leery of BTRFS, even though it was a fairly esoteric stack (SLES, ESX, NFS datastores served from a ZFS-backed storage server), so entirely possible the fault didn't lie exclusively with the filesystem. But I still avoid it, just because I've been burned once.
Care to elaborate? Not saying I doubt you, it's just the polar opposite of my experience and I'm curious why that is.
What an odd way to say "America started a drone war without enough weapons to intercept drones."
The frogurt is also cursed.
This made me ask "wait, is that true" and apparently it is. Super, skin cancer for everyone. 🤦
GrapheneOS aims to maintain update support for at least 5 years (from their FAQ). GrapheneOS still supports Pixel 5 for example (released 5 years, 8 months ago), Google stopped updating that model in Nov. 2023. GrapheneOS likely won't maintain support for older models forever, but for older devices they can extend the life a good few years past Google's end of support.
ETA: In fairness to Google, their support window on newer models is a lot better. From https://endoflife.date/pixel, for Pixel 8, 9 & 10 series they've committed to 7 years of Android updates. My Pixel 7 is only getting 4 years of updates, hence my interest in GrapheneOS.
I know, but... The opportunity cost of her occupying that position! Imagine if we'd had someone actually willing to exercise power to rein in Trump, instead of someone making tut tut noises while conducting massive insider trading. She deserves all the dragging we can muster.
This is it. A 2006 Ford F150 has a hood height of 51 inches, or just over 4 feet. Getting hit by one of these would be bad, but for many people it wouldn't likely result in a head injury. A 2026 Ford F150 has a hood height of 75 inches, or more than 6 feet tall. Getting hit by one of these as a pedestrian is practically a guaranteed head injury.
I'm sure there are other factors. Higher speeds, lack of investment in infrastructure, political unwillingness to make any changes that might increase congestion or slow down drivers. But I believe hood height is playing a huge role in the type and severity of pedestrian injuries in the US and Canada.
I think that part kinda makes sense. The lid is domed, which increases its strength. The seam where the lid meets the walls would tend to be the weakest point. I'm more surprised there was such a violent explosion in the first place, usually they just burn. Could be that tank was partially empty and the area beneath the lid was a highly combustible fuel/air mix. Drone hits the tank, vapour ignites, and pop.
Possibly some form of insurance. "Be a real shame if someone were to lob a drone at your big, slow, expensive oil tanker..."
Why would you even do that?? Props to the medical team, and I'm happy the victim healed so well, but seems like something that just shouldn't have happened in the first place.
TIL Spaghettios are ring shaped pasta in tomato soup...
Yes, the docs linked in OP's post have this note:
I was gonna make the same comment but you beat me to it. Article title kinda buries the lede here, the "trained to bite" part seems so much more incriminating to me.
Just one time, as a lil treat...
Not OP, but likely yes to your question. Looks like an aftermarket recoil pad to me.
The Anti-Defamation League.
Likely reversed because whoever edited these clips together wanted the camera to be moving consistently forward. If they didn't reverse the middle clip it would give the impression that the camera was moving forward, then backward, then forward again. Editor probably figured most viewers would likely focus their attention on the waving flag and not notice the backwards walking. I didn't notice until I saw your comment and rewatched the clip!
Edit: but then there's a backwards camera move at the end, so now I'm questioning my own theory...
Definitely that, but also, are those pins not recessed or guarded?? That seems like really poor engineering. There could have been some kind of physical keying between the charger and the controller to prevent other metallic items from inadvertently bridging the contacts.