<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrew Kuklewicz on Medium]]></title>
        <description><![CDATA[Stories by Andrew Kuklewicz on Medium]]></description>
        <link>https://medium.com/@kookster?source=rss-24f8fdb8981------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jBqj9z8KI4cMWolB.jpeg</url>
            <title>Stories by Andrew Kuklewicz on Medium</title>
            <link>https://medium.com/@kookster?source=rss-24f8fdb8981------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:41:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kookster/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Web Monetization and Podcasting]]></title>
            <link>https://medium.com/prxofficial/web-monetization-and-podcasting-850d45f27882?source=rss-24f8fdb8981------2</link>
            <guid isPermaLink="false">https://medium.com/p/850d45f27882</guid>
            <category><![CDATA[podcasting]]></category>
            <category><![CDATA[micropayments]]></category>
            <category><![CDATA[open-web]]></category>
            <category><![CDATA[web-monetization]]></category>
            <category><![CDATA[creative-economy]]></category>
            <dc:creator><![CDATA[Andrew Kuklewicz]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 14:13:13 GMT</pubDate>
            <atom:updated>2023-01-10T15:41:12.977Z</atom:updated>
            <content:encoded><![CDATA[<p>At PRX, we’ve been working on supporting micropayments for podcasting using <a href="https://webmonetization.org/">Web Monetization</a>. Web Monetization is a way to reward creators with real-time micropayments for their work while protecting privacy and supporting an open web. We see this as part of our larger goals to protect listener privacy and an open podcasting ecosystem.</p><p>With help from <a href="https://www.grantfortheweb.org/">Grant for The Web</a>, PRX built support for Web Monetization into our platform, and we are working with key creators to experiment with using these payments on their shows and websites, like “<a href="https://songexploder.net/">Song Exploder</a>.”</p><h4>Micropayments</h4><p>In podcasting, and the internet in general, there are many ways to monetize: sponsorship, advertising, subscriptions, or for the lucky few, a book or movie deal. Still, every choice is a matter of trade-offs. Advertising costs attention and often entails tracking people’s internet activity (and thus, a loss of privacy). Subscriptions limit audiences and require signing up for yet another service. Movie deals…well, alright, that’s nice work if you can get it.</p><p>A still nascent form of monetization is micropayments. With micropayments, people sign up to reward creators based on their attention, and then creators receive a stream of payments when someone reads, views, or listens to their work online on a platform that enables payments. Micropayments are already happening with <a href="https://podcastindex.org/podcast/value4value">Podcasting 2.0’s Value 4 Value</a>, and many podcasters (&gt; 10,000) have adopted micropayments using <a href="https://podnews.net/article/how-to-earn-bitcoin-from-your-podcast">Bitcoin over the Lightning network</a>.</p><p>But, for all the potential, the trade-off with micropayments is the technical and behavioral challenge of getting people to adopt the technology. To effectively adopt micropayments, you need consumers to sign up and enable payments, a way to know when content is consumed, <em>and</em> an affordable means to send payments. Ideally, all of this would be enabled to work on any website, anywhere, and not be limited by currency or vendor, and everyone would use it.</p><h4>Web Monetization</h4><p>Web Monetization meets the technical challenges of micropayments. It is a<a href="https://webmonetization.org/specification.html"> proposed standard</a> with the W3C, the same international consortium that established all the major standards for the World Wide Web. Unlike other micropayment attempts like Value 4 Value that requires Bitcoin or <a href="https://brave.com/brave-rewards/">Brave that uses the Basic Attention Token (BAT)</a>, Web Monetization is not tied to a specific currency, implementation, or proprietary technology. Like other web technologies, it is based on standards that are meant to have many competing implementations, just as Mozilla, Google, and Microsoft all implement web standards in their own browsers. Another open standard that Web Monetization depends on is the <a href="https://interledger.org/developer-tools/get-started/overview/">Interledger payments protocol</a>, which is built for transferring payments between banks, ledgers, and currencies, allowing payments to flow without requiring any single payment provider or financial institution.</p><p>For example, if a person only wants to pay or receive traditional fiat currencies like USD, they can do so. The payments move through payment routers like data through a network, with defined start and end points, but no particular currency or payment provider required along the way, though in current implementations, they will often go through the<a href="https://xrpl.org/"> XRP Ledger</a>, an open-source, low-cost, energy-efficient blockchain built for making micropayments.</p><p>Even with all these technical advantages, there is still the behavioral challenge to adopting Web Monetization by consumers, creators, and the technologists that build on these standards. To that end, the <a href="https://interledger.org/">Interledger Foundation</a>, <a href="https://foundation.mozilla.org/en/campaigns/web-monetization/">Mozilla</a>, <a href="https://creativecommons.org/2019/09/16/grant-for-the-web">Creative Commons</a>, and <a href="https://coil.com/">Coil</a> all recognized the need to bootstrap adoption of the new ecosystem and created <a href="https://www.grantfortheweb.org/">Grant for the Web</a> to support this new open payments ecosystem.</p><h4>Getting Started for Creators and Audiences</h4><p>For creators to get started, they need an online wallet, like an <a href="https://webmonetization.org/docs/uphold/">Uphold</a> account, to receive money via the protocol that handles micropayments (i.e. <a href="https://interledger.org/developer-tools/get-started/overview/">Interledger</a>).</p><p>With a wallet, they get a public address for receiving payments, something like the <strong>“@First-Lastname”</strong> addresses Venmo and similar (proprietary) services provide. Public addresses for Web Monetization are called<a href="https://webmonetization.org/docs/ilp-wallets/#payment-pointers"> Payment Pointers</a>, and look something like <strong>“$ilp.uphold.com/ABC3DefGHijk”</strong>.</p><p>Much like an email address is how folks send messages to someone, this payment pointer is how they send payments to a creator. To use it, the address needs to be available and enabled where an audience pays attention to work on the web, and the audience needs to have set up paying for that work.</p><p>Wallets provide a way for a creator to receive payments, while a membership with <a href="https://coil.com/">Coil</a> (and <a href="https://help.coil.com/docs/membership/coil-extension/index.html">installing a browser extension</a>) is how a fan can send money. Each Coil member who pays $5 a month supports web-monetized content with $0.36 per hour of attention. This may not sound like much, but it adds up, especially when compared to advertising. A thousand listens to a podcast, with three mid-rolls at a $20 CPM, would only pay $60, but if those same thousand listeners play 30 minutes of content, that’s $180.</p><p>Wallets and memberships are the two hands reaching out to make Web Monetization connect. When used in combination, if a <a href="https://coil.com/">Coil</a> member visits monetized content, all a creator needs is <a href="https://webmonetization.org/docs/getting-started#4-add-the-meta-tag-to-your-website">a single tag</a> on their site, link their<a href="https://help.coil.com/docs/monetize/content/youtube-monetize-channel/index.html"> YouTube channel</a>, or add it to their PRX-hosted podcast to enable payments.</p><h4>Web Monetization with Dovetail</h4><p>For podcasters using <a href="https://dovetail.prx.org/">Dovetail from PRX</a>, it’s simple to get started with Web Monetization (all explained in <a href="https://help.prx.org/hc/en-us/articles/9901810244251-How-can-I-set-up-micropayments-for-my-podcast-">this help article</a>).</p><p>On any podcast in Dovetail, a producer can paste in a payment pointer address, hit save, and the feed will be updated to include the address and enable monetization:</p><figure><img alt="Screen shot of setting up Web Monetization in Dovetail" src="https://cdn-images-1.medium.com/max/1024/1*F627GuS5sBmC0PQlWaTqEA.png" /><figcaption>Setting up Web Monetization in Dovetail</figcaption></figure><h4>A Web Monetized Podcast Player</h4><p>Adding the payment pointer to the feed is essential, but we also need podcast players to be Web Monetization enabled and make use of it. PRX also supports an open-source web player for podcasts, so we added support for web monetization in our own player, the same one used already by many of our podcasters like on “<a href="https://songexploder.net/">Song Exploder</a>” and “<a href="https://bookexploder.com/">Book Exploder</a>.”</p><p>Now, when someone using web monetization listens to an episode on the<a href="https://bookexploder.com/episodes/james-mcbride"> Book Exploder</a> website, they will send payments while they listen, with the dollar sign icon showing that monetization is happening:</p><figure><img alt="Screen shot of the PRX Player showing the monetization dollar sign in the bottom right corner" src="https://cdn-images-1.medium.com/max/1024/1*E5j6N0RX-dsM5jVSEmU2aw.png" /><figcaption>An example PRX Player showing the monetization dollar sign in the bottom right corner</figcaption></figure><p>Clicking on the dollar sign icon shows a visualization for the streaming payments, and how much money has been sent while listening:</p><figure><img alt="Screen shot of the PRX player showing payments streaming from the listener to the creator during playback" src="https://cdn-images-1.medium.com/max/1024/1*bw4tHdtYx8vZdFEy2xqobg.png" /><figcaption>The player shows payments streaming from the listener to the creator during playback</figcaption></figure><p>To make this work, Dovetail adds the payment pointer in a special tag in the RSS feed for the player to use to stream payments during playback. But we didn’t want to update the feed in a way that only works for PRX, we built on the work at the <a href="https://github.com/Podcastindex-org/podcast-namespace/issues/132">Podcast Index defining monetization</a> in RSS, and further on how the folks at <a href="https://blog.castopod.org/castopod-supports-web-monetization/">Castopod built support for Web Monetization</a>. The result is a <a href="https://github.com/Podcastindex-org/podcast-namespace/pull/409">Podcasting 2.0 proposal for a standard way to use web monetization for podcasting</a> that should work for any podcast host, and can be adopted by any podcast website or web player.</p><p>This is important, because when you believe in standards, it means working to support and bolster the work and inventions of others. As a practical result, it also means what we’ve built is interoperable, so with help from the team at <a href="https://blog.castopod.org/castopod-supports-web-monetization/">Castopod</a>, Castopod hosted podcasts can also receive payments from the open source PRX player.</p><p>For example, this Castopod hosted show “<a href="https://lespoesiesdheloise.fr/@heloise">Les Poésies d’Héloïse</a>” can use the <a href="https://play.prx.org/e?uf=https://lespoesiesdheloise.fr/@heloise/feed.xml">PRX embeddable player</a> to receive web monetized payments, just exactly like one hosted on Dovetail:</p><figure><img alt="Screen shot of the a Castopod podcast with streaming payments in the PRX player" src="https://cdn-images-1.medium.com/max/1024/1*Ucrbig7uwep0yOdUCe9wCw.png" /><figcaption>A Castopod podcast with streaming payments in the PRX player</figcaption></figure><h4>What next?</h4><p>As we advance an open podcasting ecosystem, we need more of the kind of collaboration and interoperability that standards provide and experiments to learn how best to use them.</p><p>As you might expect with experimental tech, there are still some limitations to how this works.</p><p>One shortcoming is that the current Web Monetization is really only for the web and isn’t integrated into mobile apps, which account for much of podcast listening. This is also true of other types of media consumption and will eventually be addressed as the standards gain adoption.</p><p>Another is that payments only flow <a href="https://github.com/WICG/webmonetization/issues/17">when the browser is in the foreground</a>, which is perfect for text and video but not for audio. The equivalent for podcasts and music might be to stream payments when the sound is playing unmuted and loud enough to hear but unrelated to the browser focus or visual placement.</p><p>And the main limitation is not enough folks have <a href="https://coil.com/">signed up to use Web Monetization to reward creators</a> for it to replace other sources of revenue.</p><p>If we want the future to be more equitable, open, and privacy safe, we have to be willing to experiment and work for it. We invite you all to <a href="https://help.prx.org/hc/en-us/articles/9901810244251-How-can-I-set-up-micropayments-for-my-podcast-">join us in this experiment</a>, <a href="https://community.interledger.org/page/intro-to-web-monetization">learn more</a> about <a href="https://webmonetization.org/">Web Monetization</a> than this one post can convey, and think critically about how the choices we make affect creators, listeners, and the open web.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=850d45f27882" width="1" height="1" alt=""><hr><p><a href="https://medium.com/prxofficial/web-monetization-and-podcasting-850d45f27882">Web Monetization and Podcasting</a> was originally published in <a href="https://medium.com/prxofficial">PRX Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Front Row Seat for S-Town]]></title>
            <link>https://medium.com/prxofficial/front-row-seat-for-s-town-462f158de2be?source=rss-24f8fdb8981------2</link>
            <guid isPermaLink="false">https://medium.com/p/462f158de2be</guid>
            <category><![CDATA[this-american-life]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[podcasting]]></category>
            <category><![CDATA[radio]]></category>
            <category><![CDATA[advertising]]></category>
            <dc:creator><![CDATA[Andrew Kuklewicz]]></dc:creator>
            <pubDate>Thu, 13 Apr 2017 20:03:46 GMT</pubDate>
            <atom:updated>2017-04-13T20:07:39.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*dWJjxrrLtUpGMGrzXsn8BQ.png" /><figcaption>S-Town Chapter 1, taken gently from the website</figcaption></figure><p>At <a href="https://www.prx.org/">PRX</a> we’ve had the good fortune of working with the team at <a href="https://www.thisamericanlife.org/"><em>This American Life</em></a> for a while, starting with our collaboration on <a href="http://webbyawards.com/winners/2011/mobile-apps/handheld-devices/entertainment-handheld-devices/this-american-life-for-iphone/">mobile applications</a>, then <a href="https://blog.prx.org/2014/05/american-life-self-distributes-partners-prx-deliver-episodes/">broadcast distribution</a> when they became an independent <a href="https://www.thisamericanlife.org/blog/2015/07/changes-at-this-american-life">public benefit corporation</a>, and for the last few years in podcast ad serving (we aren’t involved in producing the shows, so don’t ask me when <em>Serial</em> season 3 is coming out). At each juncture, their <a href="https://serialpodcast.org/">popular</a> and <a href="https://www.thisamericanlife.org/">beloved</a> programs have been inspiring to work with, but also challenging, especially technically. All that love can translate into strained servers.</p><p>No challenge had been bigger than when we took on ad serving for the <a href="https://serialpodcast.org/"><em>Serial</em></a> podcast, starting with <a href="https://serialpodcast.org/season-two">season two</a>’s launch. <a href="https://serialpodcast.org/season-one">Season one</a> was distributed the traditional way, with the now famous ads for “<a href="https://qz.com/298094/how-mailchimps-irresistible-serial-ad-became-the-years-biggest-marketing-win/">MailKimp</a>” and other sponsors mixed into the episode audio, and the mp3 files served statically from a <a href="https://en.wikipedia.org/wiki/Content_delivery_network">CDN</a>. In the traditional model, the main bottleneck is that the CDN needs to scale to serve large volumes of requests and bandwidth, but of course, that’s what they’re made for.</p><p>For <a href="https://serialpodcast.org/season-two"><em>Serial</em> season two</a>, the plan was to get more advanced and use dynamic ad serving, “injecting” the ads into the episode audio. With dynamic serving, things get complex. Instead of sending download requests to the CDN immediately, our <a href="https://blog.prx.org/2016/05/dovetail-prxs-ad-insertion-product/">Dovetail media server</a> has to specifically answer every request, figuring out which audio messages to stitch in based on the scheduled campaigns, and what we know about the listener from the download request, like their geolocation, device, and app they’re listening on. We joke that we’re making “artisanal audio”, with each file lovingly hand-crafted for the listener, but the truth behind the joke is that every request does get its own consideration, its own announcements, and its own sponsorship messages stitched in along with the show.</p><p>After getting Dovetail to work for <em>Serial</em>, I’d show off graphs of what it looked like when a new episode dropped and all the podcatcher apps decided to download it at once:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lH1hHZPyLQVLW9ne_8T3NA.png" /></figure><p>Whenever a new episode landed, in just a moment the already significant traffic for season one &amp; two episodes would increase by six times. I love showing how Dovetail had been tuned to handle the load.</p><p>I thought that was pretty impressive, and that after <em>Serial</em>, Dovetail could handle just about anything. Then <a href="https://twitter.com/sethlind">Seth</a> at <em>This American Life</em> said they had a new show to put on Dovetail, and it would have a few differences. First, even though it was a <em>Serial</em> spin-off, it would be a whole new feed, so for better or worse it wouldn’t start with the existing <em>Serial</em> subscribers. Second, they wanted to have different ads in the audio from the start, but didn’t want them injected. They wanted the ads to be “baked in”, with two different versions of each episode, and each served half the time. Finally, (surprise!) all the episodes would drop at once, like a podcast version of a Netflix “binge-ready” show.</p><p>For this new show, which we now know as <a href="http://stownpodcast.org/"><em>S-Town</em></a>, having a new feed wasn’t a problem. If anything, I thought perhaps the system wouldn’t be hit as hard as it was by <em>Serial’s</em> two seasons of subscribers. That turned out to be correct but not meaningful; though starting from scratch, the initial burst of traffic reflected the enormous number of <em>S-Town</em> listeners who subscribed to the preview.</p><p>Serving up different but complete versions of a show was not a feature of Dovetail, and to some degree it still isn’t, but Dovetail is flexible and extensible. Given this challenge, we looked for a way to make the experiment work — I think I sent Seth about five different ideas to try, and luckily we had enough warning to figure out one that worked. Normally, the episode audio is the constant, and only the ads change. For <em>S-Town</em>, we created scripts to set it up in a unique way, reversing the usual role of the audio files; the ad would be the actual episode audio with ads baked in, and the episode audio would be a tiny silent audio file. The result was that half the time it served up the complete “Blue Apron” version of an episode, by stitching the Blue Apron episode audio as an “ad” onto the empty “episode” audio. The other half would be the “Squarespace” version, depending on whose turn it was as determined by the Dovetail traffic system. A neat trick, almost like A/B testing, and perhaps one we’ll figure out how to turn into a regular feature of Dovetail. For now it’s a successful experiment, and one we have the scripts and experience to build on.</p><p>The final difference was dropping all seven episodes at once. Our best guess was that this would create a spike greater than a single <em>Serial</em> episode, despite there being fewer initial subscribers. We more than doubled the cluster of Dovetail servers, and were prepared to expand further if needed. As it turns out, we didn’t need to at first, but the spike was just a bit higher than <em>Serial’s. </em>Below is a similar graph for <em>S-Town</em> lined up against that “impressive” <em>Serial</em> graph:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBQfHACnpGQSvZXeOjfp5w.png" /></figure><p>If a <em>Serial</em> episode was a mountain peak, then <em>S-Town</em> was the Himalayas; not only was the initial traffic roughly quadruple that of <em>Serial</em>’s, it just kept going, rising in the evening to a higher load than when the episodes first dropped. <em>Serial</em> episodes would often have a smaller secondary peak in the evening, but never higher, and never with such sustained traffic between the peaks. I’ve honestly never seen a download request pattern like what <em>S-Town’s </em>release produced.</p><p>Unlike when a single <em>Serial</em> episode would drop, where the sudden spike was followed by a downward slope as traffic abated, <em>S-Town</em> requests continued apace all day, and then day after day, with day two requests slightly fewer than one, day three practically identical to two, then only slightly decreasing in the days that followed.</p><p>While our estimate of servers was enough for the initial release, within the first day of <em>S-Town</em>, we upgraded Dovetail’s cluster to bigger machines to handle the unprecedented sustained load. We’ve made another round of improvements to caching and operations to keep it performing. After <em>S-Town</em>, we are that much more confident in our technology, both in new ways of using it, and under extreme load. Plus, the next time someone asks me what Dovetail can do, I have a new graph to show them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=462f158de2be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/prxofficial/front-row-seat-for-s-town-462f158de2be">Front Row Seat for S-Town</a> was originally published in <a href="https://medium.com/prxofficial">PRX Official</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>