Formatting?

Gotta find out if it’s copyrighted, you know?

I’d say yes, but, you don’t have a right to appropriate someone else’s art as your own.

By all means, copy and distribute. Even modify and make derivatives. But no plagiarism, please. Don’t take something that someone else made and then claim to have made it yourself without giving them due credit.

Can’t sign in to xitter. Username already taken.

Oops, you missed the cave and now you’ve just invented Middle Earth’s fastest possible way to return the Ring to Sauron.

And they will be right to do so. The Dems are fully complicit in enabling this.

Honestly, I think Kubuntu is slept on as a beginner’s distro.

Yes, Ubuntu has its issues … but those sorts of issues are really not going to affect a newbie much. And it’s stable, easy to use, KDE defaults will be pretty familiar-feeling for Windows refugees, and it should be relatively easy to find help – 90% of the time, if you just type “how do I _____ in Linux?” into Google Duck Duck Go, the results you find will be perfectly applicable to Ubuntu. Want to install 3rd party software that’s not in their repos? In pretty much any software that offers a Linux version, the Ubuntu-compatible install method is the first one they list.

(Oh, and the installer is literally one click if you just let it do everything in automatic mode. No keyboard needed. The install image boots into a full GUI installer with mouse support, and if you want, all you have to do is click ‘automatic install’ and wait. Once it’s done and reboots, you’re in your new OS.)

Once you become an advanced enough user that you get annoyed by Snap packages or feel like you need more cutting-edge package updates … well, then you should also be advanced enough to do your own distro-hopping.

That’s the tricky part, innit?

A few good options:

A) Set up your backup/restore procedures immediately after setting up your fresh new system. And then immediately test them to see if you can successfully restore, before you’ve done anything important on the new system that you can’t afford to lose. If the restoration completely fails, no biggie. You just have to start over on setting up your fresh new system.

B) Attempt to restore your backup to a different system, not your primary one. You’ll need a second set of hardware to do that, but if you’ve got the hardware lying around, it’s a great way to test your restore procedure. If you’re upgrading your hardware anyway, it could be a good time to do this test – use your backup restoration procedure to move your data to the new hardware. (As an extra bonus, this doesn’t require any downtime on the primary system.)

C) Simulate a complete hard drive failure and replacement by replacing your primary system’s drive(s) with a blank new one. If the backup restoration fails, you should (fingers crossed) be able to just plug the old hard drive back in and everything will go back to how it was before your test.

D) Have multiple backups and multiple restore plans, and just hope to fuck that at least one of them actually works during your testing.

Option A can only be done if you’re proactive about it and do it at the right time.

Options B and C require extra hardware, but are probably the best choice if you have the hardware or can afford it.

And Option D will always have at least a tiny amount of risk associated with it.

Do you know how to transfer the files back if your OS has completely failed?

Verifying the files are there in your backup is only, like 10% of verifying that it’s a real, usable backup.

The important question is: can you successfully restore those files from the backup? Can you successfully put them back where they’re supposed to be after losing your primary copy?

Not really. Along most major roads, if trees are close enough to even potentially be a problem, they will be trimmed by road crews.

It’s not because they get hit by trucks, it’s because they’re deliberately trimmed back to keep the road clear.

Really hard to build an empire without it.

Because to have an empire, you have to rule over a lot of people. Many of those people would rather not be ruled by you. If you want to force them to accept it anyway, you’re going to need some of that genocide, slavery, and especially bloodshed.

Though, I suppose, maybe 2/3 of those aren’t really necessary.

• Genocide probably isn’t absolutely necessary to empire-building. Definitely still have to kill lots of people, but there’s no particular reason you need to do so on the basis of race or ethnicity. (Though if you count cultural genocide as well, that may very well be necessary to build an empire. Difficult to bring diverse peoples under one banner without suppressing their cultural differences.)

• Slavery is a big probably. It certainly does help – after all, your growing empire will need lots of labor, and it’s unlikely you can afford to pay the going market rate for it. Plus, if you don’t use slavery, you’ll probably be out-competed by other potential empires that are using slavery and/or slavery-adjacent labor practices. But I suppose it’s not technically absolutely necessary. Theoretically, at least, you could build an empire without slavery.

Ideally, you’d also first talk to the developers in charge of the project to see if your changes would be wanted in the first place.

(Or you’d start by reviewing existing bug reports and feature requests and addressing one of those.)

What I mean is, it’s generally better to not just throw code at them and hope they’ll like it. If you check first to see if they want it, you can save yourself from wasting effort on writing code that they’ll decline.

This is what you get when you have your manuscript illustrated by cloistered monks who aren’t allowed to go outside and see what a real horse looks like.