<?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 Ross Beazley on Medium]]></title>
        <description><![CDATA[Stories by Ross Beazley on Medium]]></description>
        <link>https://medium.com/@rossbeazley?source=rss-7f8f0516b82------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iEemsYyjE6j5AMXbW6tALg.jpeg</url>
            <title>Stories by Ross Beazley on Medium</title>
            <link>https://medium.com/@rossbeazley?source=rss-7f8f0516b82------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:28:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rossbeazley/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[Updating ExoPlayer — a subtitle]]></title>
            <link>https://rossbeazley.medium.com/updating-exoplayer-a-subtitle-2b692612fed5?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b692612fed5</guid>
            <category><![CDATA[wiremock]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Tue, 04 Jun 2019 08:47:06 GMT</pubDate>
            <atom:updated>2019-06-04T08:47:06.143Z</atom:updated>
            <content:encoded><![CDATA[<h3>Updating ExoPlayer — a subtitle</h3><p>Hello <a href="https://medium.com/google-exoplayer/exoplayer-from-the-other-side-5909553abae2">again</a>, my name is Ross Beazley and I’m a developer in BBC Media Services. Our team within Media Services deal with integration of playback in the BBC mobile apps. I’ve been meaning to to write up some more on our ExoPlayer integration (its been three quarters of a year since the <a href="https://medium.com/@rossbeazley/on-updating-to-exoplayer-v2-and-how-we-test-our-integration-d06fe470ff3c">last post</a>), in this post I shall talk about subtitles. For the uninitiated, subtitles are words displayed on a piece of media that translate or transcribe the dialogue or narrative (remember 888 on your UK tv?). This article describes how we verify our integration of subtitles using ExoPlayer.</p><p>I’ve added another test in <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/F_ExoplayerStartsPlaybackOfSubs.java">F_ExoplayerStartsPlabackOfSubs.java</a>. If you take a look at the source you can see it’s essentially the same as <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/D_ExoplayerStartsPlaybackOfVideo.java">D_ExoplayerStartsPlaybackOfVideo.java</a>, we fire up ExoPlayer with our subtitles file and sample the colour that is output.</p><p>Much like you might engineer your environment to make the robots job easier, we do the same thing. We restrict the size of <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/F_ExoplayerStartsPlaybackOfSubs.java#L97-L99">ViewGroup</a> in which we render subtitles to 100px by 100px and use a <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/assets/streams/files/subs/some.ttml">subtitles file</a> that has quite a few lines of text so they fill the area. The subtitles themselves are styled in an unusual way. One set of subtitles has a <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/assets/streams/files/subs/some.ttml#L13">background colour and font colour of Red</a>, the other is <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/assets/streams/files/subs/some.ttml#L14">green</a>. By restircting the “view port” area, rendering lots of text and making forground and background colours the same we get an effect much like the Red/Green video from <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/D_ExoplayerStartsPlaybackOfVideo.java">D_ExoplayerStartsPlaybackOfVideo.java</a>.</p><p>We then <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/F_ExoplayerStartsPlaybackOfSubs.java#L111-L129">sample the colour</a> of the pixels on the screen and assert that the colours are correct for the current time in the stream. This is enough to assert that our integration of subtitles in ExoPlayer is correct.</p><p>I hope you find this of some use, wrangling with third party SDKs is something our team have to deal with daily and it’s important to know what is the appropriate type of test. Don’t test your third party SDK, test your integration of it.</p><p>As always, <a href="https://careershub.bbc.co.uk/members/modules/job/detail.php?record=40256">we are hiring</a>, so if you are a junior or entry level software engineer who is interested in developing their software test (read design) capability, drop me a line.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b692612fed5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using a bluetooth mouse with XFCE on Debian]]></title>
            <link>https://rossbeazley.medium.com/using-a-bluetooth-mouse-with-xfce-on-debian-2d43a661c5ca?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d43a661c5ca</guid>
            <category><![CDATA[bluetooth]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Fri, 31 May 2019 06:34:06 GMT</pubDate>
            <atom:updated>2019-05-31T06:35:08.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*z9qS19bVrPIaDRUW9u3ckQ.jpeg" /></figure><p>I got a bluetooth mouse and was actually amazed, after a quick bit of</p><pre>apt install bluetooth pulseaudio-module-bluetooth blueman bluez-firmware</pre><p>then opening up bluetooth manager I got my bluetooth mouse working first time!</p><p>I hit search after putting the mouse in pairing mode, it was discovered so i right clicked on it and selected pair.</p><p>Once paired I right clicked on it and selected setup, this allowed me to add it as a HID to the system.</p><p>I’m not much of a mouse user, but its kind of essential when playing minecraft with your <a href="https://www.youtube.com/channel/UC_bDLHpbk3KJehwXoZYWaZw">son</a> &gt;&lt;</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d43a661c5ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mixed arch kubernetes cluster]]></title>
            <link>https://rossbeazley.medium.com/mixed-arch-kubernetes-cluster-fbf155f57550?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbf155f57550</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Sat, 02 Mar 2019 19:59:44 GMT</pubDate>
            <atom:updated>2021-02-04T15:24:59.485Z</atom:updated>
            <content:encoded><![CDATA[<p>My notes for running on Raspberry Pi 2 (32bit os), 3(64bit os) and amd64.</p><p>It probably wont make sense to you.</p><p>with reference to <a href="https://gist.github.com/elafargue/a822458ab1fe7849eff0a47bb512546f">https://gist.github.com/elafargue/a822458ab1fe7849eff0a47bb512546f</a>/,.</p><p>On the Pi;</p><p>Install hypriot OS (64) using the flash tool</p><p>boot it and then</p><p>curl -s <a href="https://packages.cloud.google.com/apt/doc/apt-key.gpg">https://packages.cloud.google.com/apt/doc/apt-key.gpg</a> | sudo apt-key add - &amp;&amp; echo “deb <a href="http://apt.kubernetes.io/">http://apt.kubernetes.io/</a> kubernetes-xenial main” | sudo tee /etc/apt/sources.list.d/kubernetes.list &amp;&amp; sudo apt-get update -q &amp;&amp; sudo apt-get install -qy kubeadm=1.10.5-00 kubectl=1.10.5-00 kubelet=1.10.5-00</p><p>I use NFS for storage so install that also</p><p>apt-get install nfs-common</p><p>Something about disabling CNI on the master as shown here; sudo sed -i &#39;/KUBELET_NETWORK_ARGS=/d&#39; /etc/systemd/system/kubelet.service.d/10-kubeadm.conf</p><p><a href="https://gist.github.com/elafargue/a822458ab1fe7849eff0a47bb512546f/">https://gist.github.com/elafargue/a822458ab1fe7849eff0a47bb512546f/</a></p><p>Initialise the cluster but you need to increase the time out on the API starting up, i run this as soon as the yaml files appear:</p><pre>sudo sed -i &#39;s/failureThreshold: 8/failureThreshold: 20/g&#39; /etc/kubernetes/manifests/kube-apiserver.yaml &amp;&amp; \<br>sudo sed -i &#39;s/initialDelaySeconds: [0-9]\+/initialDelaySeconds: 360/&#39; /etc/kubernetes/manifests/kube-apiserver.yaml</pre><p>then multi arch the kube proxy as mentioned here</p><p><a href="https://masterofnone.io/spinupk8/">Install a multi-node ,multi-arch Kubernetes cluster using kubeadm in 30 mins!</a></p><p>Next up is multi arch flannel, use flannels yaml from their github repo</p><p>I then label all the arm nodes with arch.family=arm so you can deploy 32bit to 64bit archs using a node selector of arch.family: arm</p><p>I also use an internal (to the cluster) insecure registry so need to open that up to docker by</p><p>/etc/docker/daemon.json <br>{<br> “experimental”: true,<br>“insecure-registries” : [<br> “registry:30000”<br> ]<br>}</p><p>— — -</p><p>Update: Feb 2021 — I have been using K3S for ages now and works much better for my usecase. I recomend you use it over full blown kubernetes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbf155f57550" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Raspberry Pi Kodi and a cheap PCM5102a DAC]]></title>
            <link>https://rossbeazley.medium.com/raspberry-pi-kodi-and-a-cheap-pcm5102a-dac-7b70383477a8?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b70383477a8</guid>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[kodi]]></category>
            <category><![CDATA[openelec]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Sat, 16 Feb 2019 20:42:00 GMT</pubDate>
            <atom:updated>2019-02-16T20:42:00.413Z</atom:updated>
            <content:encoded><![CDATA[<p>I bought a cheap DAC so I could use my Pi to play music through my amp, I also use that Pi to play videos on my TV.</p><p>I followed this to get the DAC working</p><p><a href="https://blog.sengotta.net/connecting-a-pcm5102a-breakout-board-to-a-raspberry-pi/">Connecting a PCM5102a breakout board to a Raspberry Pi</a></p><p>And this to make music play through the DAC whilst videos still go through the HDMI</p><p><a href="https://forum.kodi.tv/showthread.php?tid=201896">AUTOMATIC (and/or manual) AUDIO SWITCHER for different Audio Output</a></p><p>Works well</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b70383477a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adventures with Pydio Cells and Kubernetes]]></title>
            <link>https://rossbeazley.medium.com/adventures-with-pydio-cells-and-kubernetes-b5d05d9fdd6b?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5d05d9fdd6b</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Sat, 08 Dec 2018 21:32:09 GMT</pubDate>
            <atom:updated>2018-12-22T19:25:45.976Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m no expert; I’m not even an amateur; I’m a novice Kubernetes user, this is a recording of the steps I took to “get Pydio Cells working” on my home mixed architecture Kubernetes five node cluster.</p><p>I may re-write into something understandable at some point!</p><p>I deployed Maria DB to a pi3 running a 64 bit hypriot os, I could only get Pydio to run against 10.1. As far as I could tell Mysql wasnt available on arm64 past version 5.5. I pulled the official image from dockerhub.</p><p>NFS was used to give storage for the pydio cells deployment.</p><p>The pydio cells docker image wasnt available for arm so I had to use an old intel core i3 laptop.</p><p>This was my deployment file:</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: pydio<br>spec:<br>  selector:<br>    matchLabels:<br>      app: pydio<br>  template:<br>    metadata:<br>      labels:<br>        app: pydio<br>    spec:<br>      nodeSelector:<br>        role: pydio<br>      containers:<br>      - image: pydio/cells:latest<br>        name: pydio<br>        env:<br>        - name: CELLS_BIND<br>          value: &quot;0.0.0.0:30010&quot;<br>        - name: CELLS_EXTERNAL<br>          value: &quot;0.0.0.0:30010&quot;<br>        command: [&quot;/bin/sh&quot;]<br>        args: [&quot;-c&quot;, &quot;/root/.config/pydio/cells/migrate_ips.sh&quot;] <br>        volumeMounts:<br>        - name: pydio-persistent-storage<br>          mountPath: /root/.config<br>        resources:<br>          limits:<br>            memory: &quot;2048Mi&quot;<br>            cpu: &quot;2.0&quot;<br>          requests:<br>            memory: &quot;1024Mi&quot;<br>            cpu: &quot;1.0&quot;<br>      volumes:<br>      - name: pydio-persistent-storage<br>        persistentVolumeClaim:<br>          claimName: pydio-claim</pre><p>In the first pass I have punched a whole out of the cluster using a NodePode to expose the pydio cells service.</p><p>I have ha-proxy running on my broadband router terminating the TLS traffic (thanks to lets encrypt) and this proxies the traffic to the pydio cells service that is listening on a clear http endpoint.</p><p>Getting clear http tripped me up a bit and i had to “jump through some hoops” to get it working.</p><p>Start off with TLS enabled, but then edit the pydio.json config file to disable:</p><pre>&quot;cert&quot;: {<br>    &quot;proxy&quot;: {<br>      &quot;self&quot;: true,<br>      &quot;ssl&quot;: false<br>    }<br>  }</pre><p>It was important to still have a cert, things didnt work with out it, go figure?</p><p>I also move from 0.0.0.0 to the public dns entry specifed in the deployment, again by editing the pydio.json file.</p><pre>&quot;defaults&quot;: {<br>    &quot;database&quot;: &quot;dcf9c3b7607c942aab9e2b0a0db91bb448f7b1cf&quot;,<br>    &quot;datasource&quot;: &quot;pydiods1&quot;,<br>    &quot;url&quot;: &quot;<a href="https://pydio.rossbeazley.co.uk/">https://some.public.url.co.uk</a>&quot;,<br>    &quot;urlInternal&quot;: &quot;<a href="http://0.0.0.0:30010/">http://0.0.0.0:30010</a>&quot;<br>  },</pre><p>Pydio storage was a real fiddle. When the cluster restarted or the POD was restarted it got a different IP. So for now I use a script to update the config file with the ipaddress of the POD on startup.</p><pre>#!/bin/sh</pre><pre>IP=`ifconfig eth0 | grep inet | awk &#39;{print $2}&#39; | sed &#39;s/addr://&#39;`</pre><pre>sed -i “s/PeerAddress\”:\ \“.*\”,/PeerAddress\&quot;:\ \“$IP\”,/g&quot; /root/.config/pydio/cells/pydio.json</pre><pre>/bin/docker-entrypoint.sh cells start</pre><p>And that’s it… I deployed collabora online to another node in the cluster. Bizarrely I couldn’t get it to edit files (always file not found) until I enabled debug logging…. go figure.</p><p>Next up, im going to work out how I can run each micro service in its own POD. For now i’m happy with a google free online docs system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5d05d9fdd6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On updating to Exoplayer v2 and how we test our integration]]></title>
            <link>https://rossbeazley.medium.com/on-updating-to-exoplayer-v2-and-how-we-test-our-integration-d06fe470ff3c?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/d06fe470ff3c</guid>
            <category><![CDATA[exoplayer2]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 13:56:31 GMT</pubDate>
            <atom:updated>2021-12-14T14:38:43.499Z</atom:updated>
            <content:encoded><![CDATA[<h3>On updating to ExoPlayer v2 and how we test our integration</h3><p>Hello <a href="https://medium.com/google-exoplayer/exoplayer-from-the-other-side-5909553abae2">again</a>, my name is Ross Beazley and some time ago I was a developer in BBC Media Services. The BBC Media Services team are responsible for the ingest, transcoding, packaging and IP delivery of all of the media content in the BBC. On the IP side, the BBC’s Standard Media Player (SMP) is used for playback of that media in our mobile and web applications — In essence SMP is the client SDK of Media Services.</p><p>At the start of the project in 2015, we used ExoPlayer at the core of our SMP implementation. We had fully embraced ExoPlayer, in the DDD (Domain Driven Design) parlance we were in a conformist relationship. ExoPlayer classes existed within the heart of our codebase and also appeared in our UI tier. Our tests were expressed in terms of ExoPlayer classes eg an action in our test might be ExoPlayer signalling READY or an assertion might be around the values dispatched to ExoPlayer’s seek method.</p><p>ExoPlayer now lives in its own subdomain, called a Decoder, and is adapted to conform to our model rather than our model conforming to ExoPlayer’s.</p><p>The design of SMP takes inspiration from <a href="http://wiki.c2.com/?HexagonalArchitecture">Hexagonal architecture</a>; “Decoder” is modelled as a port that we plug into different technology specific adapters — there is one for each type of media we play.</p><p>Leveraging this software design has allowed us to perform a phased roll out of ExoPlayer V2, slicing off each media type as we go; we started with the audio on-demand use case.</p><p>This article focuses on the techniques we use when developing a technology-specific adapter in a hexagonal-architecture style system.</p><h3>Adapters come in two parts</h3><p>In general we find our adapters are made up of two parts and a factory (or builder) to bring it into existence. The two parts are a plain old code object (POCO) and a very tech specific object: in the specific example of a AudioOnDemandDashDecoder we have:</p><p><em>1. An “API Narrowed” ExoPlayer 2 object.</em></p><p><em>2. Code that adapts the Decoder API calls and types into ExoPlayer API calls and types — an anticorruption layer between the two subdomains.</em></p><p><em>3 A factory that builds the object with the correct configuration for the media type.</em></p><p>With ExoPlayer V1 we had willingly disregarded the “Don’t mock what you don’t own” advice (some discussion <a href="https://8thlight.com/blog/eric-smith/2011/10/27/thats-not-yours.html">here</a>). Instead we spent time understanding how ExoPlayer behaved and encoded that in our own mock object. When integrating new releases of ExoPlayer this hand made mock object potentially needed updating.</p><p>This time, however, we a better understanding of media and how to encapsulate that understanding into tests — this has allowed us to integration-test our API-Narrowed ExoPlayer object. We can then use a mock version of this api narrowed object in our fast tests. The resultant behaviour of this mock, driven out through collaboration tests on the adapting side, defines the contract that the slow integration tests of the real ExoPlayer instance verify.</p><p>We are left with a set of very fast tests (milliseconds rather than seconds) to verify our adaption code. This slow/fast divide encourages us to keep the conditionals, complexity and other fun stuff in the adaption side (for more info on contract and collaboration tests refer to <a href="http://blog.thecodewhisperer.com/permalink/integrated-tests-are-a-scam">this JBrains article</a>). But how do you reliably integration test ExoPlayer?</p><h3>Integration testing ExoPlayer</h3><p><a href="http://wiremock.org/">WireMock</a> is one of the main technologies behind our integration tests. An instance of WireMock is embedded directly into an on-device connected test. It is used to serve DASH streams to ExoPlayer and simulate different network conditions for our ABR (adaptive bit rate) related tests. The assertions that our tests use include pixel colour sampling and audio sampling to verify things are playing.</p><p>The purpose of these tests is not to extensively test ExoPlayer works - the ExoPlayer team have spent a good amount of effort doing this. Instead they are to verify we have we integrated ExoPlayer correctly for the features we want. This is why I prefer the term “test of our integration” rather than “integration tests”.</p><p>What follows is a explanation of the example tests in this <a href="https://github.com/bbc/exoplayer-testing-samples">Github repository</a> and how we use them to verify a feature has been integrated correctly. At the time of writing there are five tests, A through to E. These verify that we can prepare a stream for playback, produce some audio, render some video and report on bitrate as we ABR up. This is not an exhaustive list but, for the purposes of this article, should illustrate to you some of the more interesting techniques to test your integration of media playback.</p><h3>Test A: <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/A_JustWireMock.java">Wiremock Setup</a></h3><p>Before we do anything, you will want to get WireMock working. You can see a basic WireMock test in <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/A_JustWireMock.java">A_JustWireMock.java</a>, it spins up WireMock (using the junit Rule), sends it a request and verifies the request is received.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/548cb9248a3c0560cb2369037407ba45/href">https://medium.com/media/548cb9248a3c0560cb2369037407ba45/href</a></iframe><p>You will also have to declare some WireMock dependencies in your modules <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/build.gradle">gradle</a> file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf15e4b4363e9d2594563e293789f1d5/href">https://medium.com/media/cf15e4b4363e9d2594563e293789f1d5/href</a></iframe><p>With this in place you can be sure your WireMock setup is correct and can move on to the fun stuff.</p><h3>Test B: <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/B_ExoplayerPreparesStream.java">ExoplayerPreparesStream.java</a></h3><p>The first part of our journey is preparing a stream for playback. The test asserts ExoPlayer has prepared our stream by asking WireMock to <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/B_ExoplayerPreparesStream.java#L61">verify</a> it received the request for the manifest (there are a few more things you can check but let’s just focus on this). In many ways this test will become redundant as we move on to starting playback, it’s up to you if you keep it or delete it.</p><p>This, however, requires us to introduce another WireMock technique, serving files. WireMock can serve files from a static folder, but on an Android phone this probably means the SD card. We have a WireMock <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/wiremockextensions/WireMockStaticFileFromRequestPathTransformer.java">Transformer</a> teamed up with an implementation of a <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/wiremockextensions/FileSourceAndroidAssetFolder.java">FileSource</a> to load files from the test assets folder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ebecb8402ce91d4eb95955f36690c032/href">https://medium.com/media/ebecb8402ce91d4eb95955f36690c032/href</a></iframe><p>We initialise the WireMockRule with this configuration and then create our stub mappings to always attempt to serve files matching the URL path.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c5532baa833533ef5cf241dcc4fab5e1/href">https://medium.com/media/c5532baa833533ef5cf241dcc4fab5e1/href</a></iframe><p><em>A little side note about the </em>FileSourceAndroidAssetFolder<em>; WireMock expects files to be in a </em><em>__files folder, the two underscores are stripped from the path before accessing the </em><a href="https://github.com/bbc/exoplayer-testing-samples/tree/master/app/src/androidTest/assets"><em>assets</em></a><em> resources as shown </em><a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/wiremockextensions/FileSourceAndroidAssetFolder.java#L49"><em>here</em></a><em>. The </em>streams<em> parameter maps to a </em><a href="https://github.com/bbc/exoplayer-testing-samples/tree/master/app/src/androidTest/assets/streams"><em>folder</em></a><em> (to keep things tidy) within the assets resources containing the WireMock </em><em>__files directory.</em></p><p>The test creates a new player for a given URL, waits for it to signal it’s ready and then verifies the request for the MPD was made.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8659c42c6b07692a8ade26b0c72e8e62/href">https://medium.com/media/8659c42c6b07692a8ade26b0c72e8e62/href</a></iframe><p>This may be enough to give you confidence that things are wired up correctly. You can continue to specify more assertions, but try not to over specify.</p><p>Next up we look at starting to play this stream.</p><h3>Test C: <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/C_ExoplayerStartsPlaybackOfAudio.java">ExoplayerStartsPlaybackOfAudio.java</a></h3><p>To be kind to the ears, an audio only stream with a 50hz tone is used in this test and things start getting interesting as we employ the use of an android.media.audiofx.Visualizer in our assertion.</p><p>xThe test follows on from the previous test, hence the setup is the same. The test creates a new Visualizer, enables capture of the output mix (the constructor parameter), plays for a bit and then grabs the FFT (Fast Fourier Transform) from the Visualizer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6fb3a0b37623cc71640746ff3a585637/href">https://medium.com/media/6fb3a0b37623cc71640746ff3a585637/href</a></iframe><p>For the purposes of this test we only check that sound is made, not what frequency bucket maxes out.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/67035e517ee296b61985920de44d887b/href">https://medium.com/media/67035e517ee296b61985920de44d887b/href</a></iframe><p>Actually, this implementation is wrong and should maybe be just adding up the real parts, but you get the point. Listen to this test fail by breaking your player.play() implementation, or rather see it go red then go green as you implement player.play().</p><p>The test hooks into the output mix rather than the specific audio session. Accessing the output mix requires the RECORD_AUDIO and MODIFY_AUDIO_SETTINGS permissions, we use the GrantPermissionRule from Android’s test support libs.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8ef21e0243bd03d9f057f917063dc7b2/href">https://medium.com/media/8ef21e0243bd03d9f057f917063dc7b2/href</a></iframe><p>You can expose the local audio session ID if you like to avoid this permissions problem, give it a (test first) go!</p><h3>Test D: <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/D_ExoplayerStartsPlaybackOfVideo.java">ExoplayerStartsPlaybackOfVideo.java</a></h3><p>Now to add video playback. For this test we are going play a short video clip of less than 8 seconds. It first displays a full frame of red and then changes to green. The setup for the test is slightly different and we need to spin up an activity into which we inject a TextureView. We can then sample the pixel colour in the TextureView and assert on its green-ness. Aside from that it’s basically the same, declare WireMock stubs for a locally hosted stream and begin playback.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d6e80ebf6859f87243c5661e3f1adb5/href">https://medium.com/media/0d6e80ebf6859f87243c5661e3f1adb5/href</a></iframe><p>We use an ActivityTestRule to start our Activity (its declared in the <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/AndroidManifest.xml#L5">Test AndroidManifest</a>).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd96a5fde9c22ab16dda0c9063fb136c/href">https://medium.com/media/dd96a5fde9c22ab16dda0c9063fb136c/href</a></iframe><p>And set its content view to the newly created TextureView. When its SurfaceTexture is created attach a Surface made from this to the player.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/77f12f7b0d902aa02b5c162bbbd323ca/href">https://medium.com/media/77f12f7b0d902aa02b5c162bbbd323ca/href</a></iframe><p>The test lets the video play for some time and samples the colour of the pixel at coordinate [100, 100] asserting its colour is <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/D_ExoplayerStartsPlaybackOfVideo.java#L78-L80">GREEN</a></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ab132e376b370225e32d543f16554b92/href">https://medium.com/media/ab132e376b370225e32d543f16554b92/href</a></iframe><h3>Test E: <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/E_ABRsThroughRepresentations.java">ABRsThroughRepresentations.java</a></h3><p>The test covers two features in one go. We are going to check we have enabled ABR for our streams and also that the player reports the bitrate it’s playing back. Actually, we are going to use the reported bitrate to confirm ABR is working. If that makes you fall off your seat then we could do more, for example check what segments have been requested from WireMock, or have a stream with a different colour for each representation and sample those colours.</p><p>The test starts playback and uses a journalling listener to capture the reported bitrates. The test waits until playback has stepped up three rungs on the ABR ladder, or a maximum time based on the segment length.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3a2bf3fa25540be842808e629d3ae3a7/href">https://medium.com/media/3a2bf3fa25540be842808e629d3ae3a7/href</a></iframe><p>The test uses a feature of WireMock called ChunkDribbledDelay. With this we can deliver each segment in 1KB blocks over a known timeframe, in essence this allows us to restrict the network connection to a specific bitrate. This bitrate increases over time — i.e. if later segments can be delivered faster, ExoPlayer ABRs up.</p><p>The implementation of this is not ideal, <a href="https://github.com/tomakehurst/wiremock/issues/957">at the moment</a>, and is mostly buried in the <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/exoplayertestingsamples/E_ABRsThroughRepresentations.java#L53">setup of the stubs</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3fe3c7506dc6dc0d97c7d02930410a99/href">https://medium.com/media/3fe3c7506dc6dc0d97c7d02930410a99/href</a></iframe><p>A <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/wiremockextensions/WireMockStaticFileFromRequestPathTransformerWithChunkedDelay.java">transformer</a> very similar to the existing static file version is used to apply the bandwidth restriction. The application of the bandwidth restriction all hinges around the use of <a href="https://github.com/bbc/exoplayer-testing-samples/blob/master/app/src/androidTest/java/wiremockextensions/WireMockStaticFileFromRequestPathTransformerWithChunkedDelay.java#L74">withChunkedDribbleDelay</a>. The method takes two parameters: number of chunks and time taken to deliver those over the network. When the file is loaded from disk the number of 1KB chunks is determined and the length of transfer time to meet the bps (bits per second) is calculated.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aac4bad8a3786e8aae3d6a7c830cad45/href">https://medium.com/media/aac4bad8a3786e8aae3d6a7c830cad45/href</a></iframe><p>The test assumes the later segments can be delivered over a faster network, it uses some very crude string comparison of the name to work this out. I’m sure you could do a much better job.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/12553799f70100cf95b06bcb1995d29d/href">https://medium.com/media/12553799f70100cf95b06bcb1995d29d/href</a></iframe><p>So to wrap up, when dealing with technology specific integrations try not to fall into the trap of testing the features but rather your integration of the feature. You will need to know how the underlying technology works in order to setup the test context. I hope you have been inspired by something you have read here and can apply this to other problems you face during your development career.</p><p><a href="https://medium.com/@rossbeazley/updating-exoplayer-a-subtitle-2b692612fed5">Read more about how we integrated subtitles.</a></p><p><strong>** UPDATE ****</strong></p><p>Having moved to pastures new to work on their player integrations I have had to re-implement some of this.</p><p>I now use this wiremock dependency as it does not need any legacy apache http client workaround;</p><p>androidTestImplementation &quot;com.github.tomakehurst:wiremock-standalone:2.26.3&quot;</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d06fe470ff3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bootstrapping Arduino ESP8266 with OTA]]></title>
            <link>https://rossbeazley.medium.com/bootstrapping-arduino-esp8266-with-ota-731ddbfe4b98?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/731ddbfe4b98</guid>
            <category><![CDATA[esp8266]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[arduino]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Sun, 14 Jan 2018 20:29:36 GMT</pubDate>
            <atom:updated>2018-01-14T20:29:36.983Z</atom:updated>
            <content:encoded><![CDATA[<p>These days the first thing I upload to my esp8266 is an Arduino OTA implementation (I have it wrapped up in one class that responds to a loop message), this means no more serial port required and I can leave the board plugged in out of the way. Especially useful for Sonoffs, means I can get them deployed early.</p><p>I use this command on linux to find the arduino to update</p><h4>avahi-browse -t -r “_arduino._tcp”</h4><p>with output similar to</p><h4>+ wlp1s0 IPv4 corner _arduino._tcp local<br>= wlp1s0 IPv4 corner _arduino._tcp local<br> hostname = [corner.local]<br> address = [192.168.10.127]<br> port = [8266]<br> txt = [“auth_upload=no” “board=generic” “ssh_upload=no” “tcp_check=no”]</h4><p>this gives me the hostname so then I can use this platform io command to flash the board</p><h4>platformio run — target upload — upload-port corner.local</h4><p>or i can use the IP instead of the hostname</p><h4>platformio run — target upload — upload-port 192.168.10.127</h4><p>job done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=731ddbfe4b98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some thoughts on a chromecast connected test runner]]></title>
            <link>https://rossbeazley.medium.com/some-thoughts-on-a-chromecast-connected-test-runner-fda602a2f185?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda602a2f185</guid>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[chromecast]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Tue, 19 Dec 2017 08:46:39 GMT</pubDate>
            <atom:updated>2017-12-19T10:39:49.262Z</atom:updated>
            <content:encoded><![CDATA[<p>Our go to architecture is often a <a href="http://alistair.cockburn.us/Hexagonal+architecture">ports and adapters (hexagonal) architecture </a>where we have a plain old code application core and technology specific adapters around the edge glueing our app into the real world. We are very comfortable testing technology specific adaptors on other systems like s3, android views, most of the ios bits, crud operations on databases etc etc; but when it comes to chromecast we are seriously lacking.</p><p>Our chromecast receiver still conforms to a hexagonal design but in the case of the cast sdk adapters we have gone down the path of <a href="https://8thlight.com/blog/eric-smith/2011/10/27/thats-not-yours.html">“mock classes you dont own”.</a> So its all just a little bit risky, it gave us confidence at the time — but with a half life.</p><p>One thought Ive had is around using the sender sdk in a headless chrome coupled with a “test runner” receiver. I think i could serialise commands and responses over the wire using custom message channel. Therefor we could load tests into the reciever, execute them and report results back to the client.</p><p>If I have time, or I can inspire anyone out there to have a go, ill report back with results.</p><p>I think the first thing to try would be boot strapping a simple test with one assertion in it.</p><p>Then next up would be actually sending through normal media style commands like a load operation.</p><p>Anyway, if you want to give this a go, drop me a line!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda602a2f185" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ExoPlayer from the other side]]></title>
            <link>https://medium.com/google-exoplayer/exoplayer-from-the-other-side-5909553abae2?source=rss-7f8f0516b82------2</link>
            <guid isPermaLink="false">https://medium.com/p/5909553abae2</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[exoplayer]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Ross Beazley]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 19:04:04 GMT</pubDate>
            <atom:updated>2017-03-01T12:14:20.443Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Ross Beazley and I work for the BBC in the Mobile Platforms team. Mobile Platforms make components and libraries for many of the BBC’s mobile apps including the BBC’s Standard Media Player (SMP). SMP is used for the playback of unencrypted BBC content and at its core, on Android, uses ExoPlayer.</p><p>So why did we opt to use ExoPlayer? The BBC’s strategic direction for media streaming on TVs, Desktop and Mobile is to move towards the streaming technology DASH (and specifically the DVB DASH, see <a href="http://www.dvb.org/resources/public/standards/a168_dvb-dash.pdf">document A168</a><a href="https://www.dvb.org/resources/public/standards/a168_dvb-dash.pdf).">)</a>. ExoPlayer fits in well with this strategy as it supports the sort of DASH streams the BBC <a href="http://www.bbc.co.uk/rd/blog/2013-09-mpeg-dash-test-streams">produces</a>.</p><p>This post is about a few of the things we did to use ExoPlayer (version 1) for some of the BBC’s use cases. As it happens, during the writing of this post the ExoPlayer v2 branch became <a href="https://medium.com/google-exoplayer/exoplayer-2-x-its-here-plus-faqs-cce34b0d4c7b#.108fjic04">stable</a>, however reading this may still be of use. If you are interested in reading more about SMP you can do so on the BBC blogs <a href="http://www.bbc.co.uk/blogs/internet/entries/768ae4f2-7933-42d7-9a12-c71dfacf12b6">here</a>.</p><p>ExoPlayer comes with a large number of useful parts, much like a box of Lego, and it is up to you how you plug all these bits together. But before we get bogged down with detail it’s worth just understanding what the BBC wants from the standard media player.</p><p>SMP, for our clients like iPlayer, should:</p><p>1. Be trivial to use,</p><p>2. Play both on-demand (catch-up) and live content (like BBC1),</p><p>3. Seek forwards and backwards through a stream,</p><p>4. Transition from embedded to fullscreen,</p><p>5. Monitor quality of service,</p><p>6. Integrate playback with Chromecast,</p><p>and many many other features.</p><p>Most of these features require integrations with ExoPlayer and I hope by summarising a couple of these here they may be of use or inspiration to you on your journey.</p><p>What follows describes a) how we modelled “media time” in the system (and thus implemented seeking) in a way that unifies live and on-demand streams, and b) managed the async lifecycle of the UI.</p><h3>Modelling On-demand Media Time</h3><p>At any point you can query ExoPlayer for the current playback position and duration of the stream. For SMP we wanted to simplify things for our clients (of which our player UI is an example), and so we made time an observable property. This property combined playback position and duration, in essence a MediaPosition coordinate, from ExoPlayer. You may argue that duration was not something that really changed with an on-demand asset and thus is inefficient, but stick with it and I hope all will become clear.</p><p>SMP uses a ScheduledExecutorService to poll ExoPlayer for playback position and duration changes. Observers held in a collection are notified of the new values using the single MediaPosition object. We used a CopyOnWriteArrayList to hold observers. The majority of operations on this collection are reads and this Collection type avoids concurrent modification exceptions if we add or remove an observer during event propagation. The frequency of polling was a tune-able SMP parameter and could be overridden at construction time if required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*8ihQZsKRIXmrOO2LfnRwmQ.png" /></figure><p>The MediaPosition could now be bound to our seekbar, allowing the player UI (or any client) to dispatch seeks to SMP. At this point, support for the on-demand use case was complete.</p><h3>Modelling Live Media Time</h3><p>Unlike on-demand, which has a duration, live playback has a “rewind window”. This means its default position when playing is the “live edge” — the latest point in the stream, the opposite for on-demand. If you start watching BBC One you start watching what’s on TV right now and have the option to rewind the stream back in time. The BBC only keeps about two hours’ worth of media for its live streams available i.e. a two hour rewind window. ExoPlayer can report the availability of this rewind window and we shall go into this in a little more detail in just a moment. Therefore a live stream has a current position, an end time and a start time and these values in general always increase with the passage of time.</p><p>In order to keep things simple SMP would like to present the same MediaPosition object for live playback, as really it is the same observable time related state in the system. The only real difference between on-demand and live is the assumption that on-demand starts at a position of zero and the duration is really the end time of the stream. With a little property renaming to remove this “starts at zero” assumption we can use the same MediaPosition object for both on-demand and Live playbacks. Our MediaPosition object now looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/103/1*ZZyxMXRmYxoDIYCDzkVzyA.png" /></figure><p>But how do we create a MediaPosition object for a live stream? We have a little more work to do with ExoPlayer. The current position is still read from the main ExoPlayer instance but to calculate the stream start and end time requires us to use a new DashChunkSource.EventListener attached to our DashChunkSource. This listener will be notified when there is a change in the size of the rewind window giving us the current start and end times (in milliseconds since the epoch). We then calculate the size of the rewind window, and the live edge latency (the difference between the end time of the stream and the current time).</p><p>When a “live” MediaProgress object is created we determine the EndTime by subtracting the live edge latency from the current system time. The start time is simply the end time less the rewind window. The current position is simply read from ExoPlayer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/0*MeWoT823BX1FnyI1." /></figure><p>This MediaProgress object can be bound into our seek bar in the same way as for on-demand. This allows us to seek within live and on-demand streams in the same way. So just as James Clerk Maxwell unified electricity and magnetism into one force, we have unified our concept of time into one object — ok so maybe not as grand, very tenuous and certainly less useful.</p><p>Now that we have time and seeking sorted; we turn our attention to the UI and displaying video.</p><h3>Asynchronous UI</h3><p>SMP, like ExoPlayer, can be either run headless or with our UI on display. To support this we expose a method to attach or detach a surface to SMP. Before I go into how (and why) this implemented I shall explain a) how our default transition to full-screen action is performed and b) how we manage a “video card” list.</p><h4>Transition to full-screen</h4><p>When an “embedded” playout view is used in an app (you know, like YouTube when it’s not fullscreen) a surface is created and this is ultimately sent (in a message) to the ExoPlayer video track renderer. When the switch to fullscreen button is pressed we fire up a new fullscreen activity, inject the SMP instance using an Application.ActivityLifecycleCallbacks listener, and create a new playout view for the activity. This again results in a surface being created and sent to the video track renderer. This replaces the previous surface sent to the video track renderer by the embedded view. When the fullscreen activity is closed, its surface is detached from SMP and playback should continue on the “embedded” playout view.</p><h4>Video Card List</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/143/1*SY2ews0DMwUjmridOyQ4nw.png" /></figure><p>SMP supports the use of multiple views on a single instance. This is how we implement a video card list. A different piece of content is displayed in each view and only one piece of content can play at any time. Pressing play on a card results in a surface being created and attached to SMP. If playback is initiated on another card a surface is created and attached to SMP and the surface in the other card is detached and destroyed. SMP makes no assumptions about what order this may happen in.</p><h4>Surface Stack</h4><p>We maintain a stack of surfaces that have been attached to SMP. When a surface is attached to SMP we push it onto the top of the stack and when that UI is removed and surface destroyed it is detached from SMP and is popped off the stack.</p><p>The surface at the top of the stack is the one attached to the video track renderer, when the top surface is popped (removed) we attach the new top of the stack to the video track renderer. This might be null of course if the stack is now empty which results in the video decoder getting disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*Evh5E3fj17ATZqzZY_r18w.png" /></figure><p>This solution covers both the embedded, fullscreen and video card list use cases. It also allows us to move towards an enhanced secondary screen experience when you plug in an HDMI cable, the TV showing the main video content and controls remain on the main SMP UI.</p><p>This article has covered only a small number of the ways we use ExoPlayer and if time permits I will follow up with more details including what we learned on our transition to ExoPlayer 2.x, how we decoupled ourselves from ExoPlayer, how we shaped our acceptance test suite, how we avoided conditionals with a “one class per state” FSM and the benefits (and pitfalls) or raising domain events on a global event bus.</p><p>If you are interested in reading more about building mobile components for media playback at the BBC please head over to our technical <a href="http://www.bbc.co.uk/blogs/internet/entries/768ae4f2-7933-42d7-9a12-c71dfacf12b6">blogs</a>. If you want to get stuck in to building mobile components for media playback, the BBC needs you — drop me a line.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5909553abae2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-exoplayer/exoplayer-from-the-other-side-5909553abae2">ExoPlayer from the other side</a> was originally published in <a href="https://medium.com/google-exoplayer">AndroidX Media3</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>