Depends on your religion, I guess. The Flying Spaghetti Monster seems pretty edible.

one could argue this is a harmless way for people who suffer from this to get their fix.

I don’t know how many people get off from drawings. I think that AI-generated child porn might be better?

I’ve never understood the complaints about that. It’s not like real children are hurt by those drawings.

Also Ireland, Norway & Sweden.

If you make it amphibious and go fast enough, it will plane.

1. do not use ANY company resources. This could put you at risk of theft.
2. do not do it on company time or make it look like it’s on company time. See point 2.

Did you mean “See point 1.”?

I mostly agree with you, but this is not quite true:

XDG implementation (which is also only used as a fallback when the three DE-specific implementations fail, even though all of them actually support XDG so having separate implementations is pointless)

Yes, the DE-specific implementations is pointless (as far as I know, I use a WM), but the XDG implementation is actually used first, and the function returns true if any impl returns true, like xdg() || gnome() || gnome_old() || kde().

rework the code so that there is a difference between “this DE wants light mode” and “couldn’t figure out of this DE is in light or dark mode” - both of these are now represented by the “false” return value.

This isn’t that bad? Yes, having an enum with three variants would be better and more readable, but the code just defaults to light mode if nothing wants dark mode, and prefers dark mode even if separate impls want both light and dark mode.

With multiple impls, you have to resolve conflicts somehow. You could, for example, match on current DE/WM name, only using the current DE’s impl, defaulting to XDG, avoiding the problem entirely or just use first impl that doesn’t return “default” or “error”.

I don’t like AI generated code, having reviewed some disgusting slop before. But it’s better to criticize the code’s actual faults, like the incorrect impls (which you listed) or failing the Linux CI.

What about “I’ll accept your pull request if you accept my merge request”?

Their vision is based on movement, stay perfectly still.

You’re thinking of a different kind of predator. I don’t think that would work against sexual predators.

The theory of everything?

I meant the following:

1. Find out the Debian package is too old
2. Create Arch Live USB
3. Boot Arch Live USB
4. Copy GRUB config from the Debian install to the current Arch live system
5. Install the up-to-date GRUB while in the Arch environment

The bootloader installer package is distro dependent, the bootloader the package installs isn’t. You can boot Debian no matter if the GRUB is installed from Debian stable, Debian Sid, Arch, Fedora or even FreeBSD. Otherwise, dual booting wouldn’t work.

Like I said, I’ve done that before, though with SystemD Boot instead of GRUB, which was a bit simpler due to how the bootloader is configured.

emerge --ask cake
...
[ebuild  N     ] dev-dotnet/cake-5.0.0  USE="-debug"

Huh. Seems like Gentoo really has a cake recipe.

As it’s a bootloader, it should make almost no difference which distribution was used to install it. (I’m not sure if Debian patches their GRUB.) I just used Arch as an example, as it is famous for being up to date. And, no matter where it’s installed from, if you’ve made changes to GRUB’s configuration, you’ll have to copy it over to the live distribution to keep your changes.

Yes, Debian Sid might be more familiar for Debian users, but that’s it.

Edit: You said “get the grub debs from Debian sid”, but installing Sid packages on non-Sid systems isn’t something that you should do.

But bootloaders are distro/OS agnostic. Why wait for Debian, when you could, for example, boot an Arch live ISO to install a newer GRUB?

I don’t use GRUB, but have done the same thing with SystemD Boot before. As GRUB’s configuration system is a bit more complex, you might have to mount your main install to get the correct config file.

Unlike Windows, on Linux you need to run ./<command> instead of just <command> for executables in you current directory.

That’s quite fast, do they cause many accidents?

You can blame the EU for that:

pedal cycles with pedal assistance which are equipped with an auxiliary electric motor having a maximum continuous rated power of less than or equal to 250 W, where the output of the motor is cut off when the cyclist stops pedalling and is otherwise progressively reduced and finally cut off before the vehicle speed reaches 25 km/h;

Bikes that do not comply with that are classified differently, and at least here, have to be registered as motorcycles/mopeds. Which won’t go through, as, for example, the brakes are typically not motorcycle-grade.

source

Where I live, they’re only allowed to assist to up to 25km/h (about 15.5mi/h), so I can ride a lot faster with a normal bike.

What kinds of limits are there for (e)bikes where you are?

Here, for electric bikes, they have an age limit of 15 years and a BAC limit of 0.5‰.

I’ll see your ebike and raise you a non-electric bike.

Lemmy is not GPLv2, but AGPLv3.

So, the game would have to be (A)GPLv3. (The licenses are fairly interoperable. IIRC you can use AGPL components in GPL software if you abide by the terms of the AGPL.)

Viral licenses are nice and all, but they’re not without their drawbacks. I caught GPL recently (the slightly rarer Affero v3 strain) and now no DNA testing companies want me as a customer. I can no longer write MIT or BSD licensed code. Whenever I open a project, a LICENSE file appears within ~15 minutes of contact. I hope to recover soon.