The docs drifted behind three changes: the /queues + /bookmarks +
/captures split folding into one /crabidy provider, three providers
arriving (soundcloud, jamendo, abs) with nothing written about them, and
the spectrum toggle moving off v to f when library visual mode took v/V.
- The book gains a page per undocumented provider — /soundcloud,
/jamendo, /abs — each with its tree, its playback path, every config
option, and how to log in. The providers index and intro list all nine
roots in the order the server actually serves them.
- Every provider now documents its login: Tidal's device flow (and that
a broken tidaly.toml is the one fatal provider config), audiobookshelf
API keys, the optional SoundCloud token and where to read it out of a
browser, YouTube cookie exports, Jamendo's shipped key, and "nothing
to do" for fyyd and /fs.
- fsdy's README described three server-managed mounts under
~/.config/crabidy that have not existed for a while; it now describes
/crabidy over the state dir plus the shared content store, and how
deletes there never touch store audio.
- Stale /captures/<name> save paths in the tidaldy and ytdy READMEs are
/crabidy/<name>. The TUI key table, the README walkthrough, and the
spectrum section use f, and visual mode (v/V) is documented.
- config.md and the README list all seven provider config files, say
plainly that credentials are stored in cleartext, and cover the audio
output device; the CLI page documents audio-devices and features.
- No README or docs page references architecture/, quality/, or plan/
any more: the book describes the system as it is, and points at the
crate READMEs for usage and config.
- devenv-docs.nix was never committed even though devenv.nix imports it,
so a fresh clone could not enter the shell at all. It is in now, which
also makes the README's `devenv shell -- docs` work.
Also fixes two ./store.md links in providers/fs.md that pointed one
directory too shallow.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The app key identifies the application, not a user, so there is no reason
to make everyone register one before they can play anything. An unset (or
blank) client_id now falls back to DEFAULT_CLIENT_ID, and init writes
whichever key is in force back into jamendo.toml, so the effective value
is always visible and replaceable.
Jamendo rate-limits per key, which the docs say plainly: a shipped
default is a shared budget, and a heavy user should register their own.
A configured key always wins.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The mp32 audioformat is not reliably provisioned for the streaming
audio URL — Jamendo returns an empty audio field for many tracks — so
mp32 as the default made playback fail with track is not streamable
even though metadata resolved. Default to mp31 (the freely streamable
MP3), and have track_stream retry without a forced format when the
configured one yields no audio, so a Pro-only format degrades to a
playable stream instead of skipping the track. Live-verified: default
config resolves a stream URL, and an explicit mp32 now falls back.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Jamendo API v3.0 answers HTTP 200 success with an empty result set to
any request that carries no User-Agent header. reqwest sends none by
default, so every search/detail/stream call came back empty and tracks
would not resolve or play (jamendo resource not found). Set a UA on the
JamApi client, like the SoundCloud provider does. Live-verified against
the API: search, track detail, and stream-URL resolution all return data
with the header present.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
New jamendody crate implementing ProviderClient, mounted at /jamendo:
search the Jamendo catalogue and play tracks, browse an album a track
belongs to, with captures/downloads for free.
Unlike the SoundCloud provider this is the simple case — Jamendo has a
stable official API (api.jamendo.com/v3.0), so there is no client_id
scraping, no OAuth, and no HLS: a track streams via its direct audio MP3
URL on the existing windowed-HTTP path, and duration is already in
seconds (matching Track.duration). A registered client_id in jamendo.toml
is required; missing it disables /jamendo only, non-fatally.
Ran the full dev-flow pipeline; artifacts under architecture/, quality/,
and plan/. 16 jamendody unit tests over a faked Jam network seam; server
wired with the standard owns/provider/build/dispatch pattern and a
jamendo toggle in ALL_PROVIDERS.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Test User