I don’t know, to be honest; I’m not deeply familiar with its workings. I just know that I made a habit of running a command “dry” without sudo, both because not everything should be done with superuser privileges* and because it’s a way to make sure I get the syntax right, then if it does need sudo, I repeat it with sudo.

*Which is why sudo -i (the interactive mode) is a dangerous tool that shouldn’t actually be your default mode of working

Pretty sure the person you responded to knows that and is joking, since you can hardly have a fraction of a CVE. Germany (where their instance is hosted) uses comma for decimal separators, so that joke is pretty close at hand.

Doesn’t it autocomplete? I mean, not if it’s an argument for sudo, obviously, but my terminal starts in interactive mode anyway, so that’s rarely an issue

Then you’re probably more knowledgeable on the topic than me. I did a great job of only learning the basic minimum of frontend development in my WebDev classes, never mind UI design or UX testing. If it weren’t for a webapp QA gig I did for a while, I would’ve had no experience with usability at all.

I have one accessibility quibble:

WCAG 2.2.2 recommends that any moving content, such as your carousel of reviews, have some mechanism to pause it. More information can be found in the accompanying Understanding WCAG document.

I didn’t do any full accessibility test on your page. I don’t know if you care about WCAG compliance anyway, and frankly, I wouldn’t expect it for a hobby project. It’s just one of the details a professor of mine drilled me on so thoroughly that I still remember it eight years later.

The saying applies to the “bird”, meaning the person using language models to generate code, not to the projects that code is contributed to. The risk of sliding into overreliance and dependency on machine-generated code is real and part of the reason I staunchly refuse to try it, but it’s not the responsibility of the maintainers of the project to guard its contributors against their own lack of care.

The project maintainers only care about the quality of their contributions, so that is the target we should judge the policy by.

We know that AI “guardrails” are about as reliable as the models they’re supposed to guard. So instead, we need human safeguards in place to hold the result, whatever its origin, to a high standard.

In that spirit, the KDE contributor guide makes it clear that you need to be able to own and explain the code and answer any questions, “even if it originates from the internet, an LLM, a friend, or your pet lizard.” Whether that slop is natural or artificial in origin matters less than the fact that it’s slop.
There is also a provision for dealing with unvetted contributions: “Throwing code over the wall” explicitly uses the example of “relying on an LLM to generate a patch, and then trying to get it merged without understanding the actual changes” and encourages maintainers to reject such requests.

So by these policies, if that proverbial bird gets stuck and stops delivering useful contributions, their slop should be rejected. Whether they use a text generator to produce arguments why it should be accepted doesn’t matter if it’s unacceptable.

Read the actual post. The stance is much the same as the kernel’s: If your code is solid, it doesn’t much matter how it came about.

The idea is that good code shouldn’t be identifiable as LLM-generated. If it’s within the general variance of human coding styles, abides by standards and the logic is sound and humanly understandable, it’s practically impossible to prove that it’s AI anyway.

If your code reeks of AI slop, it’ll be rejected because nobody wants slop. You, not your tools, are responsible for the quality of your contribution.

That is very different from the “fuck quality, use LLM for the sake of using LLM” mentality Micro$lop are exhibiting.

If you look closely at almost any large community, you’ll find both lovely and awful people and interactions. I try to be part of the former, but I confess that I sometimes fall in with the letter. I think that’s just human nature, but we tend to notice the negative more than the positive.

Glad to restore some memory of youth to you ;-)

Hope it helps, or is at least an interesting read

I think this was the one:

https://wiki.linuxaudio.org/wiki/system_configuration

I added threadirq to the launch options as described under “Using the threadirqs kernel option”, which solved it for me, but you’ll probably want to read the whole page anyway.

which is audio related

flaskbacks intensify

I’ve never has freezes, but I fought my pipewire for a long time over chopped-up audio. I believe some kernel flag for real-time interrupt handling solved the issue at last, which I found on some audio forum after three evenings’ worth of tinkering and fiddling and eventually scouring the internet when I accepted I wouldn’t figure it out on my own. IDK if it’s of any use to you, but I can dig it out if you’d like.

Read again. Not “runs destiny” (as in the game) but “runs your destiny” (emphasis mine). It’s a joke about faith controlling your fate.

That makes you one of today’s Lucky 10,000.

(The figure is US-based, but it has become proverbial even beyond the US)

Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do.

Some

Who?

would argue that it is the opposite of being a Nazi.

If they would, I’d love to hear how membership in an organisation centered on hatred against a non-Aryan culture is the opposite of being a Nazi.

(Besides, membership in the EDL is hardly the only indictment against Robinson)

I think that’s the distinction between an expert using a tool diligently and responsibly, and a lazy person using it haphazardly as a crutch.

If that tool ever gets ripped out from under you, you’ll possibly suffer a loss in performance, but you’ll still be able to perform and do your job.

If their crutch is kicked out, they’ll crash.

Linux has made great strides to being approachable for new users. The agony of choice for so many things (distro, editor, nearly any tool family with more than one option) and the factionalism around the options is probably one of the few big obstacles left.

I don’t have a solution for the factionalism. I’d put forth a suggestion for a simple “standard” choice (Kate/gedit for GUI and nano for CLI; I personally use vim, but I think nano is more approachable) but I’m sure someone will disagree and we’re back to square one.

What could be more fun than hiding a landmine in your “convenience pile”? Every time you don’t want to retype a command, you’re gambling. Is it worth the risk to save those two keystrokes on ll?

Also, that’s a thing Systemd is (more or less) infamous for.

I’ve never heard of it before. I don’t know where it is infamous, I’ve never had that issue and of all the criticism I’ve seen levelled at Linux in general or systemd in particular, that has never been one. Maybe there was some configuration stuff, as the other reply mentioned?

I don’t think I’ve ever had that issue. My PC shuts down within a few seconds. What kind of things would refuse to terminate?