Elezea — releases

discogs-mcp v3.6.0 — Self-hosting on the Workers Free plan

Rian van der Merwe — Wed, 07 Oct 2026 13:26:03 GMT

This release is mostly for people who run their own copy of discogs-mcp. The one-click deploy works on the Workers Free plan again, and a large collection now finishes syncing there. Login links and status messages also make more sense on a self-hosted server.

Breaking changes

If you self-host, an MCP client that signed in by naming your /mcp URL as its OAuth resource will have to sign in once more after you upgrade. Clients that used your bare domain, which is what the server advertised, stay signed in.

What's new

get_cache_stats shows how far your collection sync has got: how many items the snapshot holds, when it was fetched, and which page a sync in progress is on (page N of M).

Fixes

The Deploy to Cloudflare button failed at its first step on the Workers Free plan. It works again.
Collection sync on the Workers Free plan used to stall partway through a large collection, because each page it saved cost more CPU time than the last. Each page now costs the same, so a big collection finishes over a few scheduled runs. One self-hoster's 4,157-release collection synced completely this way. Searching a collection that size can still run out of CPU time on the Free plan, and the README's sizing note says where the line is (roughly 2,000 releases).
The login links in auth_status, server_info, and every tool's "please sign in" message pointed at discogs-mcp.com, which is a private instance. They now point at your own deployment.
auth_status showed a session expiry date of January 1, 1970. It shows the real date now, or leaves the line out when the server doesn't know it.
When refresh_collection fails, it tells you why. If Discogs is rate limiting you, that includes how long to wait.
A sign-in link with something missing (no client ID, say) gets a plain error message and never reaches Discogs.
get_collection_stats labels decades as "2010s" and not "2010ss".

Under the hood

Upgraded the OAuth library (@cloudflare/workers-oauth-provider) from 0.3 to 1.2. Existing sign-ins keep working, and it's the base for a consent screen in a later release.
Tools and prompts register through registerTool() and registerPrompt(), the only registration methods in version 2 of the MCP SDK.
The test suite runs on Vitest 4 and Node 22.
Removed an unused entry point and JWT module.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

lastfm-mcp v2.6.0 — Sign-in without client registration

Rian van der Merwe — Mon, 05 Oct 2026 16:04:29 GMT

MCP clients can now sign in by pointing at a web address that describes them, with no registration step first. This is the method the current MCP spec prefers, and existing connections keep working as before. All five changes behind it came from Jonathan Hitchcock, the project's first outside contributor.

What's new

Sign-in with Client ID Metadata Documents. A client can use an HTTPS URL as its ID, and the server reads the client's name and allowed redirect addresses from the document at that URL. Some clients support nothing else. The documents Claude Code and VS Code publish are accepted as they are.
If a client's document can't be fetched or doesn't validate, sign-in stops with a plain Invalid client_id error.
Dynamic client registration is still on, so clients that rely on it are unaffected and nobody needs to sign in again.
The landing page at lastfm-mcp.com has current setup steps for Claude, two more example questions, and a link to the privacy policy.

Fixes

server_info, the discovery card, and /health report the real server version. They said 1.0.0 before.

Under the hood

Four indirect dependencies (fast-uri, hono, ip-address, qs) moved to patched versions after new security advisories. None of them ship in the deployed Worker, and npm audit on production dependencies is back to zero.
Wrangler is pinned to 4.124.0, the version the test runner uses, so local dev, deploys, and tests share one runtime. Dev and deploys had been on a Wrangler more than a year older.
CI fails on unformatted code, after a one-time cleanup of files that had drifted.
The suite is at 183 tests, up from 174. The new ones include full sign-in round trips using the document shapes Claude Code and VS Code publish.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

Discrobble v1.3.6 — Your Discogs notes on the album page

Rian van der Merwe — Fri, 28 Aug 2026 19:10:44 GMT

