<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tuneping</title>
    <link>https://tuneping.com/notes/</link>
    <atom:link href="https://tuneping.com/notes/rss.xml" rel="self" type="application/rss+xml"/>
    <description>What is playing on internet radio, right now. A live index of tens of thousands of stations, served as a JSON API. Metadata only, never audio.</description>
    <language>en</language>
    <lastBuildDate>Sat, 07 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Search for a song, find the station playing it, press record</title>
      <link>https://tuneping.com/notes/tapelark-meets-tuneping/</link>
      <guid>https://tuneping.com/notes/tapelark-meets-tuneping/</guid>
      <pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate>
      <description>Tapelark records radio into a library of named tracks on your own computer. Tuneping knows which of 23,000 stations is playing what. The add-on joining the two is being built. Here is what it does, what it will not do, and a way to hear about it once, when it ships.</description>
    </item>
    <item>
      <title>Twelve things you could build on a live index of internet radio</title>
      <link>https://tuneping.com/notes/twelve-things-to-build-on-a-live-radio-index/</link>
      <guid>https://tuneping.com/notes/twelve-things-to-build-on-a-live-radio-index/</guid>
      <pubDate>Fri, 06 Nov 2026 00:00:00 GMT</pubDate>
      <description>Tuneping knows what about 23,000 stations are playing at this moment, and what 58,000 played over the last weeks. Here is what that is good for, with the endpoint each idea needs and the plan it takes. Most fit a weekend.</description>
    </item>
  </channel>
</rss>
