Publishing JavaRubberDuck Podcast to Apple Podcasts and Spotify

The show is already self-hosted via the RSS feed at https://javarubberduck.com/podcast.xml (audio files live on Cloudflare R2). Both Apple Podcasts and Spotify ingest shows by reading that public RSS feed — there is no audio upload involved, you just point each platform at the feed URL and verify ownership.

0. Prerequisites checklist (do these first)

• [ ] At least one episode published — done (3 episodes live as of 2026-06-06).
• [ ] Feed validates and is publicly reachable — confirmed, https://javarubberduck.com/podcast.xml returns HTTP 200.
• [x] Cover artwork: assets/images/podcast-cover.png is in place and referenced in podcast.njk (<itunes:image>). It's a 1400×1400 px RGB PNG at ~491 KB, meeting Apple's requirements (JPEG/PNG, RGB, square, 1400×1400–3000×3000 px, under 512 KB).
• [ ] Contact email reachable: the feed's <itunes:owner><itunes:email> resolves to site.email in _data/site.json (toenail-resolve.0q@icloud.com). Spotify sends an 8-digit verification code to this address — make sure you can receive mail there before starting the Spotify claim flow.
• [ ] AI-disclosure language is in place — see "Legal & policy notes" below. This has already been added to the channel description, the /podcast/ page, and every episode's show notes as of this write-up.

1. Submit to Apple Podcasts (via Apple Podcasts Connect)

Apple Podcasts is the feed that also powers Overcast, Pocket Casts, and most other third-party apps that use Apple's directory — so this is the highest-value submission.

1. Go to https://podcastsconnect.apple.com and sign in with an Apple ID (a free Apple ID is enough; no paid developer account required).
2. Click the + button → New Show.
3. Choose "Add a show with an RSS feed" and paste:

   https://javarubberduck.com/podcast.xml
   

4. Apple fetches and validates the feed. Review the Show Information page — title, description, category (currently Technology → Software How-To), language, and artwork should all be pulled from the feed automatically.
5. Content Rights: confirm you hold the rights to the show's content. You do — the commentary is generated from your own published news-digest posts, and the synthesized audio is produced under Google's NotebookLM terms of use for your own account.
6. Contact information: provide a name and the email from the feed (toenail-resolve.0q@icloud.com) so Apple can reach you about review issues.
7. Availability: select the countries/regions where the show should appear (default: worldwide).
8. Distribution: keep the feed publicly available, and choose whether to publish immediately or schedule a release date.
9. Click Save, let Apple re-validate the feed, then click Publish.
10. Validation/listing typically takes from ~30 minutes up to a few days. You'll get an email confirmation once the show is live in the Apple Podcasts directory and app.

Once approved, every future episode you push through the /podcast skill is picked up automatically — Apple polls the RSS feed; no manual re-submission is needed per episode.

Source: Apple Podcasts for Creators — Submit a new show

2. Submit to Spotify (via Spotify for Podcasters)

1. Go to https://podcasters.spotify.com and log in with a Spotify account (or create one — a free account is sufficient).
2. Click "Add or claim your podcast" and paste the feed URL:

   https://javarubberduck.com/podcast.xml
   

3. Spotify reads the <itunes:owner><itunes:email> value from the feed (toenail-resolve.0q@icloud.com) and emails an 8-digit verification code to that address.
4. Enter the code on the Spotify for Podcasters claim page.
5. Fill in the show's language, location/country, and category prompts (these can mirror what's already in the RSS feed: English, Technology / Software How-To).
6. Submit. Spotify typically completes review and lists the show within 24–48 hours.

As with Apple, Spotify polls the RSS feed automatically afterward — no manual step is needed for future episodes. Once the show is live, replace the placeholder https://open.spotify.com/show/ link in pages/podcast.md, _includes (if referenced elsewhere), and the episode-post template in ~/.claude/skills/podcast/SKILL.md (Step 7) with the real show URL Spotify assigns.

Source: Spotify for Creators — Claiming your podcast

3. After both are live

• Update the "coming soon" Spotify links across the site (podcast page, episode template, RSS feed if applicable) with the real show URL.
• Consider also submitting the same RSS feed to other directories that read from Apple's catalog or accept direct feeds (e.g., Pocket Casts, Overcast, Amazon Music, iHeartRadio) — they all use the same https://javarubberduck.com/podcast.xml URL, so submission is a repeat of the "paste feed URL, verify ownership" pattern above.

Legal & policy notes — publishing AI-generated content under your own name

Short answer: yes, you can publish this under your name (Stanislav Lentsov / JavaRubberDuck), as long as you clearly disclose that the hosts are synthetic voices and the show is AI-generated. Publishing it as if real people recorded it — without disclosure — is the part that would create legal and platform-policy exposure, not the act of a human producing and owning an AI-made show.

What's been done to cover this (as of this session):

1. RSS channel description (podcast.njk) now states the show is AI-generated with synthetic NotebookLM voices, right in the metadata that Apple/Spotify display in their directories.
2. /podcast/ landing page (pages/podcast.md) carries an explicit callout: "This show is AI-generated... synthetic voices produced with Google NotebookLM... no human narrators."
3. Every episode post (existing 3 episodes plus the generator template in ~/.claude/skills/podcast/SKILL.md) now includes an inline disclosure line right next to the audio player.

Why this matters and what's driving it:

• Apple Podcasts Content Guidelines (§1.11–1.12) require disclosure — in audio and/or metadata — whenever a synthetic voice performs a material portion of hosting/narration. Two fully-synthetic hosts clearly qualifies; the disclosures above satisfy the metadata half. (Optional but recommended: have the NotebookLM intro itself state "this podcast was generated by AI" in the audio — see "Suggested follow-up" below.)
• Spotify classifies shows as human-made / AI-assisted / fully AI-generated and is actively cracking down on undisclosed synthetic shows (it now offers "Verified" badges partly to combat AI impersonation). Being upfront about the NotebookLM pipeline keeps the show on the right side of that policy and avoids takedown risk.
• FTC guidance on AI-generated/synthetic media (2025–2026 enforcement push) centers on deception — misleading listeners into thinking they're hearing real people or independently-reported claims. A clear, prominent disclosure that the hosts are synthetic and the commentary is AI-generated from your own published articles removes the deceptive element entirely. There is no rule against an individual owning, producing, and publishing an AI-generated show under their real name — the obligation is transparency about how it was made, not anonymity about who made it.
• No voice-cloning concerns: NotebookLM's "Alex"/"Jordan" personas are Google's synthetic voices, not clones of real identifiable people, so right-of-publicity laws (e.g., Tennessee's ELVIS Act, NY's new synthetic-performer law) don't come into play here.

Suggested follow-up (not yet done, optional): add one sentence to the very start of the NotebookLM generation prompt in ~/.claude/skills/podcast/SKILL.md (Step 4, the DESCRIPTION variable) so the audio itself opens with something like "Quick note before we start — this episode was generated by AI using Google NotebookLM, based on real published news stories." That gives you both an audio-level and a metadata-level disclosure, which is the most conservative reading of Apple's guidelines and removes any ambiguity for listeners who never see the show notes.