I have KDE Plasma, Hyprland, and Mango (WM) installed.

Of the three, I use Mango most of the time, and KDE Plasma sometimes. Hyprland, I've kept because most of my config was for it, and I'm still currently porting them to Mango. Most of the dotfiles are in their own areas, though I've mostly piggybacked on Plasma components. One area that I've got some trouble with is program theming. KDE Plasma has its own, Qt has its own (which is different from the KDE Plasma one), and GTK is yet another. I've decided that the best way to deal with it is to make them look as similar as I can, so that whether I'm on Mango, Hyprland, or KDE Plasma, my programs will look the same--except for the presence of window titlebars, which Mango doesn't show, Hyprland shows via a plugin, but KDE Plasma does show.

I used Ubuntu's implementation of Gnome back when I started dabbling with Linux some time ago. I didn't bother theming it. And then I moved to XFCE when that underpowered machine I was using couldn't handle Ubuntu's Gnome without feeling like it's swimming in molasses. XFCE is nice and configurable in contrast, and I didn't have much to complain about. However, I found its configuration back then to be quite troublesome, especially as I tried tweaking my own bars and panels.

I then moved to KDE Plasma when I got my current machine. It was pretty okay out of the box, but coming from a tweaked XFCE, I couldn't stop myself from theming it to my liking. Hyprland was introduced to me mid-2024, and I was thrust head-first into configuring it from scratch, no dotfiles to copy from, or pre-made shells to make my experience easier.

At present, Mango won me over by having a decent vertical scrolling layout, as well as the flexibilty of using other layouts on the fly. While I like Hyprland's level of polish and customizability, and recently have implemented scrolling (both vertical and horizontal), I am staying with Mango if only because I've already done the work porting most of my stuff there.

Or maybe just put Arch in that Ventoy USB. (Yeah, yeah, I use Arch, btw.)

I've had one of those (battery died, unfortunately) and if you'd look at its files, you'd notice that they are organized in a different structure than what an MP3 player might expect.

iPod_Control\Music's sudirectories might contain some songs, but the filenames are hashes (corresponding to the entry in the iPod db). The metadata and the contents are perfectly fine, and you can play the file yourself via a different player (you can probably test it in your computer).

I suggest you just connect the iPod through the 3.5mm output audio jack or find a 3.5mm audio output to Bluetooth transmitter adapter.

---

EDIT:

WTF. I triple posted. My bad. I deleted the two others, also corrected some minor typos and mistakes.

It takes a lot of work and adjustment if you're new to tiling window managers. It takes time (and some skill, but that can be built over time).

I only got to know this because of an XKCD comic.

The Arch Wiki (and possibly other Arch websites, but when I checked I wasn't able to catch it) uses Anubis (https://anubis.techaro.lol/) to mitigate AI crawlers causing issues on their servers. Anubis works by making your computer do some computations before being let in. For users like you and me, it'd be a minor inconvenience, but for these AI crawlers, it'd cost them a lot of computation as they hit these sites a huge number of times.

Using Anubis is said to be a nuclear option, but as these AI crawlers don't care about that, sites, especially FOSS ones, started using it.