Here's my problem with #ArchLinux: it seems to greatly prioritize "feeling super cool h4x0rm4n" over actually being useful.

Take package updates for example. If it's been a while, it will almost certainly tell you for every package you're trying to update:

> [Package file] is corrupted (invalid or corrupted package (PGP signature)).

Oh shit! Corrupted file! MITM! Hax!

Lol no. Nowhere, *anywhere*, does it tell you what the actual (trivial) problem is, or how to fix it.

#flamebait but true :P

Here is a useful error message:

----
The signing keys have expired. You can update them via

sudo pacman -S archlinux-keyring
sudo pacman-key --refresh-keys
----

Or, better yet, don't have an error at all and just *do this automatically*.

But if it did that, you wouldn't be able to feel super cool key-jockeying your crypto shit, and if you don't intrinsically know this then maybe you're just too dumb to Arch.

This attitude seems to be pervasive across the entire operating system.

I may be irritated at my computer today.

Then again I'm irritated by almost every computer almost every day, so 🤷

@ojensen Agree with your assessment of Archlinux. They make me feel too dumb to Arch, and it's just silly gate-keeping!
@ojensen archlinux makes you cool!
@ojensen that's my primary gripe with pacman, sometimes keys are out of date and you need to update your archlinux-keyring. not really intuitive unless you stare at the ArchWiki for a miment, which let's face it, most new users aren't going to do