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.

You’re a kid now 🎶

They can, yes. You’ll need an experienced psychologist to diagnose that, probably. At least it’s not me, too insecure to answer honestly, instead thinking about the “socially correct” answer, because mine would be either too telling or a cringe reference.

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!

Ahh, I found you, Toby Fox!

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 🤷

I’d call the furniture in a train restaurant furniture. There’s tables, lamps …

That’s something to figure out with your instance specifically, maybe it has a meta-community? On Reddit, that process goes through r/redditrequest, maybe you have a c/lemmyrequest?

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.

Gibt es hier irgendwo !nichttoteöffnendrinnen?

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.

JIS is only good for being cheap, and only works if you’re a precision robot. You lose the autocentering and overtorque protection of Phillips, without gaining any of the advantages of Torx. (Phillips has overtorque protection in the sense that your tool doesn’t break, the screw does; which doesn’t matter if you don’t need to unscrew it.)