Discrobble now shows the Notes you keep against a record in your Discogs collection, and lets you edit them from the album page. This release also collects everything shipped since 1.3.1: marketplace prices, the full Wikipedia intro, cleaner artist names, and compilations that scrobble properly.

What's new

Album pages show the Notes from your Discogs collection, and you can edit and save them without leaving the app. Turn it on with "Show collection notes" in Settings. If you own two copies of a release, the notes come from the first one, with a "1 of N copies" caption so you know which.
The album page can also show what a record is going for: how many copies are for sale on the Discogs Marketplace, the lowest asking price, and a link through to the listings. There's a Settings toggle for that one too.
The Wikipedia section gives you the full introduction now, paragraph breaks and all, where it used to stop after a sentence or two.
Settings has a small ask at the bottom: a link that opens the App Store review sheet, if you feel like leaving a rating.

Fixes

Discogs disambiguation numbers are gone from artist names, so "Nirvana (2)" displays and scrobbles as "Nirvana". Albums already in your library get cleaned up once, on launch.
Compilations whose tracks carry no artist of their own now scrobble under the performer credited on the release. Last.fm quietly drops anything filed under "Various", so those plays used to disappear without a word.
When a scrobble does fail, the app tells you why.
If your Discogs collection is set to private, sync now says so and points at the privacy setting to change. It used to fail with "Sync interrupted after 5 attempts" and no explanation.
Fixed a crash that could hit when an album left your collection while you had the grid or that album's page open.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

lastfm-mcp v2.5.0 — Latest MCP protocol support

Rian van der Merwe — Tue, 25 Aug 2026 00:04:31 GMT

The server now speaks the current MCP revision (2026-07-28, the stateless one) natively, while older clients keep working through the SDK's compatibility lane. Tool responses also got smarter about what to call next, and two long-standing crash bugs in the public catalog tools are gone.

Breaking changes

The Mcp-Session-Id header is no longer read or echoed, since the 2026-07-28 spec removed protocol sessions. If you connected through the manual /login flow, pass ?session_id= on the /mcp URL, which was always the documented way. Nothing changes for OAuth clients such as Claude.ai, Claude Code, or Claude Desktop.

What's new

MCP 2026-07-28 support: server/discover, the _meta request envelope, and the MCP-Protocol-Version, Mcp-Method, and Mcp-Name headers. Clients on the 2024 and 2025 revisions still connect with initialize and get the same tools.
Every tool response ends with a "Next steps" block listing the most likely follow-up calls with their exact arguments. Where the response has a clear top item (your top artist this month, the most recent week in a chart list), the first suggestion is filled in with it. The server also ships instructions naming the recommended tool path per entity, so a model lands on the right verb without reading all 21 descriptions.
Numeric parameters (limit, page, from, to) accept strings, because some clients send numbers that way. The same bounds still apply.
Resource templates advertise a description and MIME type.
/mcp is rate limited per IP at 60 requests a minute to protect the shared Last.fm API budget. That is well above what any interactive client does.

Fixes

get_album_info, get_track_info, and get_artist_info no longer throw for an album, track, or artist with exactly one tag, one track, or one similar artist, or with none at all. Last.fm sends those as a bare object or leaves the key out; the tools handle all three shapes now. This was producing a few dozen errors a week in production.
A failed Last.fm fetch raised a second, unhandled rejection alongside the error the caller already received.
The discovery card and server_info reported protocol 2024-11-05. Both now report 2026-07-28.

Under the hood

@modelcontextprotocol/server 2.0 and @modelcontextprotocol/client 2.0 replace the v1 SDK, with Cloudflare Agents SDK 0.21 (createMcpHandler from agents/mcp/server) and @cloudflare/workers-oauth-provider 0.10. npm audit on production dependencies reports zero vulnerabilities, down from 14.
All tool, prompt, and resource registrations use the register* APIs with z.object() schemas.
Two OAuth workarounds for Claude.ai's RFC 8707 resource parameter are gone; the provider handles it correctly now.
Test stack is vitest 4, @cloudflare/vitest-pool-workers 0.22, and Node 22. CI runs the suite again (174 tests) after a long stretch with that step disabled. New tests drive a real SDK client through the Worker on both protocol lanes and snapshot the advertised catalogue.
Dead code removed: the session-logging utilities, leftover type files, and an unused OAuth registration wrapper.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

