spicetify/Backup
should not reside in ~/.config
| Or: following the XDG spec
#3201
Labels
spicetify/Backup
should not reside in ~/.config
| Or: following the XDG spec
#3201
📝 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 forBackups
, 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
The text was updated successfully, but these errors were encountered: