Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spicetify/Backup should not reside in ~/.config | Or: following the XDG spec #3201

Open
rien333 opened this issue Oct 12, 2024 · 1 comment
Labels
🔴 custom app on hold The issue is on hold due to no detailed information

Comments

@rien333
Copy link

rien333 commented Oct 12, 2024

📝 Provide a description of the new feature

~/.config is meant for configuration files. I think anything that customizes spotify in any way should be stored here, as is mostly the case today.

There's a couple of exceptions, however: by default, spicetify stores Spotify backups in ~/.config/spicetify/Backup, and extracted files in ~/.config/spicetify/Extracted.

This is both conceptually wrong, and practically annoying. The current behavior is conceptually wrong because spotify backups/extractions are not configuration files. Looking at the XDG spec, $XDG_STATE_HOME (~/.local/state, by default) or $XDG_DATA_HOME (~/.local/share) are more appropiate places to store those. $XDG_STATE_HOME seems especially appropriate for Backups, because these backups are (previous) states of an application.

Moreover, spicetify's current behavior can be annoying from a more practical standpoint. Extracted/ contains tons of uninteresting, minimized .js files. These make recursively grepping for strings in ~/.config annoying (near impossible, actually, because a match from one of those files can easily fill 10000+ lines of scrollback, and they nearly always match). Moreover, people like to backup or VC their ~/.config. I think a lot of people would find including spotify backups and extractions completely undesirable in these contexts (spicetify/ is 5000x times larger than most directories in my ~/.config).

I know both of these practical issues can be worked around, but I think spicetify should do the right thing here, rather than to expect users to circumvent its arguably non-standard behavior.

Alternative proposals

As an alternative, the backups and extracted files could be saved as (compressed) archives. That way, their contents are ignored when performing searches, and they potentially take up less space. (my ~/.config/spicetify/Extracted compresses really well — >4 times smaller with zstd compression)

➕ Additional Information

No response

@rxri
Copy link
Member

rxri commented Nov 2, 2024

Spicetify v2 is in currently maintenance mode so your proposal won't be considered by me because I don't even have linux installation rn. Feel free to make a pull request changing it of course.

@rxri rxri added the on hold The issue is on hold due to no detailed information label Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔴 custom app on hold The issue is on hold due to no detailed information
Projects
None yet
Development

No branches or pull requests

2 participants