discogs-mcp v3.5.0 — Egress relay, faster 429 recovery

Rian van der Merwe — Mon, 17 Aug 2026 22:39:19 GMT

This release is about the Discogs rate limit: fewer 429s to begin with, and a quick, clear answer when one does happen. Discogs throttles by source IP and a Worker's calls leave from Cloudflare's shared IPs, so discogs-mcp can now send its traffic through a relay on a machine you own (the hosted instance already does). When you are throttled, an interactive call tells you within seconds.

What's new

Route Discogs calls through your own IP. Point DISCOGS_RELAY_ORIGIN at a Cloudflare Tunnel to any always-on machine (a home Mac, a small VPS) running a local reverse proxy in front of api.discogs.com, guard it with a Cloudflare Access service token, and the whole 60-requests-a-minute budget is yours. The README has the setup, including the X-Forwarded-Host gotcha that bites cloudflared on its own. If the relay machine is off, calls go direct and nothing stops working.
ping and server_info now say how Discogs traffic is leaving ("Discogs egress: via relay relay.discogs-mcp.com, no fallbacks recorded") and, if the relay has failed, how many times and how recently.

Fixes

A single rate-limited request could take the server down for ten minutes. Now the limiter stops assuming a full budget after idle periods, backs off exponentially, and forgets stale 429 streaks across restarts, so the circuit breaker trips only on real, sustained throttling.
Interactive tool calls report a throttle in seconds; they used to sit through around 80 seconds of retries first. The background collection sync, which has nobody waiting on it, still waits the throttle out, and it now queues behind your requests.
Every authenticated tool used to spend a Discogs request just to look up your username. That now comes off the session, so a cold cache can't burn budget or trip the breaker before your actual call.
get_wantlist serves the page size you asked for when the answer comes from cache.

Under the hood

The 6-hourly collection sync runs at :23 past odd hours, away from the crowd of 0 */6 crons on the shared IPs.
Relay fallback rule: an error status with neither an x-discogs-* header nor a JSON body is treated as the relay layer (530, 502, Access 401, HTML 404) and retried directly. A 429 never is.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

TL;DL v2.5.0 — Editorial decks everywhere and a new transcription model

Rian van der Merwe — Sun, 02 Aug 2026 19:16:55 GMT

The first TL;DL release in four months. Episode summaries now carry their editorial deck and pull quote into the email newsletter and the RSS feed, transcription runs on OpenAI's new gpt-transcribe model, and a season of pipeline reliability fixes ships alongside.

What's new

Summary emails now open with the episode's editorial deck and feature its pull quote, matching the broadsheet look of the site.
The RSS feed leads each item with the episode's deck, so feed readers see the standfirst instead of a raw summary excerpt.
Transcription moved to OpenAI's gpt-transcribe model — their recommended successor to the 4o-transcribe family. Transcripts now reliably run to the end of the episode (the old model could stop early on some files), and the whisper-1 safety net for unusual audio is unchanged.
The admin dashboard was redesigned into a tabbed layout, including a new subscribers view.
Shared links look better: a proper 1200×630 social card, and page titles that lead with the tagline.

Fixes

Curly quotes and other special characters in episode titles no longer show as raw “-style codes — new titles are decoded at ingest, and existing ones were cleaned up.
An episode whose final minutes can't be decoded now keeps its transcript (marked partial) instead of failing outright.
Long episodes hosted on rate-limiting CDNs (looking at you, Substack) now ride out the throttling instead of failing mid-transcription.
Episodes no longer show up twice when the monitor and a manual submission both pick them up.
Adding a podcast whose directory listing is incomplete can no longer queue up its entire back catalog by mistake.

