Running a constant arp poisoning attack on a whole network trying to mitm the dns server just to block ads is going to be unreliable as hell, and it'll screw with more than just dns traffic.

If you control the network, it's far simpler and more reliable to point clients to a dns server that blocks ads. And if you don't control the network, probably shouldn't be attacking it this chaotically.

Like, magically?

I prefer a Sofirn Q8 Plus - it's half a kilogram so it takes a lot of duct tape to secure it to the bars, but the 16000 lumens are worth it. Car cuts you off? Double click to just vaporize them.

I still listen to the Riven soundtrack, 29 years later. It's so rich and atmospheric, and composed and performed by one of the game's co-designers Robyn Miller.

Everything about that game was beautiful. Still holds up today.

Omarchy is just a bunch of dotfiles in a Hugo Boss trenchcoat pretending to be a linux distribution.

More laws written by people who have zero fucking idea what they're writing laws about.

A partial solution to this evil-maid attack vector is Heads firmware (a replacement for the bios/uefi itself), which lets you sign the contents of your unencrypted boot partition using a gpg key on a hardware token, and verify the integrity of the firmware itself using a totp/hotp key stored in the tpm.

All the benefits of secure boot, but you get to control the signing keys yourself instead of relying on a vendor. It's great stuff.

Government thugs interrogating me in a Project 2027 concentration camp cell: "we know you gave someone named 'homeassistant', born on 1970-01-01, access to your server, now tell use where they are!"

I was raised with Gloria Steinem's definition of feminism shaping my understanding, and have called myself a feminist since I was a child:

"A feminist is anyone who recognizes the equality and full humanity of women and men."

A more modern and inclusive version of that same idea, adopted by UN Women:

"Feminism is the belief that everyone, regardless of gender, should have equal rights and opportunities."

Feminism is a very complex grouping of movements and ideologies, but I think "membership" within them is very simple: if you believe in equality regardless of gender, you're a feminist.

Of course the secondary opt-in user repo with unvetted package maintainers is infected with malware, it'd be a miracle if it weren't! They warn as much in the docs. Use at your own risk, or package and maintain it yourself, because you're likely not finding it packaged more reliably elsewhere.

And I love Debian, but if you think the Debian repos with 30,000+ packages and 1000+ community maintainers aren't also infected with malware...

Because that cuts into their profits, and they won't do that until forced to by law. Tale as old as time.

The full text of the AGPL with no line breaks.

"The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software..."

Everything I run, I deploy and manage with ansible.

When I'm building out the role/playbook for a new service, I make sure to build in any special upgrade tasks it might have and tag them. When it's time to run infrastructure-wide updates, I can run my single upgrade playbook and pull in the upgrade tasks for everything everywhere - new packages, container images, git releases, and all the service restart steps to load them.

It's more work at the beginning to set the role/playbook up properly, but it makes maintaining everything so much nicer (which I think is vital to keep it all fun and manageable).

Not a disk issue, but looks instead like an issue with power management on that thunderbolt root port at 0000:80:1b.4. See this thread for proxmox-specific writeup: https://forum.proxmox.com/threads/kernel-7-0-x-regression-acs-violation-on-pcie-port-80-1b-4-causes-vm-freeze-%E2%80%94-arrow-lake-thunderbolt-5-intel-arc-b50-passthrough.184312/

And here for more: https://github.com/minisforum-docs/MS-02-Ultra/issues/10

Looks like you can resolve it for now by either reverting to 6.17.x kernel or creating a udev rule for the device.

To allay any confusion like I had, DRM in this context refers to the Direct Rendering Manager, a subsystem of the linux kernel responsible for interfacing with gpus.

That's good, that's the whole point - if there were nothing wrong with android/google worth picking a fight over, graphene wouldn't need to exist in the first place.

I want my graphene/EFF/etc teams rabid, angry, picking fights, and armed with bazookas.

This is a week-old repo with a 163,000-line initial commit, and the test repo that init was dumped in from is filled with hundreds of claude/codex co-author commits. Regardless of whether it's to hide the ai co-authoring, it's shady to obscure a repo's initial work like that.

I could be wrong, of course, but this smells like yet another overambitious ai-slop project that'll get abandoned in a month.

modprobed-db can create a profile of the kernel modules that get loaded by your system over time. You can feed that directly into make localmodconfig to build a kernel that only includes those modules, or use the data to build a modprobe whitelist.

Scoopta living in 3026

It sucks that google changed its chatbot name from bard to gemini and drowned this cool project out in the process. It's a beautiful simple thing, and feels like the internet as it once was and should partially remain.