No, but thinking about whether it’s conscious is an independent thing.

our homeland security guy gets her security breached in DC, our heartland. included are blank checks and her IDs (including government clearance), and what she’s focused on getting back is her money information.

DHS Sec.'s salary alone makes $3.3k a week.

job market is packed enough

I would not compare Hamas to ISIS or al-Qaeda at all. For starters, they don’t want a caliphate and don’t do jihad. (Or at least did jihad very very long ago. Fun fact: the biggest part of Israel’s current ruling party used to kill IDF soldiers.)

Hmm, what do you see in it?

What’s oniony about this?

Yeah, and you have to pay for that. Lots of open source software have enterprise support and usage limit licenses but having to pay for something isn’t open source. I am personally ambivalent at non-commercial licenses but I agree that the restriction against using proprietary software with Redis in commercial usage is kinda bad.

Valkey was created recently as Redis changed their license, having clauses which made the user choose between being “discriminatory against users of the software that use proprietary software within their stack, as the license requires the open-sourcing of every part interacting with the service, which under these circumstances might not be possible” or being non-commercial. Forgejo was created when Gitea decided to go the JetBrains route a few years ago. It’s since absorbed Gitea’s clout.

Good thing there are community frontends.

If you want to run post-upgrade, you got to do it yourself.

That’s just wrong. Pacman has hooks, and easy hooks are one of the reasons Pacman is loved. In a normal weekly upgrade I see Pacman run over 30 hooks. I do not think simply not updating user-modified config files is just the bare minimum needed.

I think this boils down to Arch’s philosophy: the users should know their system, and when something could break things, don’t assume things and do it automatically; have the user do it instead. Thus when shipping config updates to a user who had already changed their config, Arch does not overwrite the configs and instead ships the updated vanilla config with a .pacnew suffix. The user is expected to review such pacnews, a process that’s just like normal git merge conflicts when you use the pacdiff tool.

I agree that this article doesn’t really onion. There’s definitely a potential spin to make this oniony, though: “Government eats cake as doctors urge it to combat Victorian diseases–inducing living situations”

That’s just the funding part. There’s so many more components to renovation like design and construction, and without utilizing Amtrak there’s absolutely no legal avenue for them to take over the renovation of “private” property of Amtrak’s. The article even mentions a draft executive order detailing a design.

to be fair, it mentions “average human” is just a single sample

TOTAL QUANTUM FORENSIC LEGAL DOCUMENTATION ABSOLUTE TOTAL ULTIMATE BEYOND INFINITY APOCALYPSE

Agreed. The normal pacman CLI does have a comparatively much higher learning curve though compared to e.g. APT. It’s not that hard to learn either but when you’re scrolling over a long-ass manpage, you do not immediately realize from the headers which whizz by in a flash that -S (alias for --sync) is for installing from repos, -Ss is for searching from repos, -S does not by itself “synchronize” with repos by pulling newest repo package metadata because well that’s not what we’re “synchronize”-ing with and you have to add the “y” flag, -Su (remember to add “y”!) is for upgrading all packages instead of -U (alias for --upgrade), and -U is for installing a local package. Compare that to the APT/dpkg system’s apt install, apt search, apt update, apt upgrade, and dpkg -i.

Admittedly APT does need one to get behind the fact that there are different commands and that “update” and “upgrade” are different, but that’s way less to remember (especially since apt is meant to be the interface for everything a user should do) compared to remembering pacman’s interesting definitions of database, query, sync, upgrade, and maybe files, while the only definition unlikely to be guessed with APT IIRC is update vs upgrade. You’re far more likely to need a pacman cheatsheet than an apt cheatsheet.

But in the end, let’s all love libalpm, and the actual code behind that pacman interface.

Redis is also on the list, but not Valkey. Gitea is on the list, but not Forgejo. Still nice to see governments endorsing the open-source-ish software they know and FOSS principles, though!

Yes, promotion and awareness of a service is necessary for its continuation. I’ve agreed with that. But again, without the technological resources and money, there is no service to promote and nothing to continue because it hadn’t even started.

That’s not contradictory. Most would rather offload hardware and security costs, running one’s own hardware is time intensive nevermind power and equipment costs, and you can indeed add advertising and awareness costs to that list. But you do also need the resource investments for a service to start with before advertising it.

extra 4% tariff on aliased packages