Under the hood

Queue processing hardened: zombie messages are dropped instead of retried forever, and the consumer's CPU budget was raised for very long episodes.
Test stack upgraded to vitest 4 + Workers pool 0.15, CI now runs on every push, and Hono security patches applied.
A summary-model A/B harness compares candidate models on real transcripts before any model swap.
The Postmark email templates are now versioned in the repo as source-of-truth copies.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

discogs-mcp v3.4.0 — Wantlist support

Rian van der Merwe — Sun, 28 Jun 2026 14:47:11 GMT

Your Discogs wantlist is now first-class in discogs-mcp. Browse the records you want but don't own, add one the moment you spot it, and clear it off the list once you've finally tracked it down — all from your LLM client, without a trip to the Discogs site.

What's new

get_wantlist browses the releases you want but don't own, paged, with the details for each so you can scan the list in conversation.
add_to_wantlist adds a release to your wantlist by its Discogs release ID — pair it with search_discogs to find the release, then add it in the same breath.
remove_from_wantlist takes a release off your wantlist once you own it.
There's a ready-made workflow built on these: the finding-original-cds skill picks the best original, non-remastered CD pressing of an album and adds it to your wantlist for you.

Fixes

The server now backs off cleanly when Discogs rate-limits a request. A per-entry retry cap and circuit breaker stop it from retrying in a tight loop, so a burst of 429s during a big collection sync pauses and recovers on its own instead of wedging.

Under the hood

Collection sync now runs every 6 hours instead of hourly — the snapshot stays plenty fresh at that cadence and it's far gentler on the Discogs API.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

Discrobble v1.3.1 — Free to start, plus a Wikipedia summary on each album

Rian van der Merwe — Fri, 19 Jun 2026 16:29:07 GMT

Discrobble is now free to start, with a one-time $4.99 unlock for unlimited scrobbling. If you were already using the app before this change, you keep unlimited scrobbling for free — thanks for being an early user. This update also adds a Wikipedia summary on the album page, a clearer view of your membership in Settings, and the option to show or hide album ratings.

What's new

Discrobble is free to start. New listeners get 20 free scrobbles, then a single $4.99 purchase unlocks unlimited scrobbling, with no subscription and no ads. Anyone who used Discrobble before this change keeps unlimited scrobbling for free.
Album pages now include a summary from Wikipedia, with a link to read the full article.
Settings shows your membership status, and lets you upgrade or restore your purchase.
You can choose whether to show album ratings, under Settings.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

Discrobble v1.2.1 — Rate your albums

Rian van der Merwe — Fri, 12 Jun 2026 23:05:41 GMT

Discrobble now shows your Discogs rating for every album and lets you set or change it without leaving the app. Open an album, tap a star, and your rating saves straight to your Discogs collection.

What's new

Your Discogs rating now appears on each album's detail screen.
Tap a star to rate an album from 1 to 5, or tap the star you've already selected to clear the rating. Ratings save to your Discogs account, so they stay in sync wherever you use Discogs.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

Discrobble v1.2.0 — Synced scrobble history

Rian van der Merwe — Sun, 31 May 2026 20:45:54 GMT

Your Recently Scrobbled history now syncs across all your devices. Scrobble an album on your iPhone and it's there on your iPad — your recent plays follow you anywhere you're signed in with the same Last.fm account.

What's new

Recently Scrobbled now syncs across every device signed into the same Last.fm account. It's there on launch — no pull-to-refresh needed.
Clear your history on one device and it clears everywhere.

Fixes

Older scrobbles from before this update may show without cover art. They clear out on their own as you keep scrobbling, or you can tidy them up right away with Clear Recent History in Settings.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

Discrobble v1.1.0 — Native iPad support

Rian van der Merwe — Tue, 26 May 2026 20:30:26 GMT

