Perhaps the deer introduced (bi)proportional representation and are living the good life now?
That's what allows me to vote 6th party without making my vote useless.
Perhaps the deer introduced (bi)proportional representation and are living the good life now?
That's what allows me to vote 6th party without making my vote useless.
Agreed.
You almost need an AI agent in a sandbox to download and run all the POCs to weed out the fake ones until one of them becomes well known.
Sounds like a good malware vector to target security researchers...
So it seems like it was rather easy for an IT security professional to create an exploit within 24h of the disclosure. Not sure if every script kiddy can do it, but this means that there are certainly malicious people/organizations who can.
Ultimately, it seems to me that the only real choice is to patch our (public) systems ASAP these days.
And it's like 5 sentences apart in the article xD
I think for me spin-down was working initially. But then I added some Docker containers and those could only be run on the HDDs, blocking spin down. With Debian I just put the containers on the smaller SSD, allowing the HDDs to spin down.
I like being able to drop in whatever disk I need to for expansion or replacement.
I didn't move that far away (to Debian + ZFS), so that limitation still remains. Although the addition of Raid-Z expansion should alleviate things quite a bit.
My NAS/home server takes about 180 kWH/year, or 20W on average (costs me about 5 Euro/month). This feels like a lot to me and makes up a good chunk of my total energy usage.
What I did to optimize it is mostly select a "low-power" x86 platform, and limit the number of disks. I also decided not to use TrueNAS because it couldn't let the disks from going to sleep.
The machine hosts 10 TB of usable storage (+RAID 1), syncthing, immich, file server, Influx DB, Grafana, and a few other services.
The kernel has supported it for a few years now and it's a supported architecture for Debian.
For me, the main thing holding me back from getting a RISC-V SBC/computer is the lack of high performance processors. But they seem to be making progress there too.
They also looked at Gnome and raw DRM. As mentioned in the talk, there's no significant difference between Gnome and KDE. Without VRR, they each loose one frame compared to the raw DRM. With VRR all three are on par.
The Gnome results are available in the repo: https://gitlab.freedesktop.org/klysik_nv/xdc_2026_latency/-/blob/main/Charts/heatmap_path_comparison.png?ref_type=heads
Keep in mind that they're talking about hardware control systems and not compute nodes. On these machines, the savings would probably not be too big (no/few consolidation gains). It also sounds like the decision was less about the upgrade cost and more about avoiding failure risks.
I also ran the numbers for fun. They estimated the cost to be 5.4MCHF for 2200 machines. Assuming 0.2CHF/kWh, they would need to save 140W per machine for 10 years to offset the upgrade cost. So, yes, it could indeed offset a good part of the upgrade cost over time.
Knoppix is a fun one :) Didn't know it was independent.
spoiler
Debian, Arch, Fedora, OpenSUSE, NixOS, Slackware, AerynOS, Alpine, Gentoo, LFS