I don’t understand the concern, domain names are cheap and easy to get, they can just keep using new ones. Why does it matter if they lose the ones they have?

Piratebay used to do the domain dance all the time back in the day (and maybe still do).

Most of the paid plugins I’ve messed with have code to phone home and prevent operation if there’s not a paid license of some sort.

However, before you bother trying to put effort into pirating those, I recommend making certain that what you want isn’t already freely available a different way. Many paid plugins have decent open source and free alternative plugin(s) that can be used instead. You just have to look hard enough in the plugin listing. The WordPress ecosystem is vast, but there are a ton of smarmy assholes charging monthly subscriptions for plugins that replicate features provided by free plugins and hoping you won’t notice.

I’m not trying to convince you to like something you don’t, and KDE is a fucking great suite of software.

However, it does sound like maybe you haven’t used GNOME in quite a long time. It does have various customizations built in that are available to users through the settings UI these days, and “tweaks that barely work” isn’t really a representative critique of the general ecosystem anymore.

GNOME’s extension platform is very mature at this point, and I’ve personally used a bunch of the same extensions for years now spanning like 10 major releases of GNOME without issue. Yeah, the little fly-by-night extensions that get two point releases and then are abandoned don’t work forever, but that’s true of a lot of old software, and is probably a good thing, honestly.

I tried the new version of the app (1.3.1) and it works a little better. As mentioned in my other comment, the app tries by default to write to my home directory, which fails. However, if I manually tell the app to use ~/Downloads instead, then it works!

On the other hand, closing and relaunching the app again clears out what I’ve manually configured and it tries to write to my home directory again until I change it every time.

(Also, apologies, I should be reporting to your issue tracker instead.)

Hey, sure no problem. I don’t actually have a Music folder ordinarily since I keep my music in a network location instead.

$ flatpak run --command=bash net.fhannenheim.musicfetch
[📦 net.fhannenheim.musicfetch ~]$ xdg-user-dir MUSIC
/home/luke

Flatseal shows that the app has requested permission to access xdg-music, which in my case is my home directory. I would assume that means it should be able to write there, but maybe the “All user files” toggle being off supercedes that? I’m not sure how flatpak permissions work, exactly.

Hey, thanks for the response! I tried again with the recent update (--version says 1.2.1) and still having the problem. The button you refer to opens my file manager in the system root directory, instead of the download directory shown in settings which is now by default set to my home folder instead of ~/Music like in the prior version.

To recreate, I ran the app from the CLI and searched the videos tab for “flowers”, then clicked download on the top result. The metadata pages had blank values (are they supposed to populate automatically somehow?), and I clicked through until I got to the final page below.

~$ flatpak run net.fhannenheim.musicfetch --version
musicfetch_gui 1.2.1
~$ flatpak run net.fhannenheim.musicfetch
libEGL warning: failed to get driver name for fd -1

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd -1

MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
libEGL warning: failed to get driver name for fd -1

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd -1

MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
[2026-01-28T19:22:43Z INFO  musicfetch_gui::app] Starting download of 1 songs
[2026-01-28T19:22:43Z INFO  musicfetch_gui::modules::download] running yt-dlp with args ["--ignore-config", "-x", "-f", "ba", "-o", "/tmp/musicfetch/%(id)s.%(ext)s", "--load-info-json", "-", "-O", "after_move:filepath", "--progress-template", "download:%(progress.downloaded_bytes)s-%(progress.total_bytes)s-%(progress.downloaded_bytes_estimate)s", "--newline", "--progress"]
[2026-01-28T19:22:44Z INFO  musicfetch_gui::modules::download] All songs downloaded
[2026-01-28T19:22:52Z INFO  musicfetch_gui::modules::tagwriter] reading filetype from path /tmp/musicfetch/G7KNmW9a75Y.opus
[2026-01-28T19:22:52Z INFO  musicfetch_gui::modules::tagwriter] filepath extension: Some("opus")
[2026-01-28T19:22:52Z INFO  musicfetch_gui::modules::rename] moving song to: //1 - .opus
[2026-01-28T19:22:52Z INFO  musicfetch_gui::modules::rename] creating parent dir: /

PS: I tried again with another song (Big Boogie - Shut Up) that seems to have metadata available from however MusicFetch is finding metadata. The logs are slightly different in that it seems to attempt to save the file where it is configured to do so (the home folder), but there’s still not actually a file saved in that location when I click to open in my file manager:

$ flatpak run net.fhannenheim.musicfetch
libEGL warning: failed to get driver name for fd -1

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd -1

MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
libEGL warning: failed to get driver name for fd -1

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd -1

MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
[2026-01-28T19:31:10Z INFO  musicfetch_gui::app] Starting download of 1 songs
[2026-01-28T19:31:10Z INFO  musicfetch_gui::modules::download] running yt-dlp with args ["--ignore-config", "-x", "-f", "ba", "-o", "/tmp/musicfetch/%(id)s.%(ext)s", "--load-info-json", "-", "-O", "after_move:filepath", "--progress-template", "download:%(progress.downloaded_bytes)s-%(progress.total_bytes)s-%(progress.downloaded_bytes_estimate)s", "--newline", "--progress"]
[2026-01-28T19:31:11Z INFO  musicfetch_gui::modules::download] All songs downloaded
[2026-01-28T19:31:17Z INFO  musicfetch_gui::modules::tagwriter] reading filetype from path /tmp/musicfetch/B9RNRhoUr6E.opus
[2026-01-28T19:31:17Z INFO  musicfetch_gui::modules::tagwriter] filepath extension: Some("opus")
[2026-01-28T19:31:17Z INFO  musicfetch_gui::modules::rename] moving song to: /home/luke
    /Big Boogie/Shut Up/1 - Shut Up.opus
[2026-01-28T19:31:17Z INFO  musicfetch_gui::modules::rename] creating parent dir: /home/luke
    /Big Boogie/Shut Up
[2026-01-28T19:31:23Z INFO  musicfetch_gui::app::update] Opening directory at /home/luke
    /Big Boogie/Shut Up

Edit: forgot to mention, I’m using Fedora Workstation 43, in case that’s relevant for you.

Good luck with the app, it’s a really good idea!

I had similar problems where the logs say it moved the file to my Music directory, but the directory was empty. I made multiple attempts using different directories and making sure the app has permissions with flatseal, but no luck.

It seems like a nice app though, I’m gonna keep an eye on it!

This is a good idea, except that it requires money. I already have an old Pixel right here that I can put Graphene on.

I guess my point is, it’s not necessary to harass people about their choice of phone OS before you know their situation. 🤷