<?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 Love Afinni on Medium]]></title>
        <description><![CDATA[Stories by Love Afinni on Medium]]></description>
        <link>https://medium.com/@loveafinni16?source=rss-b12efe0064dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FKy8Ri9RTZ_0q58d</url>
            <title>Stories by Love Afinni on Medium</title>
            <link>https://medium.com/@loveafinni16?source=rss-b12efe0064dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:28:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@loveafinni16/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[Building ResourceHub - Blog Post]]></title>
            <link>https://medium.com/@loveafinni16/portfolio-project-blog-post-resourcehub-d19db8e8f95f?source=rss-b12efe0064dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d19db8e8f95f</guid>
            <category><![CDATA[alx-software-engineering]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[alxafrica]]></category>
            <category><![CDATA[portfolio-project]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Love Afinni]]></dc:creator>
            <pubDate>Wed, 10 Jul 2024 20:21:32 GMT</pubDate>
            <atom:updated>2024-07-15T14:27:50.072Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building ResourceHub – Blog Post</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ua2VQIH6d04L_eiczuk6iA.png" /><figcaption>Figure 1: ResourceHub Landing Page</figcaption></figure><p>ResourceHub is a platform that simplifies resource sharing between educators and learners within academic Institutions. This project was initially designed with Nigerian universities in mind; however, the fundamental features of this platform are applicable to educational Institutions worldwide.</p><p><strong><em>Team Members</em></strong></p><p>This project was developed by a team of three: <a href="https://github.com/Abdulquyum">Abdulquyum Ajumobi</a>, <a href="https://github.com/kelanny">Kelvin Chuchu Mburu</a> and myself as our Foundations Portfolio Project in the ALX Software Engineering Programme; a key criterion for moving on to the Specialization phase of the programme. Abdulquyum worked on the frontend of the application, Kelvin worked on devops related tasks, and I built the backend of the application.</p><p><strong><em>Project Timeline</em></strong></p><p>The current version of ResourceHub was developed over six (6) weeks, with three (3) weeks spent on design and planning; two (2) weeks on development; and one (1) week on code cleanup and documentation.</p><p>During the planning phase, we defined the key features of the MVP, highlighted user stories, designed the application infrastructure on Miro, designed the UI/UX of the application using Figma, broke down tasks on Trello and assigned deadlines based on set milestones and the overall timeline for development.</p><p>During the development phase, we designed and built the data models, built the API for seamless database interactions, implemented authentication for user dashboards and developed the three user dashboards- Institution dashboard, teacher dashboard and learner dashboard.</p><p><strong><em>Who Was ResourceHub Created For?</em></strong></p><p>ResourceHub was designed to assist three key members of the academic sector, namely:</p><ol><li>Students or learners, who will use the platform to access study materials relevant to their courses.</li><li>Lecturers and/or teachers, who will use the platform to create or upload study materials to be distributed to their students or learners.</li><li>Institutions, who will use the platform to manage user accounts (teachers and learners), monitor the distribution of materials and ensure compliance with academic standards.</li></ol><p><strong><em>Personal Focus</em></strong></p><p>My personal focus during this project were:</p><ul><li>ensuring that our user workflow didn’t deviate from the existing online school system so as to ensure seamless experience for our users, and</li><li>ensuring we had a reliable and robust RESTful API for database interactions.</li></ul><h3><strong>Why I Chose To Work On This Project</strong></h3><p>Every member of our team wanted to solve a problem in the academic sector, so it was quite easy to agree on this solution. Personally, I’ve been a huge beneficiary of the academic system in my country, and in a way, I wanted to give back to the system. There were so many improvements that could be made and instead of just complaining, we decided to actually do something about them.</p><p>One of the key problems in tertiary Institutions in Nigeria today is resource sharing. In most Nigerian universities, the prevalent method of distributing relevant study materials, commonly referred to as ‘handouts’, involves printing or photocopying excerpts from books or writings, handing it over to a representative of the class, who then distributes it to students.</p><p>This primitive process presents several issues including:</p><ul><li>lack of structure and reliability,</li><li>students who cannot afford the cost of handouts are deprived of essential study materials,</li><li>lecturers may lose access to important resource materials stored on their personal devices, creating additional hurdles in material recovery and distribution.</li></ul><p>It’s interesting how there exists a structure for everything else- course registration, grade viewing, etc, except for resource distribution!</p><p>So my team and I decided to build a more organized and accessible system for distributing study materials.</p><h3>What We’ve Accomplished With Our Project</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gobVp-5klsrCQW_oh-4_Aw.jpeg" /><figcaption><em>Figure 2: ResourceHub Infrastructure</em></figcaption></figure><p><strong><em>Technologies used and why we chose them</em></strong></p><p>For the frontend of our application, we used HTML5, Jinja and Python with Flask framework to ensure:</p><ul><li>our application has fast initial load because most of the rendering will be done on the server-side and the fully rendered HTML will be sent to the client;</li><li>client does not need to handle as much processing ensuring good performance on low-powered devices as most of our users are University students who may be unable to afford sophisticated devices; and</li><li>less complexity considering the short timeline (2 weeks) for delivering the MVP.</li></ul><p>For the backend of our application, we used Python with Flask framework because of its rich libraries and extensions such as SQLAlchemy for database interactions and Flask-Login for authentication and session management. In addition, Flask is well-suited for development and testing of RESTful API since our application architecture involves a frontend and backend communicating over HTTP.</p><p><strong><em>Overview of features completed</em></strong></p><p><em>Authentication and Role-based Access Control:</em></p><p>We implemented a robust authentication system that allows different types of users (Institutions, teachers and learners) to log in to their respective dashboards using their unique credentials. Hence, users can securely log in to their respective dashboards and access only functionalities specific to their roles. For example, a teacher trying to access the ‘manage-departments’ page, will get a 403 Forbidden Error message, as only Institutions are allowed to manage departments. We used Flask-Login to implement this.</p><p><em>Resource Creation and Management for Teachers:</em></p><p>Teachers can <em>create</em> educational resources in the form of articles (more resource types coming in next version). The resource creation interface includes a rich text editor which allows teachers to compose and publish content directly on the platform. Teachers can also delete resources they created (<em>update</em> coming in next version). Each resource is assigned a unique URL, making it easily shareable. Resources are stored in the database and can be retrieved and displayed on the frontend.</p><p><em>Learner Access to Resources:</em></p><p>Learners can view all resources available in their department. They can access detailed content by clicking on a resource link, which redirects them to a dedicated resource page. Each resource has a dedicated page where learners can view its content, we used Jinja2 templating to dynamically render resource data on this page.</p><p><em>Institution Superuser Privileges:</em></p><p>Institutions have superuser privileges on the application and can manage other users within their school, ensuring that only authorized individuals are added to the system. Only institutions need to sign up on the application, and upon login, they can add or delete teachers, learners and departments. This feature aligns with real-world academic processes where teachers must be employed by an institution, and students must be admitted before accessing institution benefits.</p><h3><strong>Most Difficult Task I Succeeded in Solving</strong></h3><p>During the planning phase of our project, we decided on getting our own server, configuring it and hosting our application on it. The app would be running on one Gunicorn instance, and the API on another. The directory structure, in this case, would not have much impact as long as modules and objects were imported correctly in places where they were needed. So our directory structure looked like this: with the api, models and templates folder in the root directory.</p><p>However, a few days to the deadline, we realized that the chances of getting a dedicated server were very slim due to constraints making international purchases from our country. After several YouTube tutorials and frustrating attempts at getting a dedicated server, I reached out to my peers- <a href="https://x.com/joe_self_phu?s=21">Joseph</a>, <a href="https://www.linkedin.com/in/oladamola-taiwo-7ab39930b?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile">Stun</a> and Peter who recommended that we deploy our application on Render.</p><p>I watched YouTube tutorials on how to deploy applications on render but couldn’t seem to find one for deploying a full stack application with Flask frontend, Flask backend and database. Two days to the deadline and more YouTube tutorials later, I learnt I had to deploy each component (Flask frontend, Flask Restful API and PostgreSQL database) of the application as individual services. I then discovered a fault in the structure of the application: the frontend and backend were not entirely separate!</p><p>Firstly, the models were outside the API folder, and secondly, the frontend (app.py) was internally importing the model classes! Now Flask-login needs to take in an actual user object which inherits from UserMixin to work. But the API returned only JSON data, therefore, even users returned by the API- when deserialized- were just dictionaries containing data. Hence why user models were being imported: to recreate the objects from their JSON data.</p><p>This posed a significant challenge as I needed to figure out a way to recreate user instances without access to the classes/models themselves.</p><p>After brainstorming, I decided to create a generic user model for the frontend. This model:</p><ul><li>would inherit from UserMixin to enable its instances access to the necessary methods and attributes for Flask-Login to function, and</li><li>more importantly, recreate user objects from just their data.</li></ul><p>I moved the models into the api folder, updated the import statements with the new directory structure and disallowed models in the api/models folder from inheriting from the UserMixin class, since the generic user model at the frontend would handle authentication-related functionalities. Then I unit tested again to ensure nothing had broken.</p><p>With this fix, I was able to separate the backend from the frontend and deploy the API as an individual service linked appropriately to the database. I then deployed the application as a separate service as well, which could make calls to the API for database operations. The three components of our application are hosted on Render.</p><h3><strong>Key Lessons I Learnt From This Project</strong></h3><ol><li>Unit testing is not even a question: While building the API, my biggest priority was handling as many scenarios as possible…if possible, all. After building each API view, I was so confident I had done the right thing because I built each endpoint thinking “what if the consumer passes this…or doesn’t pass that?”. Until, I’d write unittests for a view, run them, and get a number of exceptions from unhandled errors. Unit testing made me see errors that I didn’t even think of handling and it helped me build a more reliable API. I now better understood why ALX always insisted we unit tested every molecule of code…lol.</li><li>Good planning makes development so much easier: Before starting the project at all, I had spoken to a senior peer, <a href="https://www.linkedin.com/in/i-bamidele?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile">Michael</a>, who encouraged me to take the weeks of planning very seriously. He mentioned that if we got it right in planning, development would be very easy. While my team and I did take planning very seriously, I only really understood what he meant during development. We had enough time to handle unforeseen issues because we had planned to build 80% of the entire application within the first week of development, leaving a significant chunk of our time for “unforeseen circumstances”.</li><li>Communication is key: Another key lesson I learnt was that the frequent communication between my teammates and I made it easier for us to resolve problems in a timely manner.</li></ol><p>To check out our project, <a href="https://resourcehub-0szu.onrender.com/">click here</a>. You can also view our codebase <a href="https://github.com/NiniolaX/ResourceHub/">here</a>.</p><p>I am Love Afinni, an aspiring Backend Engineer and I love to solve problems with code. You can check me out on <a href="https://github.com/NiniolaX">GitHub</a>, <a href="https://www.linkedin.com/in/loveafinni">LinkedIn </a>or <a href="https://www.instagram.com/loveafinney">Instagram</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d19db8e8f95f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens when you type www.google.com into your browser and press Enter]]></title>
            <link>https://medium.com/@loveafinni16/what-happens-when-you-type-www-google-com-into-your-browser-and-press-enter-998723d1ab9a?source=rss-b12efe0064dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/998723d1ab9a</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Love Afinni]]></dc:creator>
            <pubDate>Sun, 12 May 2024 10:30:13 GMT</pubDate>
            <atom:updated>2024-05-13T12:50:28.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>What happens when you type <a href="http://www.google.com/">www.google.com</a> into your browser and press ‘Enter’</h3><blockquote>You type <a href="http://www.google.com/">www.google.com</a> into you browser and press ‘Enter’. A few milliseconds later, a nice page is displayed on your screen.</blockquote><blockquote><em>In this article, we will look into what happens within those milliseconds.</em></blockquote><h3><strong>Introduction: The Internet and Computers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JD707aHZWzU5Q-Ce1T4yFQ.jpeg" /><figcaption>Figure 1: The internet</figcaption></figure><p>The internet is a global network of networks. A network is a system of interconnected computers sharing data and resources.</p><p>You may think that the word ‘computer’ here only refers to laptops and desktop computers. However, the word <em>computer</em> is a broad term used to refer to any device that can connect to the internet, including mobile phones, laptops, desktop computers, iPads, smartwatches and a special kind known as <strong><em>servers.</em></strong></p><p><strong><em>Servers</em></strong></p><p>All websites and applications live on <em>servers.</em> A server is simply a computer or machine that offers some kind of service to another computer. A server basically sits and <em>listens</em> for requests from other computers, called <strong><em>clients</em></strong>. There are different types of servers and they offer various types of services, such website hosting, file storage, mail service, etc. In this article, you would come across the various servers involved in getting your desired webpage to your computer screen. Servers live in data centers scattered all around the world.</p><p><strong><em>Internet Protocol (IP)</em></strong></p><p>We’ve established that the internet is made up of a ginormous number of computers, and that these computers share data and resources. But there are billions of computers on the internet, how do they tell one another apart? With IP addresses!</p><p>IP stands for Internet Protocol, and, an IP address is a unique number assigned to a device on a network. No two computers can have the same IP address. You can think of IP address as the identity of your computer on the massive internet, with which other computers can find it.</p><p>When you connect your computer to a mobile or Wi-Fi network, an IP address is automatically assigned to it by special servers known as DHCP (Dynamic Host Configuration Protocol) servers. If you’re on a Wi-Fi network, the DHCP server is usually on your router. An IP address looks like this: 192.168.0.177.</p><p>All devices on the internet have IP addresses, including servers.</p><h3><strong>DNS Resolution</strong></h3><p>Humans cannot easily remember numerical IP addresses, so we use domain names, like www.google.com, facebook.com, etc., instead. Domain names are human-readable identifiers for resources on the internet.</p><p>The first thing your browser needs to do after you click ‘Enter’ is to get the domain name <a href="http://www.google.com/">www.google.com</a> converted to the actual IP address of the server hosting the website. The Domain Name System (DNS) helps with this in a process known as <strong>DNS Resolution</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7I-qLnLPPP45vjGs0iVODg.jpeg" /><figcaption>Figure 2: DNS resolution</figcaption></figure><p>Here’s how DNS resolution works:</p><ul><li>Both the browser and the computer operating system (OS) first check their caches to see if they know the IP address to find google.com.</li><li>If the OS and browser can’t find the IP address in their caches, the OS sends a request to the DNS resolver.</li><li>The resolver queries the DNS servers for the IP address for google.com. DNS servers are a special type of servers that store domain names and IP addresses, you can think of them as an address book for domains.</li><li>After obtaining the IP address from the DNS servers, the resolver sends it to your OS, and the OS sends it to the browser.</li></ul><h3><strong>Establishing a TCP/IP Connection</strong></h3><p>Now that your browser know what server to find <a href="http://www.google.com,/">www.google.com,</a> it needs to ask the server to send the page to it through the internet. This means your computer and the server need to be able to communicate with each other. This is where TCP/IP come into play.</p><p>TCP/IP stands for Transmission Control Protocol / Internet Protocol. It is a suite of standardized protocols (or rules) developed and maintained by organizations like IETF (Internet Engineering Task Force) and ISO (International Organization for Standardization), that define how computers communicate with one another over a network.</p><p>Before two computers can ‘speak’ to one another, a TCP connection first needs to be set up between them. Through this TCP connection, packets of data can be transmitted over a network such as the internet.</p><p>So your browser sends a TCP connection request packet to the server, specifying the <strong>port number </strong>and <strong>protocol </strong>(more in coming sections) being used. <em>Port numbers</em> are like designated doors through which servers receive different type of requests, and, the <em>protocol</em> is like the language with which the client and server will communicate after they are connected. If the server is listening on the specified port, it responds with an acknowledgement packet to the browser and the connection is established.</p><p><strong><em>Firewall: Safeguarding Connections</em></strong></p><p>Most computers on the internet including servers are protected by a firewall. Firewalls serve as a security barrier between a private network or computer and an outer network, often the internet. They are usually pre-configured to perform various types of checks and filtering to enhance security.</p><p>The firewall monitors the attempted TCP connection to ensure that it is legitimate and conforms to the expected behavior of those connections.</p><p><em>If the firewall check is successful, a TCP connection is established between your browser and the server.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*miN7DeSOy7tfUnRi47FjYA.jpeg" /><figcaption>Figure 3: HTTPS over TCP</figcaption></figure><p><strong><em>Communication with HTTPS/SSL</em></strong></p><p>Now that your browser and server have established a TCP connection, they speak to one another using a language, technically referred to as <em>communication protocol</em>.</p><p>The most commonly used communication protocol for websites is HTTP (Hypertext Transfer Protocol). It is the protocol over which data is sent between your browser and a server it is connected to.</p><p>However, data sent over HTTP is not secure as it is sent in plain text. If the connection is intercepted by malicious actors, the safety of sensitive data like password and credit card information could be compromised. Hence, the advent of HTTPS, the ‘S’ stands for secure and it refers to HTTP over SSL (Secure Sockets Layer).</p><p>HTTPS is a more secure version of HTTP. With HTTPS, a client (i.e. your browser) and the server can agree on a key to be used to encrypt and decrypt data during a process known as an <em>SSL handshake</em>. Information to be sent over the connection will then first be encrypted before it is sent. This encrypted data can only be decrypted by the server, hence, even if the connection is intercepted, it will be unusable.</p><p>A server has 65,535 ports. By default, servers listen for HTTP requests on port 80 and HTTPS on port 443.</p><p>After a SSL handshake between your browser and the server, your browser sends an HTTP request to the server requesting for the page <a href="http://www.google.com/">www.google.com</a> from it.</p><p><em>So far, we have seen how the browser locates the IP address hosting </em><a href="http://www.google.com/"><em>www.google.com</em></a><em>, how it connects to the server hosting the page, and the language the server and browser will use to speak to each other. All the processes that have occurred are said to be on the </em><strong><em>client-side</em></strong><em>.</em></p><p><em>In the coming sections, we will see what happens at the </em><strong><em>server-side</em></strong><em>.</em></p><h3>Load Balancing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npqIwziqoZeJMIRTym-RBQ.jpeg" /><figcaption>Figure 4: Load balancing</figcaption></figure><p>Usually, there is more than one server handling requests for a single website. This is to increase the capacity and availability of a web infrastructure. It is estimated that Google uses over one million servers across data centers around the world.</p><p>Have you ever wondered how millions of other people on the internet, are possibly entering <a href="http://www.google.com/">www.google.com</a> into their browsers simultaneously, yet the web page is delivered to everyone’s computer screen almost immediately? This is the work of <em>load balancing</em>. ‘Load’ here refers to network traffic, and ‘balancing’ is pretty much straight-forward.</p><p>A load balancer is a server that receives client requests and tries to distribute them equally between servers.</p><p>For most websites, the IP address retrieved by the DNS servers is that of a load balancer. The load balancer receives the HTTP request from the browser and forwards it to one of the web servers specified in its configuration file. The load balancing algorithm is used to determine how requests will be distributed between servers and it is also specified in the configuration file.</p><p>Load balancers are the men in the middle that make sure your HTTP request goes to the <em>web server</em> where it can be processed the fastest, so you can get your desired web page within the shortest possible time.</p><h3>Web server: Processing HTTP Requests</h3><p>Earlier, we mentioned that there are various types of servers. So far we have mentioned DHCP servers, DNS servers and load balancers. Another type of server involved in the process of getting your web page are<em> web servers</em>.</p><p>Web servers listen for HTTP requests, process the received request and send back an HTTP response to the client.</p><p>A web server can serve two types of content; static or dynamic content. Static content is content that doesn’t change irrespective of the client, for example, a business’s home page. Dynamic content, on the other hand, is content that changes based on user settings or preferences, for example one user’s Instagram feed is not the same as another’s feed.</p><p>When the web server receives the HTTP request, it can do two things:</p><p>(i) Check the folder specified in it’s configuration file for the page (<a href="http://www.google.com/">www.google.com</a>) requested. If found, it sends a ‘200 OK’ message back to the browser and begins sending its content in small streams of data called ‘packets’. If the page is not found, it returns a ‘404 page not found’ error to your browser.</p><p>(ii) If dynamic content is requested, it can delegate generation of the content to a script or to an <em>application server</em> (more details in the next section).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_HSGFMcMDePoVekvc3SWQ.jpeg" /><figcaption>Figure 5: Web client-server architecture</figcaption></figure><p><strong><em>Application servers: Serving business logic</em></strong></p><p>An application server serves <em>business logic </em>to its clients, this client could be web servers or other programs.</p><p>For example, you want to make a transfer from your mobile banking app. The backend process roughly looks like this: the web server receives your request and forwards it to the application server; the application server then fetches your account information from the <em>database</em>, deducts the transfer amount from your account, updates the receiver’s account with the amount and updates the database with your new balance; the application server then generates a transfer receipt and sends it to the web server; the web server finally sends the generated transfer receipt to the client (your mobile banking app) in an HTTP response.</p><p>The actions taken by the application server in this illustration is an example of ‘serving of business logic’.</p><p><strong><em>Databases: Storing and Retrieving Information</em></strong></p><p>All web applications have a database, it is where user’s information is kept securely and easily accessible. A database is an organized collection of data and a system used for efficient management and security of the data contained.</p><p>Think of the billions of Google users around the world, each user’s information like name, phone number, email, etc., is stored in databases. So, when you log into your google account with your email and password, the application server queries the databases to get your name, image, photo, etc., to be displayed on your web page.</p><p>Once the browser receives the HTTP response from the server, it assembles the data packets received, displays it on your screen and closes the connection.</p><h3>Conclusion</h3><p>In summary, when you type in <a href="http://www.google.com/">www.google.com</a> into your browser and press ‘Enter’:</p><p>- Your browser asks the OS for the IP address to the website <a href="http://www.google.com/">www.google.com</a>,</p><p>- The OS sends a DNS request to the resolver which retrieves the IP address for <a href="http://www.google.com/">www.google.com</a> from the DNS servers,</p><p>- Your browser establishes a TCP connection to the server and sends an HTTP request for page <a href="http://www.google.com,/">www.google.com,</a></p><p>- The request is received by the load balancer, which forwards it to the web server most suitable to process the request at that time,</p><p>- The web server receives the HTTP request, and processes it,</p><p>- the web server sends a <em>200 OK</em> response to the browser and begins sending the content of the web page to the it in small packets in an HTTP response,</p><p>- The browser receives the data packets, reassembles them into the web page and displays it for you to see on your computer screen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=998723d1ab9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>