Rudy didn't give a fuck. He wanted an excuse for cops to arrest and menace the underclasses and he got it. The cops loved him for it.

If you go back to 2012, Vice Presidential pick Paul Ryan listed RATM as his favorite band. At least the MAGA people are raging against something and they think it's the machine, but Paul Ryan was a technocratic dweeb who probably would've gotten shoved in a locker in high school if his dad wasn't rich. Paul Ryan was supposed to be smart, too, but i guess whether you're smart or not doesn't matter if you live in a fantasy world. You're doing to make a fool of yourself either way.

All the PPA maintainers went to Arch.

I think you already got a good answer but let me throw in another:

Fedora's dnf provides some good history and update reversion tools. You can use:

dnf history list

to get a list of all actions taken on the system since install. Use "dnf history info 5" to get info on the 5th transaction. (Get the transaction ID numbers from "dnf history list".)

Then to revert a change use either:

dnf history rollback or dnf history undo

Using undo reverses a single transaction, so if you have one where you did something like "dnf install tmux" and then ran undo on it then that would be equivalent to running "dnf remove tmux" in terms of what it does on your system.

Rollback does what you might think: it basically goes through all the updates between the most recent and the one specified and it reverses each of them, theoretically restoring the system to the state it was in at that time.

I say "theoretically" because this isn't a perfect system. For example, if you have an update where you removed some software that had some customizations done to it and then went through a rollback it'll put that software back but may be missing configurations you applied to it, so potentially it could cause some issues if those were important. This gets into a lot of complicated stuff and tbh it is a powerful but imperfect system. Something like Atomic gives you more of a guarantee that a rollback will work because the whole system state is defined by the installer, not just the packages.

There's one more note: Fedora removes old versions of packages from its repos so you'll need to add their historical archives repo to do certain things. I forget how to do that off the top of my head.

This may not be what you want exactly but it's a powerful tool that's good to be aware of.

See this for more info.

dnf remove @gnome-desktop dnf autoremove

For the curious.

Note that the autoremove might not do anything here. Removing @gnome-desktop removes the whole package group and should get everything in it.

I imagine something like Fedora with an RT kernel and CPU partitioning could be as reliable as an old Amiga. CPU partitioning would let you reserve one or more cores for specific applications such as music production software. Now, the software in question may not be up to the task but that's a different problem.

I mean they may own five hundred guns each but i feel like only the first couple of them actually matter. The rest are just for masturbation purposes.

They used to be good, almost as good as the Windows drivers. Lately, though, they've been kinda trash and the AMD open driver is pretty alright now. (Performance isn't as good but other than that it's good.)

Doesn't KDE basically have color management with 6 or 6.1 or something?

Ubuntu previously was excepting Gnome point releases from major testing on the grounds that Gnome's point releases are all big fixes and thus don't require Ubuntu's major testing process. Gnome shipped a new major feature in a point release and so Ubuntu said "oops, guess we gotta test their point releases after all". Practically, it means Gnome point releases take longer to get into Ubuntu than they previously did (but are more tested for bugs).

Yeah, even if zero people ever consented the ability to defeat end to end exception would still be required in the software just in case someone ever did consent. That's all governments need to bring their other powers down on companies. They can spy on whoever they like with this.

There's a real opportunity here and we can either take it and run or we can let it pass us by.

They're definitely going to back down. I'm guessing they're going to back down a little (maybe create an opt out for the enterprise customers?) and then claim victory, but we'll see.

You should really be using a pre commit hook to catch secrets. Admittedly it may not have caught this, but manual review is (clearly) not always sufficient.

Basically what it's doing is booting to an alternate OS configuration to do the install. It's way easier to just reboot again rather than tear down the installer environment and go into a normal one. That's basically a reboot in all but name. It's annoying to have to enter your encryption passphrase twice, though.

I feel like a lot of Linux behaviors tell me most Linux people don't encrypt their data, which tbh should not only be the default but should be difficult to opt out of. Apple actually does this one right. Encryption is just the way it works.

Pretty sure you can configure "open as root" in some file managers. Also you can configure a gksudo (or similar) setup.

Really though, that makes me think. The file manager should detect you're opening something you don't have write access to and ask if you want to authenticate as root to open it.

Yeah, car thieves are famously very particular about laws relating to cars.

...Wait a minute... No, it's the opposite of that.

This one's true though.

It's not just today, even his contemporaries kinda sucked and mostly didn't like him.

Here's a Smithsonian article: https://www.smithsonianmag.com/smart-news/dna-analysis-reveals-vikings-surprising-genetic-diversity-180975865/

Here's a different one, from... i dunno the site but this roughly reflects my understanding: https://scandinaviafacts.com/were-the-vikings-black/

I think generic testing is pretty suspect but at the same time we have more than just that to suggest this.

Remember, also, that the Vikings (like other people of their era) didn't have an understanding of race in the sense we do today. Surely they had some concept of people having different skin color (they traveled enough) and of family lineage but the pseudoscientific idea of race theory has yet to be invented.

Anyway we can be pretty confident Viking slaves (thralls) were sometimes non-white and we know thralls could buy their freedom and free people could take up viking (the profession) so it stands to reason that there could be some. That plus old burial sites suggest that wasn't just a theory but something that happened. i suspect the culture at the time was even more heterogenous than we would think just from that, though it seems like the white skinned types were still the majority considering modern Scandinavians.