It could be a deepfake. A whole new class of conspiracy theory is now actually plausible.
I mean, I fully expect an administration as corrupt and dishonest as this one to spend the minimal time and money required to do such a thing for as long as they can get away with it.
Better yet, use borg to back up. Managing your own tars is a burden. Borg does duduplication, encryption, compression, and incrementals. It’s as easy to use as rsync but it’s a proper backup tool, rather than a syncing tool.
Not the only option, but it’s open source, and a lot of hosts support it directly. Also works great for local backups to external media. Check out Vorta if you want a GUI.
Android uses MTP as the transfer protocol. The Debian docs suggest Gigolo to mount devices with MTP. See: https://wiki.debian.org/mtp#XFCE
I’m on Bazzite now. It certainly made my life easier as far as GPU drivers go.
However, be aware that it comes with its own learning curve. It’s an “immutable” distro, and it has like half a dozen different ways to install software. You can’t use dnf like you would on regular Fedora. The idea is to get apps from Flatpak, or use Distrobox, or use Homebrew — all things that run on top of the base OS so you can use a monolithic “immutable” OS image. There are pros and cons to this approach.
Once I familiarized myself with Distrobox (BoxBuddy makes this a lot easier) and using Flatseal to grant Flatpak apps direct access to the folders they need to operate (like my music library on an external drive, in the case of my music player), it’s been pretty smooth sailing. But I do miss just being able to run sudo apt install <whatever>.
Well that sucks. You might be able to try “The Debian Way” mentioned here: https://help.ubuntu.com/community/Upgrades#The_Debian_way_of_upgrading
(Ubuntu is derived from Debian, which is why “the Debian way” works.)
The gist is to replace all instances of “noble” with “oracular” in your /etc/apt/sources.list file, then run some commands to do the distro upgrade.
Cool. I could well be wrong about the double-step requirement. It sure sounds that way, but the Upgrade Notes page is very old so maybe it’s easier now? Keep us posted!
On further investigation, it looks like you’d need to do an in-between upgrade to 24.10 before going to 25.04. I didn’t realize that before. It’s been a long time since I upgraded an Ubuntu system.
Here is the relevant documentation you’d need for upgrades:
From 24.04 to 24.10: https://help.ubuntu.com/community/OracularUpgrades/#Upgrading_Ubuntu_Desktops_to_24.10
And then basically the same thing again to go from 24.10 to 25.04: https://help.ubuntu.com/community/PluckyUpgrades#Upgrading_Ubuntu_Desktops_to_25.04
In case you’re not familiar with Ubuntu’s naming and update conventions, I’ll explain briefly, because it’s confusing for beginners: Each release has a name and number. The names loop through the alphabet in the format “Adjective Animal”, and the numbers are the release date in format “year.month”, with new releases every six months, in April and October. Then there are the “Long Term Support” (LTS) releases that are released every two years, matching the April “xx.04” main releases. You’re currently on “Noble Numbat” (24.04), which is followed by “Oracular Oriole” (24.10) and “Plucky Puffin” (25.04). Totally intuitive, right?! -_-
OR you could back up your stuff and install a clean 25.04. I’m not sure if the installer has an option to retain an existing home folder. Again, it’s been a long time since I used Ubuntu specifically. Perhaps someone with more recent experience can chime in.
You didn’t mention which version of Ubuntu Studio you’re running. Is it 24.04 LTS by any chance?
My initial thought is that you are probably running Wayland, and that your version of Ubuntu has KDE Plasma 5 instead of 6 and/or outdated Nvidia drivers that don’t work super well with Wayland.
A quick search shows that this is all default on Ubuntu Studio 24.04 LTS, which is the first version you’ll find at ubuntustudio.org. :(
Ubuntu 25.04 (non-LTS) has Plasma 6, which is a very important upgrade if you are using Wayland, especially with Nvidia GPUs.
Just a guess. If I’m right, you have a few choices:
Upgrade to Ubuntu Studio 25.04 (non-LTS). It has newer stuff like Plasma 6 that fixes a LOT of problems like this.
Switch to X11 instead of Wayland. This will likely introduce a new set of problems though. X11 has no future.
Switch to a different DE than KDE. I am not sure what is best in this situation.
Install the latest Nvidia drivers manually instead of getting them from the Ubuntu repo.
Option 1 is by far the simplest choice.
The Linux desktop is in a big transitional phase these past few years, as more distros default to Wayland even before a lot of their packages are updated to fully support it. It’s a terrible time to be stuck with outdated “LTS” distros. This is why I hopped away from Debian 12 (13 is out now so yay, but it was a year too late for me).
Oh wow, they already have a 2.0 prerelease build. That was fast!
I’m in no rush. 1.x has been doing its job without demanding any of my attention since I set it up a year or so ago. Setup was a bit complex, but it was definitely worth learning.
There are interesting and important points being raised here, but the particular programming language used is irrelevant. The author is only undermining himself by focusing so much energy on the tired old holy war between C and Rust proponents.
Seems like most mods work fine on Linux, but I’m sure it depends on the game. For games with built-in mod managers like Baldur’s Gate 3, it all just works. For games with manual mods that involve replacing or editing game files, they should generally work since you’re running the same game files to begin with.
I haven’t had any big compatibility problems recently, though again, I’m sure it depends on that game. Proton (built into Steam) works very very well nowadays.
Just a few years ago I found the experience frustrating. It seemed like everything had something wrong with it, even if it wasn’t big. Lots of games had glitchy input, whether using a controller or keyboard/mouse. But somewhere down the line it totally flipped, and everything I play runs great now. I still have a bootable Windows 10 system, but I haven’t actually booted it in…two years, maybe?
This must depend on country and carrier. My carrier has never removed 4G or 5G bands. They’ve added new ones and they’ve phased out 2G and some 3G but that’s all. My phones from 10 years ago can still connect just fine, although obviously newer ones are faster.
King Of Ink Land King Body Art The Extreme Ink-Ite has written to his local MP to air his grievances.
Holy shit. That’s his legal name?!
For King of Ink Land, this is particularly tricky as the system believes he’s wearing a mask – but it’s actually his tattoo-covered face.
So is it first name ‘King of Ink Land’, last name ‘King Body Art The Extreme Ink-Ite’? Or is there a middle name in there?
The King of Ink Land, who is now considering using a VPN, was attempting to access a live webcam site when the issue arose.
Whoa whoa whoa. “The” King of Ink Land? That’s his name, not a title!
Godspeed, King of Ink Land. I sincerely wish you success in this fight.
I’m telling myself it’s Irish coffee.
I mean that an individual folder will always look the same (consistent), and also look distinctly different from any other folder (unique) if that’s how you arranged it. So you could identify a folder instantly.
Everything in list view looks the same at a glance, and most file managers don’t retain a folder window’s size and placement. Modern macOS kiiiind of does but you have to fight it if you don’t want a single-window browsing UI.
The last time I found icon view useful was in Mac OS 9. There were three main characteristics that made it useful that no current systems have AFAIK:
The icon grid was tight (32 pixels) and you could either snap items to that grid or place them freely.
Window sizes and places were directly associated with folders. (There was no “browser-style” single-window mode.)
File names used dynamic spacing. Longer names would occupy multiple grid spaces as needed.
These factors meant that every folder had a consistent and potentially unique size, placment, and layout.
OS X took the Finder and either ruined or neglected everything good about it. Windows explorer has always been garbage. Never found a Linux file manager with a compelling icon view either (though to be fair, I’ve never looked all that hard). The lack of system-level metadata for layout kind of mandates an abstraction between a directory and its display.
Kind of funny how quickly we’ve flipped from “you should treat LLM output like advice from a random stranger” to “you should treat advice from a random stranger like LLM output”.
Either way, it’s the right idea. If you can’t understand what you’re doing but you do it anyway, you’re going to create all kinds of problems for yourself.
do they just want everything to be crawled
Yes. Web crawling has been a normal and vital part of the web from day 1. We’d have no search engines without crawlers.
The web is user-centric by design. I’m sick of tech companies trying to flip the script and hoard information, most of which is not theirs to begin with (e.g. Google, Reddit, Twitter, Facebook, etc.).
20 years ago I would have taken this as satire. Today, reality is far more absurd.
They clearly don’t understand what pride is about, or why it’s needed in the first place. I don’t go around showing my “straight pride” because there is literally nobody out there trying to make me ashamed of being straight. Never in my entire life have I felt unsafe because I was straight. I never had to worry about my family rejecting me if they learned I was straight. Being straight has never affected my housing security. I have not been subjected to verbal and physical assault because I am straight. Nobody has ever, to the best of my knowledge, been sent a brainwashing camp for being straight. There is not a single country on earth where it is illegal to be straight, and there never has been.
You cannot say any of those things about being gay. That’s why gay pride matters. These are not problems of the past. They are all problems today.
Generally speaking, xz provides higher compression.
None of these are well optimized for images. Depending on your image format, you might be better off leaving those files alone or converting them to a more modern format like JPEG-XL. Supposedly JPEG-XL can further compress JPEG files with no additional loss of quality, and it also has an efficient lossless mode.
As far as I know, no common compression algorithms feature built-in error correction, nor does
tar. This is something you can do with external tools, instead.For validation, you can save a hash of the compressed output. md5 is a bad hashing algorithm but it’s still generally fine (and widely used) for this purpose. SHA256 is much more robust if you are worried about dedicated malicious forgery, and not just random corruption.
Usually, you’d just put hash files alongside your archive files with appropriate names, so you can manually check them later. Note that this will not provide you with information about which parts of the archive are corrupt, only that it is corrupt.
For error correction, consider par2. Same idea: you give it a file, and it creates a secondary file that can be used alongside the original for error correction later.
That is a key advantage of this method. Adding a hash file or par file does not change the basic archive, so you don’t need any special tools to work with it.
You should also consider your file system and media. Some file systems offer built-in error correction. And some media types are less susceptible to corruption than others, either due to physical durability or to baked-in error correction.