<?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[Phytochemia Tech Blog - Medium]]></title>
        <description><![CDATA[Phytochemia tech blog - Medium]]></description>
        <link>https://medium.com/phytochemia-tech-blog?source=rss----5657d1231ca0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Phytochemia Tech Blog - Medium</title>
            <link>https://medium.com/phytochemia-tech-blog?source=rss----5657d1231ca0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:42:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/phytochemia-tech-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[3 Simple ideas to use Slackbot responses in a relevant way]]></title>
            <link>https://medium.com/phytochemia-tech-blog/3-simple-ideas-to-use-slackbot-responses-in-a-relevant-way-64de42cf78e0?source=rss----5657d1231ca0---4</link>
            <guid isPermaLink="false">https://medium.com/p/64de42cf78e0</guid>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[slack-tips-and-tricks]]></category>
            <dc:creator><![CDATA[Kim Desrosiers]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 12:45:29 GMT</pubDate>
            <atom:updated>2022-02-18T13:48:40.189Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*qHx1_dKtRhBPfPX9i2ofWQ.png" /></figure><p>Foremost, if you don’t know what is <a href="https://slack.com/">Slack</a> you must definitively try it now. Slack is a cross-platform communication tool that is simple and efficient. At Phytochemia, we are using Slack for our day-to-day communications and we love it.</p><p>Slackbot what is that? It is the default bot provided by the Slack team. Basically, it handles simple tasks such send a message asking you to complete your profile or send a message when something important happens to your Slack’s workspace (<em>Since September 5 the Slack team renamed “Team” to “Workspace”</em>).</p><p>Moreover, Slackbot has responses that can be triggered by a list of words. For example: If someone writes “Hello Slackbot” we can configure a response that makes Slackbot reply with “Hello to you”.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FASd0Ukj0y3qMM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FASd0Ukj0y3qMM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FASd0Ukj0y3qMM%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/bff4a5a0401d9568349689ff44e2c77b/href">https://medium.com/media/bff4a5a0401d9568349689ff44e2c77b/href</a></iframe><p>Awesome! But how can we take profit of this feature in a relevant way?</p><h4>1. WIFI password reminder</h4><p>Are you tired to tell the WIFI password to new employees or each time someone is not able to remind it on his own? Let Slackbot do it for you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*hPxMCXfhYXQoyCjryBZE_w.png" /><figcaption>Thank you Slackbot</figcaption></figure><h4>2. Help new employees to find a good person for the situation</h4><p>We have all been a new employee. When we start in a new company, it is not always easy to know who is in charge of what. You can use Slackbot to help with that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*tERkxe8M6GButX4mpVrvhw.png" /><figcaption>Unfortunately, it is me :(</figcaption></figure><h4>3. To choose randomly</h4><p>Drawn the short straw can be boring and you need to disturb everyone from their work to draw the straw. Why not let Slackbot do it for us? It is possible to set many possible responses to a triggered message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*z4O_jkFlmAgHawC679-FuA.png" /></figure><h3>The wrap-up</h3><p>As we have seen no need to be a software developer to add some dynamic to our slack workspace. I hope this little post will help you to have other great ideas to use with Slackbot.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64de42cf78e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/phytochemia-tech-blog/3-simple-ideas-to-use-slackbot-responses-in-a-relevant-way-64de42cf78e0">3 Simple ideas to use Slackbot responses in a relevant way</a> was originally published in <a href="https://medium.com/phytochemia-tech-blog">Phytochemia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Docker can improve your development environments]]></title>
            <link>https://medium.com/phytochemia-tech-blog/how-docker-can-improve-your-development-environments-731cdfda0b9a?source=rss----5657d1231ca0---4</link>
            <guid isPermaLink="false">https://medium.com/p/731cdfda0b9a</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Kim Desrosiers]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 14:35:38 GMT</pubDate>
            <atom:updated>2019-06-17T15:58:18.789Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Disclaimer: I want to clarify that I won’t cover any good practices with Docker in production. I will talk about development environments improvement using Docker.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*uoHYxwC8IPQhjmVK0LXM2w.png" /></figure><p>Development environments are not always easy and simple to setup. Especially with complex projects using micro services or external dependencies. For example, with a trivial backend project, you have a good chance of having to setup a local database and even a local message broker for your development needs.</p><p>For the purpose of this post, we will define a little project that has some dependencies. The project will be named “WishlistManager” and use Python and Flask. Then we’ll use PostgreSQL and Redis as the message broker. Here we go, we have our little project to set up locally.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FDgLsbUL7SG3kI%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FDgLsbUL7SG3kI%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FDgLsbUL7SG3kI%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="365" frameborder="0" scrolling="no"><a href="https://medium.com/media/efcb129e2adfd950bb05fef940c743b7/href">https://medium.com/media/efcb129e2adfd950bb05fef940c743b7/href</a></iframe><h3>Without Docker</h3><p>What we need to do if we choose to not use Docker.</p><ol><li>Install PostgreSQL, Redis and Python manually or with a script. Depending on the OS, this can be tricky sometimes.</li><li>Configure each dependency. For example, we need to create a PostgreSQL database user.</li><li>Start dependencies daemons.</li><li>Begin to code!</li></ol><p>Not so bad after all. However, there are some drawbacks to this setup.</p><ul><li>All services are installed system wide. So, if I need to upgrade PostgreSQL for a project I can break another one.</li><li>It can be a mess for your development setup documentation since you need to handle different OS and Package managers. For example, configuration files locations change according to OS or even Distros.</li><li>It is time-consuming. Taking into account the two previous points, if you have 15 developers, they will have to repeat all steps to setup their environment.</li><li>You can’t ensure that everybody has exactly the same version of each dependency. One developer might install PostgreSQL 9.4 instead of 9.5 by mistake and you realize it when this developer commits something that is no more supported.</li></ul><p>Unfortunately, I want to keep my project setup simple and quick as it will get bigger. Thus, this is where Docker helps us.</p><h3>With Docker</h3><p>In order to simplify and isolate our development environment, we will use Docker. However, you need to know the basics of Docker of course. <a href="https://docs.docker.com/get-started/">The official documentation of docker</a> is a good starting point to learn the terminology and the basics.</p><p>Here are some quick definitions of important terms related to Docker to help you understand the next part:</p><p><strong>Image —</strong> A binary file that includes everything needed to run a Docker <strong>container</strong>, including metadata describing capabilities and dependencies.</p><p><strong>Container —</strong> A runtime instance of a Docker <strong>image</strong>. Multiple containers can run concurrently using the same Docker image.</p><p><strong>Dockerfile —</strong> A text document that contains the execute commands needed to build a Docker <strong>image</strong>. An image is produced from a Dockerfile using the <strong>docker build</strong> command.</p><p><strong>Compose — </strong>A tool for defining and running multi-<strong>container</strong> applications. The containers are all defined and configured from data in a single file. All the containers can be started or stopped with a single command.</p><p>To be honest with you the Docker way requires more work and time the first time in order to install and setup the Docker stuff but this is for a good reason.</p><p>Here’s what you need to do to use Docker:</p><p>First, install Docker, of course, and Docker-Compose. <strong>Note</strong>: for Windows and Mac there is a little difference but <em>Docker for Mac</em> and <em>Docker for Windows</em> are there to fix that.</p><p>Then, create a file named <strong>docker-compose.yml</strong>. By the way, I always use <a href="https://docs.docker.com/compose/">Docker-Compose</a> to simplify my multi-containers setups and I encourage you to do so to avoid unnecessary complexity. I will explain how to use it.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/105f414581c0b9112e6aaab84090d1be/href">https://medium.com/media/105f414581c0b9112e6aaab84090d1be/href</a></iframe><p>Finally, create a <strong>Dockerfile </strong>(if needed). Why if needed? Some of my basic projects, especially Python projects, don’t really need a Dockerfile since I use Python virtualenvs to isolate my python setup. However, it is always possible to replace a virtualenv with a Docker container.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f55de8c7229f1c909b28287e10219f09/href">https://medium.com/media/f55de8c7229f1c909b28287e10219f09/href</a></iframe><p>What is actually happening? Basically, Docker-Compose helps us by simplifying the definition of our services. In one file we can define for each service which Docker image will use, port mapping, volumes mapping, environment variables and more. The Dockerfile allows us to create a custom Docker image from an existing one with our application data.</p><p>From there if we want to create and start the containers we just need to run the following command:</p><pre>docker-compose up</pre><p>Then, according to our example, you should be able to access to your app at <em>localhost:5000. </em>PostgreSQL and Redis are available from your system without having to enter in Docker containers since we mapped their port to local ones.</p><p><strong><em>Note</em></strong><em>: Giving that Docker creates a virtual local network for the containers communication, your python container will be able to connect to PostgreSQL by using its service name as IP. For example: in my app config the database address will be set to: “postgres”.</em></p><p>If we want to stop our containers we run the following command:</p><pre>docker-compose down</pre><p>Furthermore, <a href="https://docs.docker.com/compose/">Docker-Compose</a> gives us many others features that I didn’t cover in this blog post. Once again go read its documentation it’s worth it.</p><p>Thus we have our Docker version. Although we have to learn the basics of Docker and it requires a little more scaffolding, I think this setup has some advantage on the previous one.</p><ul><li>Quick setup. You need to setup somebody quickly, just clone the repository, install Docker and Docker-compose then run <em>docker-compose up</em></li><li>A consistent development environment. It does not matter which OS you use everybody has the same libraries, language runtime etc</li><li>Isolated. I might run 20 different PostgreSQL versions and everything will be alright (My CPU and my RAM will be angry but yeah I might)</li><li>Makes it easy to use automated test tools such Continuous Integration(CI)</li><li>You have only one setup to document</li></ul><h3>In Conclusion</h3><p>As we have seen above, setup without Docker isn’t too bad but there are some drawbacks to take in consideration. On the other hand, using Docker involves that we need to learn the basics and we have a little more scaffolding but it gives us a more robust environment. Once you are comfortable using Docker you will be tempted to use it in production.</p><p>I encourage you to learn advanced features of Docker to be able to get the maximum power of it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=731cdfda0b9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/phytochemia-tech-blog/how-docker-can-improve-your-development-environments-731cdfda0b9a">How Docker can improve your development environments</a> was originally published in <a href="https://medium.com/phytochemia-tech-blog">Phytochemia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we chose Vue.js]]></title>
            <link>https://medium.com/phytochemia-tech-blog/why-we-chose-vue-js-be2411ff7f34?source=rss----5657d1231ca0---4</link>
            <guid isPermaLink="false">https://medium.com/p/be2411ff7f34</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <dc:creator><![CDATA[Kim Desrosiers]]></dc:creator>
            <pubDate>Fri, 15 Sep 2017 12:46:50 GMT</pubDate>
            <atom:updated>2017-09-15T14:23:20.464Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*lOWuN3XwH1PycpZYDjzaJw.png" /></figure><p><em>I know you probably tell yourself: “Yet another post on Why we chose Vue.js”. But don’t leave now. I think posts like this are important for the startups that struggle to choose between technologies especially in the web development world.</em></p><p>When I started to work for Phytochemia , I faced a big challenge: combining <strong>IT</strong> with <strong>Chemistry. </strong>Basically, I was mandated to rewrite a web application initially developed by a chemist with coding knowledge. The project motivated me a lot and the most interesting point was that I had <em>carte blanche</em>, I could use any technologies.</p><p>For the back-end, It was easy to choose the best technologies according to the current and future needs. But when it came to choosing the front-end, it was another story.</p><h3>My front-end struggle</h3><p>The first “working” prototype was a classic server side rendering + JQuery for the dynamic parts (AJAX, DOM manipulations). For example adding options dynamically to a select element using JQuery.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fkimond%2Fembed%2Fpreview%2FVzqqmW%3Fheight%3D600%26slug-hash%3DVzqqmW%26default-tabs%3Djs%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Fkimond%2Fpen%2FVzqqmW&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F1451222.VzqqmW.small.e8f89718-5a59-4958-ad01-40f8e7f59e35.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/af260174f8a7301203a1b928d9ef6033/href">https://medium.com/media/af260174f8a7301203a1b928d9ef6033/href</a></iframe><p>Not so frustrating but I don’t want to manipulate the DOM by myself and if I change something in the HTML, I can break everything.</p><p>As the project became larger and complex, my JQuery setup gave me more frustrations than productivity. So I decided to go with the flow and use a real front-end library to improve my productivity. In the past years, I had the chance to try some popular front-end libraries such Angular and React.</p><p>I didn’t consider Angular for this project because we didn’t plan to make a big <em>SPA (Single page application) </em>and the learning curve was bigger than the alternatives. Then there was React with a more realistic learning curve and a nice ecosystem but the JSX turned me off.</p><p>If you want a more detailed comparison, I encourage you to go and read the following link:</p><p><a href="https://vuejs.org/v2/guide/comparison.html">Comparison with Other Frameworks - Vue.js</a></p><h3>My discovery of Vue.js</h3><p>I had already heard about Vue.js but I never took the time to play with it. So one day I decided to give it a try for a little application. For example I will make a Vue.js version of the previous JQuery example.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fkimond%2Fembed%2Fpreview%2FVzqqqX%3Fheight%3D600%26slug-hash%3DVzqqqX%26default-tabs%3Djs%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Fkimond%2Fpen%2FVzqqqX&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F1451222.VzqqqX.small.da6856b0-a3df-43df-8038-690caaf10237.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/466933ff792076e59230358731026511/href">https://medium.com/media/466933ff792076e59230358731026511/href</a></iframe><p>The Vue.js version is more simple and easy to change if needed.</p><p>To be honest with you, I fell in love with Vue.js ❤️ and it rekindled my love for the front-end again. It took me an afternoon to learn the basics of Vue.js and to develop my little application. My first thought was to rewrite everything with Vue.js, something that I didn’t do immediately. But I still took the time to rewrite the core feature of the web application in order to improve performances. That’s how I discovered more power with Vue.</p><h3>So why Vue.js after all?</h3><p>What makes Vue.js so attractive? First, its simplicity like I said. In only one afternoon I managed to learn the library and develop something which is still in production now. As a matter of learning curve, I think it is reasonable.</p><p>Second would be its flexibility: there are <a href="https://vuejsdevelopers.com/2017/03/24/vue-js-component-templates/">7 ways to define a component template</a> with Vue.js. Some people would say that this is too much and that it can lead to more confusion than necessary but in my opinion, these 7 ways simply add more possibilities for the library. Keep in mind that you are not forced to use all of them. This brings me to my next point: the Single File Components (<em>SFC</em>).</p><p>The SFC are my favorite feature of Vue.js and according to me one of the most powerful one. With SFC you can put in a single file the HTML, Javascript and CSS of a component so you can use the advantages of each language without having to separate the logic between multiple files. Those files have the <strong>.vue</strong> extension. The only downside is that you need to use a module bundler such Webpack or Browserify.</p><p>However, the Vue.js documentation is awesome and will help you to setup the webpack configuration which is not too complex after all. Furthermore, the documentation was another reason why I chose Vue.js. The documentation is very well explain and easy to navigate within. There are guides, API reference and examples everything that you will need to work with Vue.js.</p><h3>In summary</h3><p>Among the large variety of possibilities that the front-end world has to offer to us, Vue.js turned out to be a revelation for me in term of functionalities and learning curve. I think that React and Angular are still good choices too, but unfortunately they didn’t meet our requirements.</p><p>I’m really satisfied of my choice to go with Vue.js. Since my beginning with this awesome library, I continue to love it a little more every day. Moreover, next thing that might be of interest would be Vuex the state management pattern library for Vue.js applications.</p><p>Here are some interesting links about Vue.js</p><ul><li><a href="https://vuejs.org/">Vue.js official website</a></li><li><a href="https://github.com/vuejs/awesome-vue">Awesome Vue.js GitHub repository</a></li><li><a href="http://vue-newsletter.com/">Vue.js Newsletter</a></li></ul><p>Give it a try you won’t regret it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be2411ff7f34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/phytochemia-tech-blog/why-we-chose-vue-js-be2411ff7f34">Why we chose Vue.js</a> was originally published in <a href="https://medium.com/phytochemia-tech-blog">Phytochemia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to the Phytochemia Tech Blog!]]></title>
            <link>https://medium.com/phytochemia-tech-blog/welcome-to-the-phytochemia-tech-blog-ddb4dc0d0473?source=rss----5657d1231ca0---4</link>
            <guid isPermaLink="false">https://medium.com/p/ddb4dc0d0473</guid>
            <category><![CDATA[welcome]]></category>
            <category><![CDATA[phytochemia]]></category>
            <category><![CDATA[hello-world]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[chemistry]]></category>
            <dc:creator><![CDATA[Kim Desrosiers]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 12:41:24 GMT</pubDate>
            <atom:updated>2019-12-05T16:16:30.211Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FCmr1OMJ2FN0B2%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FCmr1OMJ2FN0B2%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FCmr1OMJ2FN0B2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/743295ec247902cfa0ec3e1894324af2/href">https://medium.com/media/743295ec247902cfa0ec3e1894324af2/href</a></iframe><p><a href="http://www.phytochemia.com/en/home/">Phytochemia</a> has been around since 2013. Last year, they hired their first tech guy (me) in order to fulfill their needs in IT. Since my arrival in the company, we had the chance to work on a lot of projects related to both chemistry and IT. For example, were able to work with machine learning.</p><p>Thus, at Phytochemia we love to share our passions with the community. This is why we decided to create this tech blog alongside the <a href="http://www.phytochemia.com/en/blog/">main blog of the company</a>. This blog will be able to share tech stories as much as chemistry ones. Everyone will be satisfied 😃!</p><p>I hope you will enjoy it!</p><p>The Phytochemia Tech Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddb4dc0d0473" width="1" height="1" alt=""><hr><p><a href="https://medium.com/phytochemia-tech-blog/welcome-to-the-phytochemia-tech-blog-ddb4dc0d0473">Welcome to the Phytochemia Tech Blog!</a> was originally published in <a href="https://medium.com/phytochemia-tech-blog">Phytochemia Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>