Discrobble now runs natively on iPad, with a denser collection grid and a side-by-side album view that puts the cover and tracklist together. This release also clears out a sticky onboarding bug, makes sync safer when it gets interrupted, and fully removes your data from the server when you delete your account.

What's new

Native iPad support. The collection grid adapts to the screen — more albums per row on iPad, same comfortable density on iPhone. The album screen shows the cover and the tracklist side by side in both portrait and landscape.
The onboarding and sync screens stay at a readable width on iPad instead of stretching edge to edge.

Fixes

The app could occasionally get stuck on the setup screen after you connected your accounts. Once you're signed in, you now move on.
Collection sync is safer. If a sync is interrupted partway through, it can no longer remove albums from your collection by mistake.
Deleting your account from Settings now fully removes your data from the server, not just from your device.

Under the hood

In-flight auth tokens are now encrypted at rest on the server (AES-256-GCM).
Added the Apple required-reason API privacy manifest.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

Discrobble v1.0.2 — Free on the App Store

Rian van der Merwe — Sat, 09 May 2026 20:05:48 GMT

My first iPhone app is live! Discrobble is now on the App Store, free. It connects to your Discogs collection and your Last.fm account so you can track your physical music listening in two taps: pick an album, hit "Scrobble," and the tracks land in your Last.fm history. There's more on the product page about how it works.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

discogs-mcp v3.3.0 — Background sync, instant search

Rian van der Merwe — Tue, 05 May 2026 01:13:29 GMT

The first search of the day is now instant. discogs-mcp pre-fetches your collection in the background every hour and keeps it in a snapshot, so search_collection doesn't have to paginate the Discogs API from cold any more.

The server also tells your LLM client how to navigate it — every tool response ends with a "Next steps" block listing the most likely follow-up calls and the exact arguments to use, so chained queries like "find me a mellow jazz album, then expand the top hit" don't make the model guess.

And if you've been putting off deploying your own copy, there's now a Deploy to Cloudflare button in the README — one click, three secrets, done.

What's new

Hourly background sync keeps your collection snapshot fresh. Add or remove a record on Discogs and it's visible to search within an hour, automatically.
New refresh_collection tool forces an immediate snapshot refresh — useful when you've just bought an album and want it visible to search right now.
Server-level instructions and per-tool "Next steps" breadcrumbs make the server self-navigating for any LLM client. The instructions name a recommended path (search_collection → get_release → mutations); each tool response ends with the most likely follow-up calls, with real values templated in (get_release(release_id=28861354), not release_id=<ID>). Inspired by Rui Carmo's MCP server post.
One-click self-hosting via the Deploy to Cloudflare button in the README. Cloudflare provisions the KV namespaces, Durable Object, cron, and prompts for the secrets — no wrangler kv namespace create needed, and pushes to your fork redeploy automatically via Workers Builds.

Fixes

First search_collection call after a cold cache no longer times out. Previously this could take 30 seconds to two minutes on a 1,500-item collection, often longer than the MCP request timeout. It's now sub-second.
Mood queries ("mellow Sunday morning", "road trip music") respond just as fast as keyword queries — they used to pay the same pagination cost as everything else.

Under the hood

New syncCollection module with per-page retry, resumable progress, and atomic snapshot swap so readers never see partial state.
Cron runs hourly with a probe path: one API call to compare count + page-1 instance IDs against the snapshot. Full repaginate only when something changed. Steady-state cron tick now costs 1 Discogs request instead of 16.
Self-healing across MCP request timeouts: if a sync stalls partway through, the next call resumes from where it left off rather than restarting.
Dropped the MCP_LOGS KV binding. Sync outcomes now structured-log to the Workers runtime so Cloudflare Observability ingests them — one fewer namespace for self-hosters to create.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

lastfm-mcp v2.4.0 — Top tracks and 8K fewer lines

Rian van der Merwe — Thu, 30 Apr 2026 20:09:55 GMT

