<?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 Ian Boynton on Medium]]></title>
        <description><![CDATA[Stories by Ian Boynton on Medium]]></description>
        <link>https://medium.com/@iboynton?source=rss-d09f3c74fa24------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nb0UTxp9aTiHivMaP04QOw.jpeg</url>
            <title>Stories by Ian Boynton on Medium</title>
            <link>https://medium.com/@iboynton?source=rss-d09f3c74fa24------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:08:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iboynton/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[JW Player Webhooks]]></title>
            <link>https://medium.com/jw-player-engineering/jw-player-webhooks-28672389377d?source=rss-d09f3c74fa24------2</link>
            <guid isPermaLink="false">https://medium.com/p/28672389377d</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[webhooks]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ian Boynton]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 14:45:08 GMT</pubDate>
            <atom:updated>2020-07-07T14:45:08.716Z</atom:updated>
            <content:encoded><![CDATA[<p>The media lifecycle is asynchronous: the final product, a video you can put on your website, is the result of a series of jobs including, but not limited to, the transcoding of media assets into the various renditions, thumbnail generation, and the indexing of the media asset for distribution via our delivery API’s.</p><p>Until now, customers have had to rely on a pull model to understand the state of their media, an imperfect solution that requires burdensome polling logic, and one which provides an incomplete picture of what has happened, and when.</p><p>Webhooks provide our customers a lighter weight and easier-to-maintain solution to address these shortcomings. By providing real-time push notifications for media lifecycle transitions, webhooks empower publishers to get their content delivered to their end users faster, and design custom workflows (including through a <a href="https://zapier.com/apps/jw-player/integrations">host of no-code integrations</a> by Zapier, which we recently released and wrote a <a href="https://medium.com/jw-player-engineering/enabling-video-workflows-with-zapier-and-jw-player-cbff64df4350">blog post </a>on).</p><p><strong>Getting set up with webhooks</strong></p><p>JW Player webhooks are managed through a RESTful API.</p><p>The structure of JW Player webhooks is relatively simple, with each webhook having the following properties:</p><ul><li>A name</li><li>An optional description</li><li>The properties for which you want to be alerted</li><li>An HTTPS endpoint to which we can forward notifications</li><li>The events you are interested in subscribing to</li></ul><p>At the time of this writing, JW Player offers the ability to subscribe to three events:</p><ul><li><strong>Media Available:</strong> The first point at which a media can be delivered via our CDN and Playlist API’s. This guarantees that the media is available in our delivery API’s, and that a thumbnail and the lowest rendition of the asset have been transcoded.</li><li><strong>Conversions Complete</strong>: The point at which all renditions, including the highest quality rendition, of an asset have been transcoded and will be served out by our delivery API.</li><li><strong>Media Updated</strong>: Notifies you when an existing media asset has been updated. This includes updates to media metadata, such as its title, tags, etc.</li></ul><p>Creating a webhook is as simple as a cURL call:</p><pre>curl -XPOST \<br>-H ‘Content-Type: application/json’ \<br>-H ‘Authorization: {v2_api_token}’ \ <a href="https://api.jwplayer.com/v2/webhooks">https://api.jwplayer.com/v2/webhooks</a> \<br>-d &#39;{&quot;metadata&quot;: {&quot;name&quot; : “Media Available Webhook&quot;, &quot;description&quot;: &quot;Webhook to notify me when media is ready to be published&quot;, &quot;webhook_url&quot;: “https://my-endpoint.com&quot;, &quot;events&quot;: [&quot;media_available&quot;], &quot;site_ids&quot;: [&quot;1A23bCD4&quot;]}&#39;</pre><p>When a subscribed-to event occurs, JW Player will send a POST request to the specified Webhook URL containing a payload with the corresponding property and Media ID’s, as well as the event that triggered the notification.</p><p>In order to provide additional security, JW Player includes a JWT Authentication token on the POST request, which can be verified using a shared secret. The secret is returned only when the Webhook is created. By using JWT, customers can ensure that JW Player was the originator of the request.</p><p>For full documentation, refer to our <a href="https://developer.jwplayer.com/jwplayer/reference#webhooks">Developer site</a>.</p><p><strong>Behind the Scenes</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HVxQgKJpyoBHt5c9" /></figure><p>JW Player relies on an event-driven architecture to notify downstream systems of media lifecycle events. At the center of our system lies PubSub, implemented using a RabbitMQ topic exchange, which allows internal consumers to subscribe to events in the media lifecycle which they care about. Webhooks Service serves as an external interface into this system.</p><p>The Webhooks Service is composed of three primary applications:</p><ul><li><strong>API</strong>: A CRUD API for the management of Webhook resources, backed by a PostgreSQL database.</li><li><strong>PubSub Consumer</strong>: A RabbitMQ worker which consumes internal PubSub events from which we query the Webhooks API to identify any corresponding subscriptions. For each subscription, a distinct RabbitMQ event is published to an internal queue for further processing.</li><li><strong>Relayer:</strong> A RabbitMQ worker which consumes from the internal “notifications” queue, sending the HTTP request to the Webhook URL specified by the corresponding subscription.</li></ul><p>Both RabbitMQ consumers are stateless, allowing us to scale horizontally as needed, and ensure that we can deliver our notifications in a timely fashion.</p><p>PubSub also provides excellent built-in retry functionality, providing us with stronger guarantees on the delivery of messages internally, and, in this case, notifications externally. Webhooks will retry with an exponential back-off over a 24-hour period if the subscribed service does not respond with an HTTP response in the 2XX range.</p><p><strong>Working with an eventually consistent delivery system</strong></p><p>In addition to RabbitMQ, JW Player heavily leverages Kafka as a message broker. Within the context of the Media lifecycle, we utilize Kafka as a source for several ElasticSearch clusters tasked with the delivery of media.</p><p>These delivery systems do not maintain the lifecycle state of media, and are eventually consistent; powered by Debezium, we are continually indexing media, streaming all creations, deletions, and updates to maintain an eventually-consistent view of our customers’ video libraries.</p><p>In the case of Webhooks’, this presents two problems as it relates to the “media available” event (when a media can first be served):</p><ol><li>We cannot guarantee the amount of time it takes to index a media asset</li><li>These systems do not store or publish data from which we can determine the time a media was first indexed.</li></ol><p>To work around this problem, we introduced an additional RabbitMQ worker which serves to provide (and publish) this information. This worker consumes all “ready” events from our transcoding system, which indicate that the first rendition and a thumbnail have been generated.</p><p>The worker guarantees a deliverable state by polling ElasticSearch for the media assets. Upon confirmation that the media has been indexed, the worker publishes a PubSub event representing the new state. For safe measure, this worker also requests the media asset from our CDN to prevent cache interference.</p><p>This new “indexed” event is then read by the primary RabbitMQ PubSub consumer and handled like any other subscribable event.</p><p><strong>We’d love to hear from you!</strong></p><p>Our focus on the Platform Interfaces team at JW Player is to provide customers with the tools they need to design intelligent workflows that meet their needs, and simplify the management of their video libraries.</p><p>Webhooks is just one of many tools that we’re thinking about, and we want to hear from you so that we can continue to deliver interfaces to help make your video-management lives all the better. If you have any feedback, questions, or comments about JW Player Webhooks, or anything else related to managing your video libraries<em>, </em>please reach out to us at support@jwplayer.com.</p><p>If this kind of work interests you as an engineer, we’re hiring: <a href="https://www.jwplayer.com/careers/#job-openings">https://www.jwplayer.com/careers/#job-openings</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28672389377d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jw-player-engineering/jw-player-webhooks-28672389377d">JW Player Webhooks</a> was originally published in <a href="https://medium.com/jw-player-engineering">JWX Product &amp; Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JW Lens, now in open beta]]></title>
            <link>https://medium.com/jw-player-engineering/jw-lens-now-in-open-beta-ce68d4169b17?source=rss-d09f3c74fa24------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce68d4169b17</guid>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[html5-video]]></category>
            <category><![CDATA[chrome-extension]]></category>
            <category><![CDATA[extension]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Ian Boynton]]></dc:creator>
            <pubDate>Tue, 23 Apr 2019 17:09:44 GMT</pubDate>
            <atom:updated>2019-04-23T17:09:44.061Z</atom:updated>
            <content:encoded><![CDATA[<h3>JW Lens, now in Open Beta</h3><p>A few months ago, we published a <a href="https://medium.com/jw-player-engineering/troubleshooting-html5-video-with-jw-player-2ddb58123ec3">blog post</a> on JW Lens. We are excited to announce that the beta is now open, and the extension is available for download on the Chrome Web Store.</p><h3>What is JW Lens?</h3><p>JW Lens is a browser extension that makes it easier for you and your team to work with your JW Player.</p><p>JW Lens captures and records information emitted from the player without you having to write a line of code and surfaces the information you care about in an intuitive interface.</p><p>JW Lens fires up when it detects a JW Player on your page, enabling you to get your player information with just a click of a button.</p><h3>Where can I access it?</h3><p>JW Lens is available on the <a href="https://chrome.google.com/webstore/detail/jw-lens/oneljddokkbioaemddedcbdejocnhijg">Google Chrome Store</a>.</p><h3>Why should I care about JW Lens?</h3><p>JW Lens helps you to explore and troubleshoot the HTML5 player in your production environment JW Player:</p><ul><li>Understand the JW Player event lifecycle</li><li>Troubleshoot player errors</li><li>Validate your player configuration</li><li>Test new ad tags</li><li>Evaluate video streaming</li></ul><h3>How do I use JW Lens?</h3><p>You don’t have to do anything, just install it from the link below! When the extension detects a player on the page, it will begin capturing, recording and illustrating all the information emitted from the player.</p><p>To open the extension, click the JW Player logo that appears in your extension bar after installation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lkP3szmHCOsqQU4W" /></figure><p>Switch between the tabs to see different information, including a player overview, an error summary, a feed of all events emitted from the player.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce68d4169b17" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jw-player-engineering/jw-lens-now-in-open-beta-ce68d4169b17">JW Lens, now in open beta</a> was originally published in <a href="https://medium.com/jw-player-engineering">JWX Product &amp; Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Troubleshooting HTML5 Video with JW Player]]></title>
            <link>https://medium.com/jw-player-engineering/troubleshooting-html5-video-with-jw-player-2ddb58123ec3?source=rss-d09f3c74fa24------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ddb58123ec3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[html5]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[online-video]]></category>
            <category><![CDATA[video-player]]></category>
            <dc:creator><![CDATA[Ian Boynton]]></dc:creator>
            <pubDate>Thu, 01 Nov 2018 14:37:52 GMT</pubDate>
            <atom:updated>2018-11-01T17:46:34.707Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Chrome extension to make it faster and easier</h4><p>HTML5 video and video advertising are complicated technologies. They depend on a broad range of technical partners adhering to loosely standardized and often nascent systems that are constantly changing at the whim of the ever-changing tides of browser support and policies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*LPk6LyOGyQA7BUvWvGcJIA.png" /></figure><p>Our HTML5 player must work across the gamut of browsers to handle the range of content protection methods. It must also account for the different streaming types, file formats, and successfully digest and present content from a myriad of transcoding services. These services produce varying and sometimes incorrectly formatted renditions that cause players to stutter and break. Even more complexity is introduced when monetizing; ad networks, ad clients, and ad providers can produce a wide variety of XML VAST responses, which can lead to various errors.</p><p>This ecosystem is fragile and it can be hard to discern <em>where </em>and <em>why</em> things are not working. Fortunately, JW Player has a robust API, detailed analytics services, and an expressive event-system that, when used correctly, are a powerful set of tools. Without deep knowledge of these systems it can be overwhelming (as I know too well from my own first few weeks in the video space). Questions such as “where to look,” “what steps to take,” and “what questions to ask” are difficult to formulate and it’s often a challenge to locate exactly where in the chain something broke.</p><h3>Reducing Complexity</h3><p>Innovation is encouraged at JW Player and during our quarterly hackathon a few engineers and I started working on a product to increase accessibility by building an intuitive, comprehensive toolkit to debug and troubleshoot a JW Player instance. Our mission was to create a solution for <em>any user </em>to accomplish these goals:</p><ol><li>Make it easy to understand what a JW Player is doing on a page.</li><li>Increase the accessibility of the players’ rich feature set.</li><li>Reduce the barrier to consume the rich information it emits, and to distill our troubleshooting “best practices” into a simple click of a button.</li></ol><p>Some months later, we are now proud to present <strong>JW Lens</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-iOYSdI1GWPDhYB7HgqhQ.png" /></figure><h3>JW Lens</h3><p>JW Lens is a browser extension built using a combination of JW Player event listeners and API methods, browser API’s, Vue.js, and VueX. JW Lens provides users a tab-based interface offering a distinct set of features and functionalities. At a high level, these tabs provide the following functionality:</p><ul><li><strong>Overview</strong>: Provides high-level context of the JW Player instance and its implementation on the page. This includes the current media file URL, the player’s buffer health, and other similar information.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/0*5jNgFx3WzJH8NbJg" /><figcaption>Overview Tab</figcaption></figure><ul><li><strong>Config: </strong>Provides quick access to the configuration used to instantiate the player, and allows users to edit the configuration and re-initialize the player with a modified configuration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/0*t0DD1K4jtBWW6em2" /><figcaption>View and Edit Player Configuration</figcaption></figure><ul><li><strong>Troubleshooting: </strong>Provides a roll-up of errors (player errors, media errors, and ad errors), as well as configuration validation, providing instant feedback on your configuration, including any misused, invalid, or missing configuration options.</li><li><strong>Automated Ads Debugging: </strong>Refreshes the page a user-defined number of times, recording the ad performance for each “run”, and outputting a detailed report in a CSV file. This report includes summary information about the number of ad impressions and ad errors, as well as detailed information about each run, including specific ad error codes, and player bidding performance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/0*cwP8MtNsqc6MhAAl" /><figcaption>Troubleshooting Tab</figcaption></figure><ul><li><strong>Events: </strong>A filterable real-time feed of the events and accompanying data from the player.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*BlxXGC8YYy7kU0dm" /><figcaption>JW Player Events Feed</figcaption></figure><ul><li><strong>Analytics: </strong>A filterable real-time feed of analytics pings dispatched by Google Analytics, along with the accompanying data.</li><li><strong>QoE: </strong>Provides insight into the performance of the player and the page it lives on, providing player-specific metrics such as time to first frame, player setup time, and page “request to ready” measurements, as well as page-level metrics such as time to interactive, DOM load event, and DOM Content Loaded event.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ppR9VYnDs27dK13PfutYmw.png" /><figcaption>Player and Page QoE</figcaption></figure><ul><li><strong>Report: </strong>Quickly capture all information required by the JW Player Support team to troubleshoot your issues. Designed to send alongside with a support ticket to facilitate a more seamless support experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/0*1og7R1fPYOSqH5HR" /><figcaption>Generate a report for JW Support</figcaption></figure><ul><li><strong>Open Test Page: </strong>Enables you to quickly test production environment players in sanitized, ‘barebones’ environment (without any external CSS or JavaScript). This can help isolate whether the issue you encountered is due to an issue on the production page or the player itself. Reports outputted by the Report can be uploaded using the <strong>Upload Report</strong> button, opening the same barebones page from the information contained in the report.</li></ul><p><strong>Technical Hurdles</strong></p><p>During the development of JW Lens, we were faced with two overarching questions, how to make the interface as intuitive as possible and how to include more robust functionality within the context of an extension. Both of which our development team had little experience working in.</p><p>The first challenge we faced was determining whether we could use a JavaScript framework in the context of a browser extension. Not many of us had worked with Vue.js before, but with the project being born out of a hack week, we were excited to get some hands-on experience with the framework. In learning more about extension build packs, we turned to Webpack to quickly produce our first iteration, a ‘Hello World’ Vue application, giving us the foundation to start building out the functionality we were aiming to provide.</p><p>The next step was to start collecting the requisite data from the player instance on the page. In a typical debugging process, which relies heavily on the Chrome Developer Tools and test pages, this would simply involve setting up event listeners and calling any API methods as needed — standard JavaScript execution. In the context of a browser extension, however, this proved more difficult due to the nature of the browser’s architecture.</p><p>The two primary scripts that comprise an extension are the background and content scripts. These scripts live outside the context of the primary window, and do not share the namespace with the page. Because the namespaces were separate, we were unable to set up listeners for a player, or invoke the player’s API methods. We determined the workaround was to use script injection. While we could not set up listeners from the content or background scripts, we <em>could</em> access the document and append an additional script which would own these responsibilities. This script contained browser messaging which forwarded the relevant data back to the content script for sanitization, manipulation and rendering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVesIabsaxgswZ0QgWpxXQ.png" /><figcaption>Browser extension architecture and API’s used</figcaption></figure><p>Leveraging browser storage in an efficient manner was another hurdle, underpinning the behavior for the automated ads reports and the ‘barebones page’ functionality (a new page opens with only the selected player and it’s configuration, and nothing else in the DOM). Instead of relying on the browser’s local storage, extensions are given access to two different storage options — <em>storage.local</em> and <em>storage.sync</em>; both offer differing amounts of storage capacity while accessible through the same asynchronous API. With these solutions, we were able to better control application state, save data between window refreshes, and pass the pertinent information we needed to re-compose the player and accompanying detail in a new tab.</p><p>As we began to test our POC’s on our customer’s production sites, we quickly came to realize that we would also need to be <em>highly</em> specific in our CSS rules. There are JW Players on hundreds of thousands of domains, and our goal was to have the same experience on every one of those pages. To facilitate this process, we adopted LESS, to take advantage of its nested structure, allowing us to apply fine-grain detail to our elements while avoiding conflicts with customers’ CSS — something that, due to the number of sites we work across, we continue to refine today.</p><p><strong>What’s Next</strong></p><p>JW Lens is currently in a closed-beta, but we are excited with the progress we have made, and with the value its already provided to internal users, as well as publishers. As we look to what’s next, we want to continue to gather feedback from early adopters, and further tailor the extension’s functionality to adhere to our mission of increasing accessibility. Our aim is to replace the mundane of video troubleshooting with the automated, and surface “hidden gems” of information that the player already captures, but may not be easily identifiable.</p><p>We are also excited about the medium of this application. From our research, browser extensions are not a widely relied upon method of delivering this type of functionality, especially in this industry. We hope that the work we have done with JW Lens can open up doors for the development of other tools to make our product the most easily accessible for <em>any </em>user.</p><p>If you are interested in joining the trial for Lens and providing feedback and helping us plot the future of the application, please let us know and we will reach out to you for additional information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ddb58123ec3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jw-player-engineering/troubleshooting-html5-video-with-jw-player-2ddb58123ec3">Troubleshooting HTML5 Video with JW Player</a> was originally published in <a href="https://medium.com/jw-player-engineering">JWX Product &amp; Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>