man man-pages tells writers to only include examples if it is complicated to piece together, otherwise just explain what man page you need to read before, e.g. understanding open(3) before read(3).

And the default GUI configs come with Firefox iirc!

“There’s no need to download a different browser”

bash: Sudo: command not found

And rm won’t work either, since you (probably) don’t have files named - and rf, and then it will complain that / is a directory. And even if we correct that, you forgot to pass --no-preserve-root.

Notch’s Bugatti is far less likely to spontaneously combust (because it was made by professionals, not AI), and if it did, it wouldn’t affect as many people. Omarchy claims to be an easy version of Arch, when in reality, it’s just doing what every beginner would be doing, including all of the accidental security holes, and then adds some more weakpoints through the unchecked shell scripts.

Part of those 8 million do go into paying “the Hyprland guy” (Vaxry)'s salary, and he himself hasn’t been very politically correct. DHH also is quite open about choosing “anti-woke” projects (i.e. without a CoC).

Linus has already chimed in, and wants Zstd to just use the standard way of checking for CPU features instead of rolling their own. Apparently, that would be even faster, compiling to a single jump instruction.

Very likely. Or, at least what the thread commenter meant. There’s other programs vulnerable to …/, but it’s mostly some kind of Application Firewall, one that inspects the message itself.

The Vienna Convention allows you to use either STOP or your native version. Likewise, you can either use a red octagonal sign, or a red upside-down triangle inside a red circle. https://de.wikipedia.org/wiki/Bildtafel_der_Stoppschilder (that list only seems to exist in German Wikipedia)

All hail the third temple OS!

Mutter is made by GNOME, what do you expect?

snix (rest in piss)

Nix Lix Guix

Client-side decorations. In most DEs and WMs, the compositor or the shell is responsible for the window border, Close button etc. On GNOME, the client (application) is expected to do all of that. There is a mechanism for a WM to request an app whether to draw CSD, and for the app to request SSD, but they don’t need to be implemented.

Then the deal needs to be changed. Contracts are not above the law 🤷

As a member of Hack Club, I can’t really believe that Hackatime is really slop-free…

The nixos-unstable channel actually does ensure a minimum set of required packages work: Those that would prevent you from booting. The compiling-from-source is because Hydra (the binary cache) only starts building once a package appears in nixpkgs-unstable, and if it immediately proceeds into nixos-unstable, or one of its dependencies is different there, that build won’t be finished yet. release- and versioned nixos- don’t have that problem, as they have a merge freeze, and are mostly fast-forwarded along unstable.

What would be good is a mechanism for Hydra to tell you “I tried to build this derivation, and it failed.” For this, Nix first needs to store build failure, and since store paths are input-addressed by default, you can also skip builds that will certainly still fail.

Btrbk if you use the right filesystem.

I have this iFixit guide as my source: https://www.ifixit.com/Guide/Choosing+the+Right+Screwdriver+Bit/93991#s176809 According to that, the JIS screws have orthogonal inner angles, while the Phillips’ are rounded, resulting in the slipping bits. However, some Phillips screwdrivers fill out that space, and thus won’t fully go into a JIS screw, and effectively be too small, stripping it.