Call it what you want. Just don't use accurate terms like apartheid, genocide or war crime.

Like pretty much every other word in that comment, we'll never know if the misgendering is intentional satire or not.

And, like news networks, maybe the router companies are forced to let him hire a censor (they like to call them ombudsmen) so the white house can real-time block inconvenient traffic.

In the same way as not releasing angry bees into your cube farm is doing nothing, yes!!

I get the impression bhyve does all that stuff too. Is sylve basically just a thin GUI wrapper on top?

(That'd be amazing if it's possible to do stuff like dump configs + check them into git from the cli, then stand them up on any bhve/sylve box later...)

It's not silly at all.

I've been repeatedly burned by systemd, both on machines I've administered and on appliances. In every situation, the right fix was either "switch distros" or "burn developer-months of work in a fire drill".

In fact, I just decided to go with FreeBSD instead of proxmox specifically because proxmox requires systemd. The last N systemd machines I've had the misfortune to touch were broken due to various systemd related issues. (For large values of N.)

I assume that means anything built on top of it is flaky + not stable enough for production use.

I have never really understood the systemd hate. It sure as hell beat the sorcery that was managing init.d scripts for everything.

I managed the distro upgrade on hundreds of remotely-managed nodes, porting our kiosk appliance from a pre-systemd debian to a post-systemd debian, and out of all the headaches we suffered systemd was not one of them, short of a few quirks we caught in our development process. It pretty much just worked and the services it provided made that upgrade so much easier.

Curious how you got burned, I hear a lot of complaining but haven't seen a lot of evidence

I don't understand the init.d script hate ;)

It absolutely is silly. I’ve been responsible for managing low-thousands of Linux servers with systemd and it’s standardized a lot of things that otherwise would’ve been a lot of bespoke scripts.

Yeah, I’m kind of in the same camp. I never really had issues with systemd either. It mostly just works, even if it’s a bit heavy.

For me, moving to FreeBSD wasn’t about escaping systemd, it was more about the overall system design and how cohesive everything feels. That said, I’ve tried to keep Sylve neutral on that front. I don’t really position it as “systemd vs not”, just focus on what it actually does well.

It’s still early and not as feature complete as Proxmox yet, but I think it already stands on its own as a solid option.

Is there an easy way to know if I'm vulnerable to this? Like some dashboard page that lists all the API keys with "revoke" buttons?

I did something or another with a google API years ago, and am not looking forward to a random surprise bill. They don't have my credit card, so maybe that'd solve the problem. On the other hand, they could hold a gmail account hostage.

You should definitely log in to Google Cloud Console and roll all the keys you see in there if you're unsure. I just did the same thing after I realized I had a lot of surface area with these keys.

Wait! I think most people missed your "touched by Copilot" disclaimer.

Over on twitter, someone from MS said that Copilot can modify PRs simply because they were mentioned?

I've been using GitHub since it was new and heavily rely on coding agents for development, but that's an insanely large security hole. There's clearly confusion about what copilot is and is not able to edit elsewhere in this thread.

I'm backing up old repos now, and am no longer trusting your service as an archive. I'm wondering if the world needs to fork things like npm and vs code to save itself from the supply chain attacks these sort of product management decisions will enable.

I already moved active development elsewhere when you dropped below three nines back in 2024-2025.

I would expect it to comment, not alter the code?

It won’t unless you ask it to. It will review your PRs and it will create PRs if you don’t turn those things off, I believe, but it won’t edit or modify any PR.

My employer pushes copilot quite hard and I’ve never seen copilot do anything without me telling it to act in some way.

Thank you for clarifying. It’s hard to get facts nowadays, people are just claiming whatever.

Demand it be made illegal. Vote, especially during primaries, and almost never for an incumbent.

I strongly suspect that this is already illegal - publicity rights are a thing - and the the demand that needs to be made is for the law to be enforced.

Claude is absolutely in love with github actions.

It's pretty much the worst CI system I've ever used, and they don't even supply runners for all my deployment targets. However, it keeps recommending it.

I guessed the first wave of ads would be in the form of poisoned training data, but MS seems to have beaten that crowd to the punch with these tips.