The big shifts in this release: three new tools, a glassmorphism-redesigned landing page, timezone-aware day boundaries on get_recent_tracks, and a 8,300-line cull of the original session-based worker now that the OAuth path has been the only one in production for a while.

What's new

Three new tools. get_top_tracks fills the obvious symmetry gap with the existing get_top_artists and get_top_albums. get_artist_top_tracks and get_artist_top_albums surface an artist's globally most-played catalog — useful for "what's the canonical record by X" questions.
Date-aware get_recent_tracks. New date param accepts a YYYY-MM-DD calendar date plus a timezone (IANA name, e.g. America/New_York) and the server computes the correct UTC day boundaries. Way better than juggling from/to Unix timestamps for "what did I listen to yesterday" queries. The response also echoes the queried range back so an LLM can self-verify it asked the right question.
Redesigned landing page at lastfm-mcp.com — glassmorphism, animated waves, glow effects.

Fixes

get_album_info no longer renders [object Object] when Last.fm returns the album artist as an object instead of a string. Latent bug, fixed via a formatArtist helper that handles both shapes.

Under the hood

Deleted the legacy worker. Removed src/index.ts plus the homemade JSON-RPC dispatch layer in src/protocol/ and the SSE transport in src/transport/. The OAuth worker (src/index-oauth.ts) has been the only production deployment for months; the legacy [env.legacy] block in wrangler.toml was never deployed to Cloudflare. Net diff: −8,293 lines, 0 added. Test suite went from 376 tests / 5 failing → 167 tests / 0 failing.
Dropped dead deps: crypto-js, @types/crypto-js, oauth-1.0a — zero imports.
Removed dead throttle. LastfmClient.throttleRequest was per-request (clients are instantiated per-request in the OAuth worker), so it never observed a previous request — it did nothing while implying rate-limit safety. Existing 429-aware retry handles rate limits correctly.
Dynamic tool catalog. The lastfm_auth_status tool list lives in one place now (src/mcp/tools/catalog.ts) instead of being hardcoded in three.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

tldl v2.4.0 — Broadsheet redesign

Rian van der Merwe — Wed, 29 Apr 2026 21:25:26 GMT

TL;DL has a new look. Inspired by classic broadsheet newspapers, the redesigned site puts episode summaries in a layout that's calmer to read and easier to scan — with proper typography, a featured "lead" episode, and a cleaner detail page for every summary.

What's new

Broadsheet-style homepage. A featured lead episode at the top, then the rest of the week's episodes laid out as numbered index entries. Episode count grows? Pagination kicks in at 20 per page.
Redesigned episode pages. New typography (Fraunces + Inter Tight + JetBrains Mono), a generated deck and pull quote on every episode, links out to the podcast's website and Apple Podcasts, and a "More from this podcast" section.
Search and tag browsing. Search the homepage with ?q=..., click any tag to see every episode with that tag, or browse the full tag and podcast directories.
Polished mobile and tablet layouts. Episode rows stack their metadata neatly on smaller screens. Tags wrap onto their own row. Pull quotes tighten up.
Subscribe, preferences, and request flows live in the new design. No more jarring jump from the new site into the old forms.
Restored social previews. Favicon, Open Graph, and Twitter Card tags are back, so links shared on social and in chat apps look right again.

Fixes

iPad portrait layout no longer cuts off episode titles — the index now collapses to the simpler mobile-style row at tablet widths too.
Masthead date shows the correct day in Pacific time instead of drifting based on the reader's timezone.
Episode summaries no longer show a duplicate title at the top — the redundant first heading is now stripped automatically.
Editorial metadata (deck and pull quote) generation now retries cleanly on transient failures instead of giving up on the first error.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

tldl v2.3.0 — Email subscriptions

Rian van der Merwe — Wed, 22 Apr 2026 23:11:37 GMT

Per-podcast email subscriptions for tldl. Pick the shows you care about at /subscribe and the summary lands in your inbox as soon as a new episode is out.

What's new

