No, more like as if this is the straw that broke the camel’s back

The comment does contain tips on how to set it up though

I’m an Arch user. I check the diffs when I update a package. I won’t do anything as I’m obviously not compromised.

Hahaha I’m old enough to get that one, but I’m sure there are zoomers going “tf they’re talking about dogs now”

Welp, you wouldn’t be the first who actually believes what you wrote!

So far I’ve just checked the diff of every package update. But with that many, I think we should maybe start using using the script provided in the article that you evidently didn’t read.

That’s not how that works.

• when you use distribution-provided packages, you trust the distribution maintainers
• when you use the AUR you trust the upstream project and check the PKGBUILD because the maintainer can change

In some cases, upstream also maintains the AUR package, in which case you can probably trust that it’ll not be abandoned

Arch usually doesn’t re-package Python packages that aren’t needed for something else, meaning they end up in the AUR. I maintain several there, and when I stop using them I abandon them. I wouldn’t be surprised if some of the ones I used to maintain are on the list

Arch actually has a large amount of official packages. Maybe some of the packages you’re referring to are just slightly renamed or alternate versions?

It’s possible that in some areas it has fewer packages of course (e.g. Debian might repackage a larger subset of PyPI as Python packages), but I need the AUR for very few things.

Paywall.

And then your auto-formatter removes them in a blink.

Mine times out sometimes during boot due to an encrypted volume, but there seem to be no problems beyond that. Also I assume that wouldn’t have happened if I hadn’t switched to homed without need.

All in all I don’t think I had any non-self-inflicted issues, and apart from this one, I fixed the rest within a day each.

There should be a large, soft keyboard with attached touchpad for the sofa, then a setup like that would be perfect. Using a mouse on the couch is kinda weird.

Your conspiracy myth is wrong, and if you actually care about what’s true, you can confirm what I say very easily for yourself:

Just go to the mailing list archives and forums and follow the decision making discussions of the time. E.g. Arch Linux. This will quickly and decisively convince you that “big tech” had nothing to do with it.

But you don’t care about the truth, do you? You just want the comfortable position of being able to look down on all the mainstream fools.

If you criticize something because of perceived bloat, maybe don’t make it the mouse in your metaphor.

And no, it’s a great init system that has all the features one wants. That’s why it ended up taking over: it was the first really good init system that introduced actual dependencies and so on.

These aren’t serious. Their mission statements are nothing but childish contrariness.

E.g. Artix has a “no true Scotsman” right in their tagline about “real” init system. Only 14 year old master debaters will attempt to deny that systemd is a “real” init system with a straight face.

LMAO, good one!

And before that books and comics. But LLMs are different: they pretend to be your friend but actually just encourage whatever you come up with. You can easily fry people’s brains by being their sycophant, now everyone can subscribe to one.

Nah, people just started using LLM assisted vuln discovery workflows and having early successes with them.

There will be diminishing returns.

Two mistakes:

1. The all setting makes little sense, unless someone wants to enforce a zero-AI policy. It shouldn’t have been the default. In-line completions don’t justify attribution, so the chatAndAgents setting makes more sense (there can be more arguments made about uncopyrightable LLM output and the fact that “creation height” can’t be automatically determined)
2. The code is bugged and attributed the contributions of other LLMs to copilot

The one you cited is more of a safety measure against the intersection of these two issues: if the code would work correctly, it wouldn’t add the copilot line anyway.