<?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 Abhilash on Medium]]></title>
        <description><![CDATA[Stories by Abhilash on Medium]]></description>
        <link>https://medium.com/@abhilash-android-dev?source=rss-da4d0c2f77dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1MWFBHw4zqySzRBVhvSjDA.jpeg</url>
            <title>Stories by Abhilash on Medium</title>
            <link>https://medium.com/@abhilash-android-dev?source=rss-da4d0c2f77dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:16:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhilash-android-dev/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[Nested Scroll in Jetpack Compose: The Forbidden Curse (and How I Broke It)]]></title>
            <link>https://abhilash-android-dev.medium.com/nested-scroll-in-jetpack-compose-the-forbidden-curse-and-how-i-broke-it-a5d410c96a89?source=rss-da4d0c2f77dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5d410c96a89</guid>
            <dc:creator><![CDATA[Abhilash]]></dc:creator>
            <pubDate>Mon, 07 Jul 2025 04:14:10 GMT</pubDate>
            <atom:updated>2025-07-07T05:49:21.418Z</atom:updated>
            <content:encoded><![CDATA[<p><em>⚠️ </em><strong><em>Any Compose developer knows:</em></strong><em> having a </em><strong><em>scrollable container inside a scrollable container</em></strong><em> is a terrible idea.<br> Why?<br> Because it crashes. Spectacularly. 💥</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h8d4eX8ZGN9kscWpsjhzYg.png" /></figure><p>You’ll get something like this in your logs:</p><pre>Vertically scrollable component was measured with an <br>infinity maximum height constraints, which is disallowed. <br>One of the common reasons is nesting layouts like <br>LazyColumn and Column(Modifier.verticalScroll()). </pre><h3>🕵️‍♂️ The Problem I Faced</h3><p>Recently, I had a case where I <em>had to</em> put a LazyColumn inside a Scrollable Column.<br> And of course… putting it directly would lead to a crash. 😬</p><p>But I did what any stubborn developer would do — <br> <strong>Face the problem head on even after knowing there’s no solution.</strong></p><p>(<em>Maybe it’s just me and you’re all normal people. </em>😅)</p><h3>🔍 Looking into the Logs</h3><p>While peeking at the crash logs 📝, it became obvious:</p><p><strong>Issue:</strong></p><blockquote><em>Maximum height is going infinite ♾️.</em></blockquote><p><strong>Solution:</strong><br> 👉 Just set the max height.</p><p><strong>And boom — the curse is lifted. ✨</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*kIA0dGEB25wWJsXJUwOu7w.gif" /></figure><h3>😏 But Wait… My Case Was Different</h3><p>I didn’t want to force my users to manually set a max height on every LazyColumn they used.<br> That’s just a chore. 🥱</p><p><strong>Compose engineers had good reasons for this limitation</strong>, but I wanted to be a bit more… clever about it.</p><p><strong>What if the LazyColumn <em>(or a Scrollable Column for that matter)</em> worked safely, whether or not the user supplied a max height?</strong></p><h3>🪄 The Algorithm (It’s Simpler Than You Think)</h3><p><strong>if (crash_going_to_happen)<br> don’t.</strong></p><p>Yup, that’s it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*SGqJqhVeluCzdUsDknBhFQ.gif" /></figure><h3>💡 The Modifier Hack That Saved the Day</h3><p>I wrote a custom modifier to safely handle nested scroll crashes:</p><pre>fun Modifier.disableNestedScrollCrash(): Modifier {<br>    return this.then(<br>        Modifier<br>            .layout { measurable, constraints -&gt;<br>                val safeConstraints = if(constraints.maxHeight == Int.MAX_VALUE) {<br>                    constraints.copy(maxHeight = YOUR_MAX_HEIGHT_VALUE)<br>                } else {<br>                    constraints<br>                }<br>                val placeable = measurable.measure(safeConstraints)<br>                layout(placeable.width, placeable.height) {<br>                    placeable.place(0, 0)<br>                }<br>            }<br>    )<br>}</pre><h3>📌 Note:</h3><ul><li>YOUR_MAX_HEIGHT_VALUE can be whatever you want. I personally use Screen height as my max value.</li><li>Just <strong>don’t make it too big</strong> — remember <em>(Not a compose pun)</em>, in worst cases this will become the actual height of your LazyColumn 📏.</li><li>The more height you give, the less lazy your lazy column will be.</li></ul><p>✅ For nested scrolling in <strong>width</strong>, swap height variables with width.</p><h3>📸 Illustration of the Concept:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dKVSN3xKsDr3KAmm7AynmA.png" /></figure><h3>📝 One More Thing!</h3><p>This modifier trick isn’t just for LazyColumn inside ScrollView.<br> You can use it for <strong>any composable with a scrollable modifier</strong> too.</p><h3>📌 But like all modifier chaining rules in Compose — placement matters!</h3><h3>❌ Incorrect:</h3><pre>Modifier<br>    .verticalScroll(scrollState)<br>    .disableNestedScrollCrash()</pre><p>👆 <strong>Problem:</strong><br> This applies the max height constraint <strong>after</strong> the scroll modifier.<br> Meaning if your scrollable content is, say <strong>3000px</strong>, and you cap it at <strong>500px</strong> here — it’ll clip your content to 500px with no way to scroll the other 2500px.</p><h3>✅ Correct:</h3><pre>Modifier<br>    .disableNestedScrollCrash()<br>    .verticalScroll(scrollState)</pre><p>👆 <strong>This is the right way.</strong><br> Now the modifier sets a safe max height on the container, then the scroll modifier kicks in — allowing you to scroll the rest of the content smoothly.</p><h3>🎉 That’s It!</h3><p>I know it’s an unconventional solution to a niche issue — <br> but hey, if it works, it works. 👏</p><p>If you ever run into this, feel free to copy this trick and make your Compose layouts a little safer and lazier 😎.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/0*L8Jesu9OQ8Wdovx6.png" /></figure><p>☕ Enjoying the content? <a href="https://coff.ee/abhilashabbas">Buy me a coffee</a> to keep the ideas flowing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5d410c96a89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Native Date Picker in Compose]]></title>
            <link>https://abhilash-android-dev.medium.com/native-date-picker-in-compose-bfd6fa581d7c?source=rss-da4d0c2f77dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfd6fa581d7c</guid>
            <category><![CDATA[datepicker]]></category>
            <category><![CDATA[compose-ui]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android-date-picker]]></category>
            <dc:creator><![CDATA[Abhilash]]></dc:creator>
            <pubDate>Thu, 02 Nov 2023 07:04:20 GMT</pubDate>
            <atom:updated>2023-11-02T07:04:20.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*koOEKOnYMsbTKxnW" /><figcaption>Photo by <a href="https://unsplash.com/@erothermel?utm_source=medium&amp;utm_medium=referral">Eric Rothermel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Recently I came across a specific requirement in my view system project. I was customising theme in my app dynamically in runtime. This dynamic colors can be applied everywhere in my app except for one thing.</p><p>Top App Bar…. I was just kidding. You guessed it right. Date Picker.</p><p>I started to look for various projects in GitHub for these requirement. Then I became curious, “How hard is it to create it in compose, locale support and all?”. And that’s what prompted me to this.</p><p>A couple of disclaimers before going into the code.</p><ul><li>I know there are material date picker in compose, that looks and feels nice. But the UI in that is a bit different from that of traditional date picker. Since the users are accustomed to the age old UI ( and to satisfy my curiosity), I decided to create this.</li><li>I did not use <a href="https://developer.android.com/studio/write/java8-support-table">desugaring</a>. That is because of <a href="https://issuetracker.google.com/issues/261249836">this issue</a>. Basically the gist of the entire issue is that desugaring is not supported in library and I would like to use this code as a library in future.</li></ul><p>Now we can start from the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*AD9j7rPEDVcWY6Fx76rGFg.png" /><figcaption>Date Picker Header</figcaption></figure><p>The UI is as simple as it looks. Just two text composables that changes the state.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f69ad1dd49383cb7f8e828627a67b23c/href">https://medium.com/media/f69ad1dd49383cb7f8e828627a67b23c/href</a></iframe><p>The year should be formatted specific to locale. We can use NumberFormat for that. (Remember to replace any comma or special character from the formatted string.)</p><p>The text in the month is the tricky one. Remember we should also handle different locale.</p><blockquote>I have scoured the android open source code and there is a way to do the entire date picker without any API level restrictions in that open source code. Unfortunately, we cannot use that code. So I have used an amalgamation of native code that we can use and API’s from our dear old Calendar object in places we can’t accomplish this.</blockquote><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eabea369227c11563ff1798a66350064/href">https://medium.com/media/eabea369227c11563ff1798a66350064/href</a></iframe><p>I have used java.icu.text.DateFormat not to be confused with java.text.DateFormat.</p><p>The header part is over. Now the main content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*i4f3sfJhGoCjfjcbRWOIuA.png" /><figcaption>Month in Date Picker</figcaption></figure><p>The main content will of course be inside Horizontal pager. The item count of pager is the number of months to be shown in between start and end years. Following this, the current index position can also be found pretty easily.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d1c51b88e2d8d74c7aec794ad1b12408/href">https://medium.com/media/d1c51b88e2d8d74c7aec794ad1b12408/href</a></iframe><p>Now lets do the month header.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*5JXee-r-a2SoS8lZa5-dkw.png" /><figcaption>Month Header in Date picker</figcaption></figure><p>Yes again, the UI is as simple as it looks. We could do it easily. But the text is the tricky one. Fortunately we have simple solution for this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/84b75d4d8045a673efb65d0bd6c6e484/href">https://medium.com/media/84b75d4d8045a673efb65d0bd6c6e484/href</a></iframe><p>We can use YearMonth API to get the display name for any device on or above OREO. For others we can use the calendar API.</p><p>The icons on the side also should be handled for RTL locale, simply rotate it 180 degree if locale is RTL.</p><p>Next is the week days. Yes, you guessed it right. The UI is simple but locale handling gets a bit tricky. Fortunately we could get the first day of week from each locale from Calendar API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*MeObjVNyPDmrXwpAohhN1Q.png" /><figcaption>Week Days in Date picker</figcaption></figure><p>From that, getting the single lettered week text is just as we got the value for month text.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1de37b9021324e0649aa1f02bb76c872/href">https://medium.com/media/1de37b9021324e0649aa1f02bb76c872/href</a></iframe><p>Yippee…..</p><p>But now comes the hardest of them all. Dates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*xpq2PnKTmPfzhAP-rK8Bwg.png" /><figcaption>Dates in date picker</figcaption></figure><p>The grid of days in each month should start at the week day correctly and also be aligned correctly.</p><p>The total days of each month, the first day of week, the week day of the first day of month all can be retrieved from Calendar API.</p><p>The UI of rows and columns can be easily achieved.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ebc382f252dfa510b7df13e2cf4cc350/href">https://medium.com/media/ebc382f252dfa510b7df13e2cf4cc350/href</a></iframe><p>The day index where the month has to start can be calculated easily by having a list of week days in the order of that locale and getting the index of the first day of the month.</p><p>If that sentence is confusing, don’t worry here is the code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e78a4a7eda76aa826cd60b433691a3c/href">https://medium.com/media/1e78a4a7eda76aa826cd60b433691a3c/href</a></iframe><p>Now since we know when the month is going to start and end, we can get the locale formatted text for values and empty string for others.</p><p>Now the hard part is over. Next is dialog buttons (OK and Cancel).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*3P9M5txvO6BZ6C53nFUt7w.png" /><figcaption>Dialog Buttons</figcaption></figure><p>The UI is simple…. blah blah blah, you get the gist of it. We need locale specific text.</p><p>Luckily we don’t need to write strings.xml for each and every language for OK and Cancel.</p><p>We can find it ourselves by getting android.R.string.ok and android.R.string.cancel.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b39c14c47bd757e2c2f9de066448acb2/href">https://medium.com/media/b39c14c47bd757e2c2f9de066448acb2/href</a></iframe><p>Next is the final part I promise. It is the year picker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*n1_k3ResYINivhbd2A6YIw.png" /><figcaption>Year Picker</figcaption></figure><p>Now I would say UI is simple, locale handling gets tricky, but as far as I saw there is no locale handling for year picker, So you may add locale handling to year picker using the number format object if you want. But I am just going to add a Lazy Column with default numbers. Also don’t forget the separator at last.</p><p>Ah, but no part of date picker is without complication. We need to put that lazy column the same height as month picker. Easiest way to achieve this is static height for both. But call me lazy, I don’t want to check every android device in the world to see whether my UI breaks in any of that by doing the easy way. So I decided to go by the next best approach.</p><p>I got the height by getting it from <em>onGloballyPositioned</em> modifier and storing it in a state.</p><blockquote>Note: For any other component, we can just use IntrinsicSize for this exact requirement. But IntrinsicSize is not allowed for lazy column.</blockquote><p>So this is it. We have completed the date picker.</p><p>Any kind of feedback is highly appreciated.</p><p>GitHub Repo: <a href="https://github.com/V-Abhilash-1999/ComposeDatePicker">https://github.com/V-Abhilash-1999/ComposeDatePicker</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfd6fa581d7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Color Picker in Compose]]></title>
            <link>https://proandroiddev.com/color-picker-in-compose-f8c29744705?source=rss-da4d0c2f77dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c29744705</guid>
            <category><![CDATA[jetpack-compose]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[compose-ui]]></category>
            <category><![CDATA[android-development]]></category>
            <dc:creator><![CDATA[Abhilash]]></dc:creator>
            <pubDate>Sat, 20 May 2023 14:52:24 GMT</pubDate>
            <atom:updated>2023-05-25T08:13:17.821Z</atom:updated>
            <content:encoded><![CDATA[<p>For my first article in medium, I would like to start by showing you how to create a color picker in pure compose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c1bWiEMmu16Cv-TzZRLV-g.jpeg" /><figcaption><a href="https://www.pexels.com/photo/rainbow-830829/">Photo</a> by <a href="https://www.pexels.com/@frans-van-heerden-201846/">Frans van Heerden</a> on Pexels</figcaption></figure><p>Usually color pickers will have 3 components,</p><ol><li>Hue — The color of the picker</li><li>Saturation — The intensity of the color</li><li>Value — The lightness of the color</li></ol><p>We are going to have 2 panels. One will contain the hue selector and other panel will have both saturation and value in it.</p><p>First we will start by having hue panel. The output should look something like this.</p><p>(Since it would not look nice to have to write <em>android.graphics.Color</em> or <em>androidx.compose.ui.graphics.Color</em> in all the places that we use. We will import <em>android.graphics.Color as AndroidColor</em>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*FYe9YZj-a_OIgt4ron4AWg.png" /></figure><p>For that we would have to draw in canvas.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f0bb71d46980fa4aadffc434b0d5e21a/href">https://medium.com/media/f0bb71d46980fa4aadffc434b0d5e21a/href</a></iframe><p>We will be drawing this hue gradient in bitmap using <em>android.graphics.Canvas.</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/15a839ccf42c4930ff83894d9a98e83f/href">https://medium.com/media/15a839ccf42c4930ff83894d9a98e83f/href</a></iframe><p>Now we will split these colors across the width of the huePanel.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ec8ee32a232894d5ccc1a9994b1fe694/href">https://medium.com/media/ec8ee32a232894d5ccc1a9994b1fe694/href</a></iframe><p>Drawing each line of color in canvas would look like</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/824729bc6eb2c56039ee48f687579445/href">https://medium.com/media/824729bc6eb2c56039ee48f687579445/href</a></iframe><p>Finally drawing this into our compose canvas</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/92af4161727bfebab2f88b3afb79da3f/href">https://medium.com/media/92af4161727bfebab2f88b3afb79da3f/href</a></iframe><p>Next step is to have a offset state to observe where user is touching and drawing a circle to that area.</p><p><em>Note: We have to draw this circle after drawing bitmap, else it will just be overdrawn by bitmap.</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d2e93ff7e45c7bda4131c1a54ff67f2/href">https://medium.com/media/4d2e93ff7e45c7bda4131c1a54ff67f2/href</a></iframe><p>We have to send a callback for when hue is changed with click and also with drag.</p><p>Luckily we can not only get click position using InteractionSource but also send pressPosition to it. This way we only need to observe for it in one place.</p><p>We will write a custom Modifier to achieve this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cddeaa42371bd457b8861d4da9cbdbc2/href">https://medium.com/media/cddeaa42371bd457b8861d4da9cbdbc2/href</a></iframe><p>We have to observe for click and drag to find out exactly which hue is user picking.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9c81e8dd67c15da348d42128440587c9/href">https://medium.com/media/9c81e8dd67c15da348d42128440587c9/href</a></iframe><p>Now the hue panel is all set. After a little bit of cleaning code will look something like this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6df468908924c5e674c168f0288d631/href">https://medium.com/media/c6df468908924c5e674c168f0288d631/href</a></iframe><p>Next is a panel which is used to select saturation and value.</p><p>The basic upto creating a Canvas for bitmap is same as that of <em>HuePanel.</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6b0555bb5878a70e0696d795ac7a59b7/href">https://medium.com/media/6b0555bb5878a70e0696d795ac7a59b7/href</a></iframe><p>Since we are creating a panel that contains both saturation and value, we will create saturation gradient from top-left to top-right and value gradient from top-left to bottom-left.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ca25e29740cc3190bb91dee5bdadb5b/href">https://medium.com/media/3ca25e29740cc3190bb91dee5bdadb5b/href</a></iframe><p>The <em>rgb </em>value is calculated under the assumption that hue is passed to this composable.</p><p>Next we will draw a rounded rectangle by combining the <em>satShader</em> and <em>valShader</em> using <a href="https://developer.android.com/reference/android/graphics/ComposeShader">Compose Shader</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/45b6cc092cc6c941dee218317aa413de/href">https://medium.com/media/45b6cc092cc6c941dee218317aa413de/href</a></iframe><p>Drawing the Saturation + Value panel is over. Now we need to observe and draw a circle where our user will click/drag and then convert that position into saturation and value.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b13ba7ba21cfb8a9bd5e34b58288c53/href">https://medium.com/media/2b13ba7ba21cfb8a9bd5e34b58288c53/href</a></iframe><p>Finally our composable will look like this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b0fe06a961c04441a039cbe6da32c5de/href">https://medium.com/media/b0fe06a961c04441a039cbe6da32c5de/href</a></iframe><p>Getting value from both of those panel and set it where ever you like.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/80d7d628db73ed22f308828e5f7f888f/href">https://medium.com/media/80d7d628db73ed22f308828e5f7f888f/href</a></iframe><p>Our output will look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_JGtHBDTngG5vTOMpYAUA.gif" /><figcaption>Compose Color picker in Emulator</figcaption></figure><p>Any criticism is welcomed. Kindly post it in comments.</p><p>Check out the code at my github.</p><p><a href="https://github.com/V-Abhilash-1999/ComposeColorPicker">GitHub - V-Abhilash-1999/ComposeColorPicker</a></p><p>#HappyCoding</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c29744705" width="1" height="1" alt=""><hr><p><a href="https://proandroiddev.com/color-picker-in-compose-f8c29744705">Color Picker in Compose</a> was originally published in <a href="https://proandroiddev.com/">ProAndroidDev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>