Per-podcast email subscriptions. Sign up at /subscribe, confirm via double-opt-in, and get an HTML summary email (TL;DL header, red CTA, summary body inline) every time a monitored podcast publishes a new episode.
Preferences management. Returning subscribers can update which podcasts they're subscribed to via a signed /preferences/manage link delivered by email. One-click unsubscribe per podcast, or unsubscribe from everything.
From address on tldl-pod.com. Emails now come from "TL;DL" <summaries@tldl-pod.com> with DKIM and SPF aligned on the tldl-pod.com domain.

Under the hood

New D1 database (tldl-subscribers) for subscribers, subscriptions, and pending confirmations.
Postmark broadcast stream (episode-summaries) with HMAC-SHA-256 signed manage/unsubscribe tokens.
Zone-level rate limiting on POST /subscribe and POST /preferences (5 req / 10 min per IP + colo, 1-hour block).
Double-opt-in flow with throttled per-email pending confirmations.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

discogs-mcp v3.2.0 — Catalog-wide search

Rian van der Merwe — Sun, 19 Apr 2026 19:58:22 GMT

Adds search_discogs for catalog-wide queries beyond your own collection, plus two real-world accuracy fixes: owned-marker correctness across pressings, and exact genre/style matching.

What's new

search_discogs tool — search the full Discogs catalog, not just your collection. Default type is master so album lookups don't return duplicate pressings. Results get a ✓ marker when you already own them.
Tool lists in README, marketing page, auth_status, and server_info refreshed with grouped categories (Search, Collection, Folders, Custom Fields, Diagnostics).

Fixes

Exact genre/style matching (#17) — substring matching caused music to match Non-Music, flipping the filter to OR mode and returning unrelated releases. Now uses exact equality per release.
Release-result owned-marker is now strict on release.id. Previously, owning one pressing of an album marked every other pressing as owned too, because isOwned() matched on master_id first. Caught by real-world dogfood on "Christian Scott Stretch Music".

Under the hood

Root CLAUDE.md for Claude Code auto-discovery; removed stale development/CLAUDE.md.
GitHub release workflow auto-cross-posts to elezea.com.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.

tldl v2.2.0 — RSS-first monitoring and audio-URL dedup

Rian van der Merwe — Sun, 19 Apr 2026 18:59:50 GMT

Two meaningful changes since v2.1.0. tldl now detects new podcast episodes directly from RSS feeds with conditional GETs instead of relying on Podcast Index re-crawls, so episodes typically land in the queue within minutes of publication. A second fix catches episodes that get retitled or have their GUIDs regenerated after publication — a surprisingly common pattern in the wild.

What's new

RSS-first monitoring. The monitor now fetches RSS feeds directly with If-Modified-Since / If-None-Match headers, queues full episode metadata without a Podcast Index round-trip, and falls back to PI only on RSS errors. Detection lag drops from "hours" (PI re-crawl cadence) to "minutes" for feeds that update frequently.
POST /admin/rebuild-index. Backfill endpoint now populates audioUrl on every existing index entry so the new dedup check works retroactively.

Fixes

Silent duplicate episodes. Episodes that publishers edited after publishing — new title, regenerated GUID, or both — used to slip past dedup and get transcribed twice. A new audio-URL dedup signal (origin + pathname, query-stripped, lowercased) catches them. Confirmed against a real-world retitle where Lenny's Podcast re-published an episode with a different title + GUID, and 100 historical near-duplicates silently deduped on the first force-check after deploy.

Under the hood

Queue messages carry full episode metadata when the source is RSS, so the consumer branches on rssSourced and skips Podcast Index + iTunes enrichment entirely on that path.
New audioUrl field on EpisodeIndexEntry.
Monitor cron cadence tuned to every 2 hours — RSS conditional GETs keep the feed-scan cost low, and most monitored feeds don't publish often enough to justify the previous 30-minute cadence.

Thanks for still believing in RSS! Get in touch if you have any comments or feedback.