rope/nixos
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

spotify-player: drop custom client_id, restricted quota 404s search

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
rope 2026-08-15 21:55:46 +01:00
parent 2a64c712a6
commit d6725f4d6d
1 changed files with 5 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

12
home-manager/fred.nix
View file

@ -92,13 +92,11 @@ in
}); });
settings = { settings = {
enable_audio_visualization = true; enable_audio_visualization = true;
# Our own Spotify app rather than the built-in default (ncspot's client # No `client_id` on purpose: the bundled default (ncspot's) has extended
# ID, shared by every spotify-player/ncspot install). Spotify rate-limits # quota mode and predates the 2024-11-27 Web API changes. Our own app is
# per client ID, and exhausting the shared one surfaced here as # newer, so it sits in the restricted quota and 404s on search, browse
# "Token is not valid" and an endlessly loading library. Public PKCE # categories and Made-For-You — upstream issues #617 / #890. Sharing the
# client, no secret involved, so it's fine in the repo. # default ID does not cost us rate limit here; upstream recommends it.
# Redirect URI registered: http://127.0.0.1:8989/login
client_id = "265506bc7bbd4032bf0fee708b321d3e";
}; };
# The home-manager module only writes keymap.toml when `keymaps` is # The home-manager module only writes keymap.toml when `keymaps` is
# non-empty, so `actions` alone would silently emit nothing. Restating a # non-empty, so `actions` alone would silently emit nothing. Restating a