← All articles

Podcast chat tag: how official chat is declared

Explore this article with AI

Open a source-aware analysis with this article as the primary source.

ChatGPTClaudePerplexityGeminiGrokGoogle AI
Follow Podder on Google

Add us to your Preferred Sources.

The podcast chat tag is RSS metadata that tells supporting apps where to find the official chat for a podcast, episode, or live event. Written as <podcast:chat>, it identifies a chat server and protocol, with optional details for the podcaster's account and the relevant room or topic. Its location in the feed determines the scope.

What the podcast chat tag contains

The Podcast Namespace chat specification defines the tag for ephemeral chat rather than general social interaction. It is designed to accommodate different chat protocols instead of prescribing one service.

Two attributes are required:

AttributeStatusPurpose
`server`RequiredFully qualified domain name of the bootstrap chat server
`protocol`RequiredProtocol used on that server
`accountId`RecommendedPodcaster's account identifier on the server or platform
`space`OptionalRoom, space, channel, or topic identifier

The protocol value should come from the protocol list maintained by the Podcast Namespace project. The server is a fully qualified domain name, not a listener-facing description or a full invitation sentence.

<podcast:chat
  server="irc.zeronode.net"
  protocol="irc"
  accountId="@jsmith"
  space="#myawesomepodcast"
/>

This IRC example supplies all four attributes. The exact format of accountId and space depends on the selected protocol.

Channel, episode, and live event scope

A <podcast:chat> element can appear once under <channel>, <item>, or <podcast:liveItem>. A channel-level tag represents chat for the entire podcast and is the recommended place for an always-on room.

An item-level tag applies to that episode. A live-item tag applies to that live event. In both cases, the more specific tag overrides chat information at channel level for the corresponding content.

<channel>
  <podcast:chat
    server="example.com"
    protocol="matrix"
    accountId="@host:example.com"
    space="#show:example.com"
  />

  <item>
    <title>Listener questions</title>
    <podcast:chat
      server="example.com"
      protocol="matrix"
      accountId="@host:example.com"
      space="#episode-42:example.com"
    />
  </item>
</channel>

Here, episode 42 points to its own room. Other episodes can continue to use the channel-level room when they do not contain a more specific tag.

The podcast RSS feed glossary maps the channel and item structure. The RSS namespace glossary explains how the podcast: prefix identifies this extension vocabulary.

Examples for different protocols

The official documentation includes IRC, XMPP, Nostr, and Matrix examples. Their account and room syntax differ, which is why the protocol attribute must agree with the values supplied in the other fields.

An XMPP entry can look like this:

<podcast:chat
  server="jabber.example.com"
  protocol="xmpp"
  accountId="jsmith@jabber.example.org"
  space="myawesomepodcast@jabber.example.org"
/>

A Nostr entry can name a relay as the server, nostr as the protocol, an npub account identifier, and a topic in space. A Matrix entry can use a homeserver domain with Matrix-style account and room identifiers.

Copying one protocol's identifier syntax into another protocol's declaration can leave a supporting app without a usable destination. Validate all four values as one configuration.

What publishing the tag proves

A valid tag proves that the feed publisher declared chat information in the inspected XML. It does not prove that every podcast app supports the tag, that the room is reachable, that listeners can join without an account, or that the named account controls the room.

The tag is also separate from an episode's media delivery. The enclosure URL glossary covers the URL an RSS item uses for its audio or video resource. A working enclosure says nothing about chat availability, and a working chat room says nothing about episode playback.

Test the feed declaration and the chat service independently. App rendering is a third check for any listening app you expect your audience to use.

How to publish and check podcast:chat

Choose the scope first. Use the channel for one always-on room. Add an item-level or live-item-level entry only when that content needs a different destination.

Confirm the server domain, protocol token, account identifier, and room value against the chat service itself. Publish the tag through your host or feed generator, then inspect the raw feed to make sure it appears under the intended parent.

Next, connect to the room using the stated protocol outside the podcast app. Check whether a new listener needs an account or invitation, and document any moderation or access steps in a place your audience can see. Finally, test the show or episode in an app that documents support for the tag. Do not infer broad support from one successful client.

Recheck a live-event room before the scheduled start. A syntactically valid feed can still point to a retired server, renamed room, or account that no longer has access. Update the source feed rather than patching a single app listing.

For episode delivery alongside your community work, Podder Analytics can provide listening context. Verify the chat declaration in the feed and the room on its own service.

FAQ

What is the podcast chat tag?

It is Podcast Namespace metadata that tells supporting apps where to find the official chat for a podcast, an episode, or a live event.

Where can podcast:chat appear in a feed?

It can appear once under a channel, an item, or a podcast:liveItem. An item-level or liveItem-level tag overrides the channel-level chat for that specific content.

Which podcast:chat attributes are required?

Server and protocol are required. AccountId is recommended, while space is optional and can identify a room, channel, or topic.

Put it into practice

See who's actually listening.

Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.

Start free