<?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 Eddie Knight on Medium]]></title>
        <description><![CDATA[Stories by Eddie Knight on Medium]]></description>
        <link>https://medium.com/@eddie-knight?source=rss-b8c04d81b34f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nPb6d6c8JEo3mmDWLvdKHw.jpeg</url>
            <title>Stories by Eddie Knight on Medium</title>
            <link>https://medium.com/@eddie-knight?source=rss-b8c04d81b34f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:20:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eddie-knight/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[Dependencies are like Diapers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://eddie-knight.medium.com/dependencies-are-like-diapers-620f573f2b80?source=rss-b8c04d81b34f------2"><img src="https://cdn-images-1.medium.com/max/2600/1*jBuEU0C8dKV9s2CZO2TLpQ.jpeg" width="5760"></a></p><p class="medium-feed-snippet">A quick and dirty reminder</p><p class="medium-feed-link"><a href="https://eddie-knight.medium.com/dependencies-are-like-diapers-620f573f2b80?source=rss-b8c04d81b34f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://eddie-knight.medium.com/dependencies-are-like-diapers-620f573f2b80?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/620f573f2b80</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Mon, 19 Dec 2022 15:20:21 GMT</pubDate>
            <atom:updated>2022-12-19T18:34:20.717Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Stop the Low-Quality Contribution Plague]]></title>
            <link>https://eddie-knight.medium.com/stop-the-low-quality-contribution-plague-b8d42cec9e3?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8d42cec9e3</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[open-source-software]]></category>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 19 Oct 2022 19:21:15 GMT</pubDate>
            <atom:updated>2022-10-19T19:41:34.498Z</atom:updated>
            <content:encoded><![CDATA[<h4>You’ve heard the phrase… this is how to actually avoid it.</h4><p>I was in a discussion thread with folks from CNCF and Kubernetes today, and this phrase came up again. The context was something along the lines of… “We’re afraid that will encourage <em>low-quality contributions</em>.”</p><p>Let’s dig in to this.</p><p>The reason low-quality contributions are such a plague is because most people are used to <em>committing</em> code, but <a href="https://eddie-knight.medium.com/becoming-a-new-contributor-to-open-source-software-567c28d8c137">new open source contributors</a> aren’t used to reviewing code for a project with a large committer base.</p><p>For this article, I’m going to look at ways you can limit the number of low-quality contributions you <em>recieve</em> and even more ways to stop <em>making </em>them yourself.</p><p>But before we make the list, we need to understand some of the most common culprits that earn the badge of “Low-Quality Contribution.”</p><p>And since we’re overusing this phrase today… Let’s just say “<em>LQC” </em>for the rest of this article.</p><h4>What a LQC isn’t…</h4><ol><li>It is not a PR from an unknown person.</li><li>It is not a long-lived draft PR.</li><li>It is not a PR that needs improvements.</li><li>It is not a PR that needs a lot of improvements.</li></ol><p>Sure, those things are tedious… but they don’t make a PR <em>low-quality </em>in the sense that we’re talking about here.</p><h4>What a LQC is…</h4><p>I’m sure this isn’t an exhaustive list, but here are the first four culprits that come to mind:</p><ol><li>It is work that is contributed with no context for the reviewer(s), or no confirmation the work is needed at this time</li><li>It is work beyond the scope or vision of the project</li><li>It is a pull request with poor hygeine</li><li>It is code or documentation that doesn’t follow established best practices</li></ol><h3>How maintainers can reduce LQCs</h3><p>You don’t need reminded, but I’ll remind you anyhow: Contributors are almost universally <em>just trying to help</em>. Remember to assume positive intent, and it’ll do wonders for your mental health (and communication).</p><p>But we still need to reduce the frequency of these well-intentioned LQCs.</p><p>So my advice for you is to take advantage of existing tools and documentation best practices. For example… check out <a href="https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors">GitHub’s tooling</a> that reminds contributors to review the docs before making a PR.</p><p>The next, more complicated option is to add some automation. Kubernetes has the most robust example of this that I’ve seen… they automate the reviewer assignment, label assignment, and explanation comments, all in addition to the normal CI checks we would expect.</p><p>Here’s an example of a draft PR I created over the weekend, where you can see how all these automations help reduce the workload on reviewers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*pTYLUoy9b3K6fwykpilWNQ.png" /></figure><h3>How committers can stop spreading the LQC plague</h3><p>Let’s go through each of the culprits, with suggested fixes.</p><h4>1. Work that is contributed with no context for the reviewer(s), or no confirmation the work is needed at this time</h4><p>The solution is just to do the opposite of the problem. Give more information to the reviewers!</p><p>This can be done through the project’s work tracking tools (such as GitHub Issues) or in discussion on their normal community channels. I usually recommend creating a GitHub issue and then finding the appropriate slack channel to reach out to. This allows the community to give feedback on your suggestion before you waste time building the solution.</p><p>Oh, and you’ll avoid potentially duplicating work that someone else is already part-way through.</p><p>You can save a lot of work by discussing your changes before making the PR. But if it’s a small change… you may just want to skip straight to the code. If you do that, be sure to provide clear, concise, helpful descriptions of both the problem and your proposed solution in the PR.</p><h4>2. Work beyond the scope or vision of the project</h4><p>This can be mitigated through discussion as well. Really… just follow all the advice I listed above, but <em>avoid</em> going directly into a pull request if your change might be outside of the normal scope of the project.</p><h4>3. Bad pull request hygeine</h4><p>Read the contribution guidelines, and always make a draft PR first!</p><p>Especially look for the following in the CONTRIBUTING.md:</p><ul><li>A specific way of formatting commits or PR titles</li><li>Tests that must be created or modified</li><li>Recommended steps for getting a PR reviewed</li></ul><h4>4. Code or documentation that doesn’t follow established best practices</h4><p>Okay come on now. You really don’t need me to tell you this, right? Look up the best practices for the language you’re working in… such as PEP8 for Python.</p><p>Additionally, documentation will likely have different “best practices” for every project. Take a look around to find out what the reviewers will expect to see documented, and make it look like it was written by the same person who wrote the rest of the docs.</p><p>Oh… and again, I shouldn’t need to tell you this… but restrict your PRs to one feature/fix/refactor. Creating multiple PRs is fine if you’ve discussed the changes with the community ahead of time — but big PRs are never okay.</p><h3>Conclusion</h3><p>The best way to avoid spreading the low-quality contribution plague is to just put yourself in the shoes of your reviewer. Imagine that you’re really busy with your day job and you are taking a look at GitHub on your lunch break. What would you <em>like </em>to see?</p><p>You probably would get a headache if you are surprised by a new massive change request from a stranger on your project. But… you’d probably get a boost of energy if you see someone coming in and asking if they can help apply a change that would benefit the entire project!</p><p>Stop spreading the plague. Be the person who gives energy to open source maintainers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8d42cec9e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a New Contributor to Open Source Software]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://eddie-knight.medium.com/becoming-a-new-contributor-to-open-source-software-567c28d8c137?source=rss-b8c04d81b34f------2"><img src="https://cdn-images-1.medium.com/max/2600/1*u-xOpt7YBrraIBhdUhQx2A.jpeg" width="5760"></a></p><p class="medium-feed-snippet">Or rather, how I did it this time around.</p><p class="medium-feed-link"><a href="https://eddie-knight.medium.com/becoming-a-new-contributor-to-open-source-software-567c28d8c137?source=rss-b8c04d81b34f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://eddie-knight.medium.com/becoming-a-new-contributor-to-open-source-software-567c28d8c137?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/567c28d8c137</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[open-source-software]]></category>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Tue, 11 Oct 2022 16:45:41 GMT</pubDate>
            <atom:updated>2022-10-11T19:35:55.338Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Is the internet magic?]]></title>
            <link>https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f28da0ff240</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 23:28:44 GMT</pubDate>
            <atom:updated>2022-09-22T18:38:07.578Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve struggled with the concept of the internet most of my life, even recently, after spending years in a variety of software engineering roles.</p><p>Even just the concept of electricity in general has eluded me for too long. How is it really possible?</p><p>The ability to communicate so quickly, to process information so quickly, and to be able to do the exact same thing with computers that are on the other side of the world with sometimes just the blink of an eye passing… it absolutely breaks my brain.</p><p>I’m left asking: <em>is this magic?</em></p><p>And yet over the years, that question hasn’t really gone away for me.</p><p>I’ve worked as a front end web developer, a backend developer, I’ve set up API integrations and databases as a “full stack engineer” (as some people call it). I’ve worked in automation engineering — setting up APIs and tools used in data centers, occasionally plugging in cables to make sure that the flashing lights were there to impress the executives.</p><p>I’ve worked as an SRE in a cloud-based role for financial institutions where I was able to work on cloud infrastructure for software deployed all around the globe in <em>highly</em> regulated environments with high demands for accessibility and millions of simultaneous users.</p><p>I’ve been able to see how technology plays a part in <em>every single step</em> of this process, and yet even recently I’ve asked myself… at the core of all of this — is it just magic?</p><p>As I’ve dug deeper and deeper, I’ve been able to assure myself that no… this is not just some little magical fairy-tale beasties that we discovered in the 1950s and have been exploiting ever since. But I have come to a new opinion: everything we are doing in our computers and across the internet is really just an elaborate set of <em>smoke signals</em>.</p><p>In order to explore the idea and to give myself a starting point to really go through the journey of what’s going on with the internet, the guiding question that I used is: <em>what happens when you type “google.com” into your browser and hit enter?</em></p><p>This question’s often seen in interviews for technical roles, and it’s just a fun conversation starter for technical friends at the pub.</p><p>Below, I’ll give a high level step-by-step summary — with links to articles I wrote to dive deeper on each topic. If you have the time and curiosity, I’ve written each of these sub articles as a single narrative following a single journey through our computer and across the internet.</p><h3><em>What happens when you type “google.com” into your browser and hit enter?</em></h3><p>Let’s just make this a quick list of things that will happen sequentially.</p><ol><li><a href="https://eddie-knight.medium.com/what-happens-when-you-type-into-your-browsers-url-bar-85b4f80f319d">You’re typing, and the computer is working</a>. This is a fairly simple concept, but quite a bit is happening. Just getting the computer to present a “g” on your screen requires a substantial amount of work. The interaction will go from the keyboard to the CPU, get instructions from the BIOS, and pass the event along to our browser.</li><li><a href="https://eddie-knight.medium.com/what-does-a-browser-do-after-we-submit-a-url-7fd347ecd3f5">Our browser will act on the event coming in.</a> Every browser is a bit different, but there are some common elements we can expect — such as autofill. <em>Bonus article: Your browser will need to know the </em><a href="https://eddie-knight.medium.com/whats-this-about-a-port-number-2ebf11c093c2"><em>port number</em></a><em> to talk to anytime it reaches out to a process on another machine.</em></li><li><a href="https://eddie-knight.medium.com/how-does-a-browser-use-dns-and-ip-9849060c9b38">Your process will request information from the DNS server</a>. In the last step we determined that we need to go outside to find the IP address for <em>google.com, </em>so we’ll form a packet following the Internet Protocol format and send it out into the wild wild web.</li><li><a href="https://eddie-knight.medium.com/what-difference-is-made-by-the-type-of-internet-service-i-have-b5d2ad79ecf2">To get anywhere, we’ll need to transmit a signal via our ISP</a>. The connection type you have will impact speeds, but the result will be the same: a bunch of hops across the inter-networked nodes. This is where I concluded that the internet is just <em>smoke signals</em>.</li><li><a href="https://eddie-knight.medium.com/how-are-dns-and-http-transactions-secured-ae3b9ee066ed">After we hear back from the DNS server, we’ll need to make our HTTP request</a>. The DNS communication and HTTP transactions will all be secured if things are operating normally, and we’ll need to send out a GET request to the target IP.</li><li><a href="https://eddie-knight.medium.com/how-does-an-http-request-get-to-the-webserver-fd2d493ce2ed">Our HTTP request will encounter some additional infrastructure before getting to the webserver</a>. This is likely to include a CDN, reverse proxy, and container orchestration among other things.</li><li><a href="https://eddie-knight.medium.com/what-happens-when-the-webserver-responds-to-our-request-51fd76b22c12">Finally, our browser will receive the HTTP response</a>. From here, the browser can use it’s built-in logic to parse the HTML and CSS in order to pass something useful back to your monitor and speakers.</li></ol><p>Thanks for joining me on this crazy journey from our computers out into the internet and back. I highly encourage you to click through to the articles I linked above.</p><p>It was an absolute wild ride just learning about all these individual little details (even though I already knew the bigger points). It was really fun for me, and I hope you enjoyed it as well.</p><p>If you saw anything in this that you were really curious about and want to learn more about… I recommend that you just take those key terms, type them into Google, find a Wikipedia page, and look for interesting articles on that topic.</p><p>These technologies all play together in fascinating ways, and I hope you enjoy peeking under the hood as much as I do!</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f28da0ff240" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens when the webserver responds to our request?]]></title>
            <link>https://eddie-knight.medium.com/what-happens-when-the-webserver-responds-to-our-request-51fd76b22c12?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/51fd76b22c12</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 23:24:26 GMT</pubDate>
            <atom:updated>2022-09-21T23:47:16.602Z</atom:updated>
            <content:encoded><![CDATA[<p>Does the webserver communicate directly with our machine at that point? What will it have to say?</p><p>This is a deep dive to answer the question above, as part of a larger question: <a href="https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240"><em>What happens when you type “google.com” into the browser and press enter?</em></a></p><p>Once a webserver finishes <a href="https://eddie-knight.medium.com/how-does-an-http-request-get-to-the-webserver-fd2d493ce2ed">running through its logic to handle the request we sent it</a>, it will send its reply back to whatever process had directly called it.</p><p>The reply will go backwards through the relays it came through on the way in- there are no shortcuts! It will eventually be passed all the way back to the CDN, which will send the HTTP response back to our machine via our ISP’s autonomous nodes.</p><p>Our browser will look at the HTTP response, which is different from the HTTP request… but it will contain a header and a body just like everything else we’ve explored in this series. The HTTP response header has information such as the <em>status code</em>, which is specified by the webserver to give us a quick hint about the result of the request.</p><p>The body of the response will then be processed by your browser. In this case, it will be a body of text in an HTML format.</p><p>To reinforce the trend we’ve seen throughout this series… all properly formatted HTML comes with two segments: the header and the body.</p><p>The HTML header provides a variety of information directly to the browser, but it’s not rendered on screen. Among other things, the header may include instructions for the title, the icon to display in the browser tab, and links to external code libraries that should be imported to aid in rendering the page.</p><p>In the response we got from google.com, we’ll find both style instructions and script logic included in the header.</p><p>Style instructions, often in CSS format, tell the browser how to render things such as the font and the color of the page. The script (often JavaScript) provides instructions on how to manipulate the information on the page or access external resources to complete the page load.</p><p>I mentioned in a previous article that the web server may have had logic to change the display based on the image of the day. But this may also be handled by a script that’s imported or written into the HTML and processed by the browser.</p><p>Once the browser finishes processing those styles and scripts, it will parse the body as well, translating it into visuals that our monitor can understand. At this point, google.com will have load exactly how we expected.</p><p>Was <a href="https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240">this process</a> more or less complicated than you expected? I’d love to hear from you in the comments on any article in this series!</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51fd76b22c12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How does an HTTP request get to the webserver?]]></title>
            <link>https://eddie-knight.medium.com/how-does-an-http-request-get-to-the-webserver-fd2d493ce2ed?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd2d493ce2ed</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 23:15:38 GMT</pubDate>
            <atom:updated>2022-09-21T23:15:38.224Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s explore some common elements in enterprise architecture.</p><p>This is a deep dive to answer the question above, as part of a larger question: <em>What happens when you type “google.com” into the browser and press enter?</em></p><p>In a previous article, we prepared ourselves to send a <em>hypertext transfer protocol</em> request to <a href="https://google.com./"><em>https://google.com.</em></a></p><p>A GET request is helpful in this situation because the body of that request is unnecessary and ignored by default. It’s usually left empty, and uses the fewest IP packets to communicate. The only information that the web server needs to know is the path that we’re requesting to view.</p><p>For older or less sophisticated applications, the IP address may take us directly to the server we’re trying to access. But we may also find that our request makes some additional hops after reaching the IP and before it reaches the web server.</p><p>Fpr a website as large as google.com, we’ll have multiple layers of infrastructure that our request must travel through after reaching the IP address that we’re targeting.</p><p>The following description is true for many large applications… though every infrastructure is built differently and I can only safely discuss common features. Much like the entry lobby to a large building, the exact flow of traffic and layout of the floor plan is unique in every situation, but some common trends exist.</p><p>The first infrastructure element we’re likely to encounter is the content delivery network.</p><p>The CDN acts as a buffer to help alleviate the work required for common tasks on a web server. Instead of going to the web server every time to get the same information, the CDN will cash the page on its own servers, spread out all around the world and will respond to the request from the location closest to the requester.</p><p>This saves processing power on the web servers and dramatically decreases the time it takes for us to load the webpage. In the case of google.com, it’s very likely that the homepage is delivered to us by a CDN, saving critical resources for the web searches and intensive logic.</p><p>But if we’re the first visitors to google.com after an update, the page won’t yet be cached with the CDN — and it’ll need to request the page update from the web servers.</p><p>Within the CDN, a piece of software called a <em>reverse proxy</em> will have instructions configured for the IP address we’re trying to reach. Information such as the port we’re requesting and the path we typed in the browser will all be considered by the reverse proxy, in addition to other configurations. This might include A/B testing, or other features set in place by the website’s maintainers.</p><p>Then a firewall is likely to exist alongside the CDN.</p><p>The firewall will have its own logic configured to determine what behaviors and origin points are allowed to continue. In many cases, the firewall will live immediately below the CDN, rejecting any traffic that doesn’t come through via the CDN.</p><p>After our request has been passed through the CDN and the firewall, it will encounter a load balancer. This will ensure our request continues on its journey to the proper region, and a machine that isn’t already overwhelmed by requests from other users.</p><p>In the case of google.com, it’s likely that we’ll also encounter a load balancer on Kubernetes, which is an orchestration technology that allows a large number of servers to be created, managed, and destroyed by automated processes.</p><p>The finer points of Kubernetes are best explored in a dedicated session, but for now we can safely say that our webserver lives in a <em>pod</em> within the Kubernetes <em>cluster</em>, that our request was passed to. Logic at the cluster level will balance traffic to an available pod that contains the webserver we’ve been assigned to interact with.</p><p>The webserver will have an <em>HTTP server</em> process with logic similar to the reverse proxy that handled our request at the top layer. Programmed instructions guide the machine to respond in a particular way based on a variety of parameters, including the port that our request is targeted.</p><p>The webserver will customize the information it sends back to us based on what our browser provided in the request, such as cookies specifying whether or not we’re logged in. Other information may come from outside of the webserver if it has instructions to reach out to external sources, such as an API to populate the image of the day.</p><p>Once the web server finishes running through its logic to handle our request, it will send its reply back to whatever process had directly called it. The reply will eventually be passed all the way back to the CDN, which will send an HTTP response back to our machine.</p><p>Continue reading to finish our journey as the HTTP response makes its way back to the browser.</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd2d493ce2ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How are DNS and HTTP transactions secured?]]></title>
            <link>https://eddie-knight.medium.com/how-are-dns-and-http-transactions-secured-ae3b9ee066ed?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae3b9ee066ed</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 22:59:45 GMT</pubDate>
            <atom:updated>2022-09-21T23:46:30.366Z</atom:updated>
            <content:encoded><![CDATA[<p>And what’s the difference between HTTP/S and a HTTP Request?</p><p>This is a deep dive to answer the question above, as part of a larger question: <a href="https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240"><em>What happens when you type “google.com” into the browser and press enter?</em></a></p><p>In a recent article, we explored how <a href="https://eddie-knight.medium.com/what-difference-is-made-by-the-type-of-internet-service-i-have-b5d2ad79ecf2">packets leaving our computer are sent and replicated across nodes using the Internet Protocol</a>. The packet we’ve most recently been following in our series is currently heading toward a DNS server in hopes of finding the IP Address for <em>https://google.com.</em></p><p>If all the network nodes between our computer and the DNS server are behaving how we expect, our packet will arrive with a greeting to the DNS server. After reading the packet, the DNS server will respond with a greeting of its own — which is called a “handshake.”</p><p>When the DNS server returns this handshake via packets across the network, it includes a certificate that can be used to authenticate itself. This certificate serves to protect our machine from being faked out by something <em>pretending </em>to be our DNS.</p><p>This is similar to a Rideshare driver, putting their license plate number into the Rideshare App.</p><p>As a rider, you know to expect a guy named Dave in a black Hyundai, but you can’t be totally sure that you’re getting into the right car unless you check the license plate number because the license plate is a globally unique identifier. We can trust that we’re getting in the right car after we compare the number in the app to the number on the plate.</p><p>Similarly, our browser knows to compare the incoming certificate with a certificate authority to make sure that no funny business is happening.</p><p><strong>This process is the backbone of our secure hypertext transfer protocol transaction (HTTPS).</strong> Without this, it’s possible that a malicious actor could have compromised any of the network nodes between our machine and our destination server, pretending to be friendly while actually harming us.</p><p>As an added bonus to the validation that we get from the certificate and the certificate authority, our browser will also be able to use that key to encrypt the rest of our message. This way, nobody except for the target server can read the data in the body of our packets.</p><p>Anytime we connect over basic HTTP, we’re sending our information like postcards, where anyone can read our messages right next to the address. In contrast, HTTPS is like a sealed envelope where the only information that can be seen is the address until it reaches its destination and a key is used to open that envelope.</p><p>If at any point during this process a response fails to come through, the sender will be aware that a packet has been dropped.</p><p>The sender must then decide how to react, often resending packets for a period of time in hopes that the connection can be restored. The common algorithms for making this decision are known as Cubic and NewReno. If multiple copies of the same packet arrive at a destination, any redundancies are simply ignored.</p><p>We know this is an HTTPS transaction because our browser decided to use <em>https:// </em>in the URL. Still, the request itself is formatted using the hypertext transfer <em>protocol</em>. So even if we say we’re using HTTPS, we’re still making an HTTP formatted request.</p><p>The connection process will be similar to the interaction we described with our DNS server, but we’ll be sending more information this time around.</p><p>Similar to IPv4 and IPv6, HTTP has experienced a few improvements over the years. The first version was published in 1991, identified as HTTP0.9 and it’s now obsolete.</p><p>Currently you can find many websites and browsers using HTTP version 1, 2, or 3. The latest version saw widespread adoption beginning in mid 2020, but regardless of which HTTP version we use several things are true.</p><p>The request will be broken up into multiple packets and reassembled at their destination based on the information provided in the packet headers. Sending and receiving packets will be the same as we already discussed as will be the TLS handshake for any new connections.</p><p>Similar to the tiny packets that carry our HTTP request, the request itself has both a header and a body.</p><p>The body contains any data pertinent to the transaction, while the header in our request tells our destination server all about the connection we wish to make. One thing the header will specify is the format of our request, such as a POST request that would commonly be used for sending your credentials to login to a website.</p><p>In our case however, we’ll be making a GET request.</p><p>This type of request is helpful in this situation because the body of a GET request is unnecessary and ignored by default. The only information that the web server needs to know is the path that we’re requesting to view.</p><p>We already know that our packets will need to hop across autonomous nodes to get to their target destination, but what happens when they arrive? Depending on the architecture, a variety of things might happen.</p><p>Continue reading to see some <a href="https://eddie-knight.medium.com/how-does-an-http-request-get-to-the-webserver-fd2d493ce2ed">common elements we might see on our journey</a> to <em>google.com</em>.</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae3b9ee066ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What difference is made by the type of internet service I have?]]></title>
            <link>https://eddie-knight.medium.com/what-difference-is-made-by-the-type-of-internet-service-i-have-b5d2ad79ecf2?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5d2ad79ecf2</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 22:43:35 GMT</pubDate>
            <atom:updated>2022-09-21T23:45:20.452Z</atom:updated>
            <content:encoded><![CDATA[<p>What difference does it make if you have fiber, digital cable, or something more ancient and mysterious?</p><p>This is a deep dive to answer the question above, as part of a larger question: <a href="https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240"><em>What happens when you type “google.com” into the browser and press enter?</em></a></p><p><a href="https://eddie-knight.medium.com/what-difference-is-made-by-the-type-of-internet-service-i-have-b5d2ad79ecf2">The technology that we’re using from our internet service provider has a big impact on speed</a>. But, regardless of the transmission type that we have, there will always be some sort of transformation that our packet needs to make so that it can ride along the waves or flash into the fiber lines.</p><p>This transformation is handled by the <em>modulator-demodulator</em> device, which we know as a <em>modem</em>.</p><p>An outdated or damaged modem may not be able to reliably transform everything it encounters, causing us to drop packets before they even leave our house. In our case, we’re assuming that we’ve maintained and updated our equipment properly so we can rely on the packets to safely leave our property and head out into the internet.</p><p>If you’ve ever heard someone describe the internet as a series of pipes or tubes, it may seem like a fairly convincing description. Instead of moving water through cylinders, we are pumping information as fast as we can along wires, but that simple analogy doesn’t help us understand the complexity of our process.</p><p>Water in a pipe is always water, regardless of who is sending and receiving it. A broken pipe still delivers water… just to the wrong place.</p><p>Of course, information in our inter-networked systems isn’t like water — specifically because it must be both interpreted and relayed. If at any point there’s a failure to properly <em>interpret </em>or <em>relay </em>the information, it will simply cease to exist.</p><h4>The closest example I can think to compare to is <strong>smoke signals</strong>.</h4><p>Imagine that we have a series of low-tech outposts that are each separated by a mile of forest or hills, blocking their ability to see signals from more than a mile away. We’ll leave an instruction manual in every on that a scout at the outpost can follow. It will tell them what to do in the event that they see smoke from a nearby outpost, or if the scout needs to send a message to another outpost.</p><p>Now let’s imagine that we are in one of those outposts and we need to send a signal to a location, 10 miles away.</p><p>We’ll follow the instructions to compose a message with smoke signals, but the smoke just rises up into the air. By itself the smoke is useless! The only value our message has is if the next outpost sees that message and <em>reacts </em>to it.</p><p>Upon seeing the signal, the next outpost consults its instructions, and then recreates the message exactly as we sent it. If at any point an outpost fails to recreate the message, it will not continue.</p><p>Unlike water, our smoke signal simply dies because it’s not been relayed correctly.</p><p>In the case of our inter-networked computers, there are a variety of network nodes where the message must be read and recreated. This includes our router, our modem, and the various stops at autonomous systems operated by our internet service provider. Only after a long series of hops will it reach the network of the machine that we’re trying to communicate with.</p><h4>When I first encountered the internet, we were using dialup everywhere.</h4><p>In order to transmit information, an uninterrupted telephone signal needed to be maintained. The digital packet would hop on a ride with electrical signals and the telephone lines, which are optimized along frequencies, designed to transmit voices.</p><p>While those electrical waves are great for carrying the shape of our voices across the globe, they can only move binary information so fast. If you’re still using telephone internet connection today, your modem is converting your digital signal into a telephone signal so that the bits can take a ride in an analog format.</p><p>As I mentioned in a previous article, analog simply means <em>non-digital</em> for most conversations. In the case of our internet connection, we know that the signal is analog when the signal functions as a wave, rather than imitating the on off signal of a computer.</p><p>On a telephone line, putting the on/off signals into wave format causes a severe restriction to the speed. Places with large demand for telephone and internet, such as Business and Universities used to be able to have more advanced lines installed, either using pre-modern fiber optics or just smashing a lot of telephone lines together. The most advanced business line during this era could support just under 10 gigabits per second.</p><p>Some of those advanced phone and internet lines served as a foundation for our modern fiber internet, as many use the same technologies.</p><p>Still the average consumer would need to send their packets over telephone lines, before the signal would hop onto the fiber lines of their service provider.</p><p>In my teen years, I was able to play Halo and Counter Strike Online because <em>DSL</em> internet was made available at my mother’s house in a middle class suburb.</p><p>It was only while writing the script for this video that I finally learned that DSL means <em>Digital Subscriber Line</em>, which isn’t surprising at all. DSL uses existing telephone lines, but operates outside of the vocal range of the electrical frequencies, and it allows the analog signal to better imitate a digital one. That also meant it wouldn’t hog the phone line while I was playing video games online!</p><p>For quite some time after that, the dominating force in the internet age was the <em>coaxial cable</em>, the same transmission line that was used to deliver sports news and sitcoms to our televisions.</p><p>Initially, cable internet was inarguably analog… using waves that just happened to be faster than phone lines. By 2010, nearly all analog cables were replaced by digital cables, which use wavelengths that operate with such drastic spikes that they closely resemble a digital on/off signal.</p><p>But (arguably) true digital communication was brought to households with the rise of fiber optic cables. These have existed between ISPs for decades, but they have recently been brought into homes more frequently.</p><p>Some arguments still exist on the internet as to whether fiber lines achieve a <em>true </em>digital signal, because technically it takes an amount of time for a light to be measured as “on,” and that period could be regarded as a wave if you squint hard enough.</p><p>Yet it remains that these lines do not need to adhere to the wave forms of existing telephone or cable lines. Data speeds can increase <em>dramatically </em>because the ones and zeros can be represented simply by whether the light in the line is all the way turned on.</p><p>Fiber lines like this are being laid all across the country, which means that your packet may be able to go from your house all the way to its destination server on the opposite side of the world without ever needing to be slowed down by conversion outside of a digital signal.</p><p>If you live in a rural area or someplace that hasn’t been upgraded to use fiber yet, you may find that you need to use satellite, telephone, or coaxial cable lines to transmit packets from your source to the destination that you’re trying to reach (Satellite, like Wi-Fi and radio communications, use human-safe electromagnetic radiation signals to send our digital data on a ride over the airwaves).</p><p>As we explored previously, there is a series of autonomous systems that are operated by the internet service providers helping our packets reach their destination. These network nodes will read the destination address from the IP header to determine the next appropriate step on our packet’s journey.</p><p>The node will then forward the packet along to the next destination. This process is sometimes called a <em>hop</em>.</p><p>There’s a chance that our packet will be dropped, failing to make it to the next hop if the target node has unexpected behavior or is experiencing congestion. It may also be dropped if the packet’s time to live or TTL value reaches zero.</p><p>Every time that the packet hops, the TTL value is decreased by one. If a node receives a packet with a TTL of zero, it will immediately discard the packet.</p><p>Now that we’ve explored how our packet may be flowing after it leaves our property, let’s go back to our packet and <a href="https://eddie-knight.medium.com/how-are-dns-and-http-transactions-secured-ae3b9ee066ed">follow it to the DNS server</a>.</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5d2ad79ecf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How does a browser use DNS and IP?]]></title>
            <link>https://eddie-knight.medium.com/how-does-a-browser-use-dns-and-ip-9849060c9b38?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9849060c9b38</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 22:03:16 GMT</pubDate>
            <atom:updated>2022-09-21T23:43:18.935Z</atom:updated>
            <content:encoded><![CDATA[<p>We know they’re <em>there</em>… but what are some finer points of this interaction?</p><p>This is a deep dive to answer the question above, as part of a larger question: <a href="https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240"><em>What happens when you type “google.com” into the browser and press enter</em></a><em>?</em></p><p><a href="https://eddie-knight.medium.com/what-does-a-browser-do-after-we-submit-a-url-7fd347ecd3f5">Our process has been running for some time now</a>… We’ve used our physical interfaces to type in google.com and we pressed enter while focused on our browser’s URL bar. The browser parsed our input, and determined that it needed to reach out to an external DNS (Domain Name System) server to find the IP address of <em>google.com</em>.</p><p>In order to reach that DNS server, our machine made an ARP (Address Resolution Protocol) request to the router asking for an address to the DNS server configured on our network. On our local machine, a process was created for this request and a socket or a port was assigned to execute the process.</p><p>Now, our process will reach out through the router and onto the internet provider, sending our request to the proper port on the DNS server.</p><p>The DNS server will have its own set of logic to process our request, search its database and provide the IP address corresponding to <em>google.com </em>as a response to our request.</p><p>The request we’re sending to the DNS server is a tiny piece of information formatted as a packet. If the size of the information we need to send exceeds a certain threshold, then it’ll be broken up across multiple packets.</p><p>Every single interaction we make online consists of a near infinite number of packets, just like this one that we’re about to send to our DNS Server. The packets we send from our computer are composed into binary format, like all digital information. The packet has a header and a body containing both our information and the instructions needed for it to be properly handled on its journey.</p><p>There are two versions of protocols that our packet may be formatted in… though the names deceptively imply a larger number of options. The first few concepts for an internet work protocol were never fully adopted, but as those were discussed in RFCs, they were each given an identifier. We know these as IPv0, IPv1, IPv2 and IPv3, but the first internet protocol to be fully adopted was IPv4.</p><p>For quite some time IPv4 was simply known as internet protocol. An experimental supplement was in development for more than two decades prior to 1995, intended to improve the internet protocol without replacing it. This was known as IPv5. Eventually however, IPv6 <em>was </em>developed to replace IPv4 with several improvements.</p><p>The most talked about upgrade for IPv6 is that it uses a 128 bit address space instead of the 32 bit used by its predecessor. This larger name space allows for dramatically more addresses and simplifies the packet headers, which resulted in increased speeds. Additional proposals have been made for version seven, eight, and nine of the internet protocol, but none of these have been adopted.</p><p>The two protocols that we may encounter on the internet as we know it today are IPv4 and IPv6. Using one of these internet protocols, the packet leaving our computer will be relayed through the router and into the realm of our internet service provider.</p><p>Keep reading to see more about how <a href="https://eddie-knight.medium.com/what-difference-is-made-by-the-type-of-internet-service-i-have-b5d2ad79ecf2">the type of internet service you have can influence the journey</a> we’re on.</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9849060c9b38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s this about a port number?]]></title>
            <link>https://eddie-knight.medium.com/whats-this-about-a-port-number-2ebf11c093c2?source=rss-b8c04d81b34f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ebf11c093c2</guid>
            <dc:creator><![CDATA[Eddie Knight]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 21:56:31 GMT</pubDate>
            <atom:updated>2022-09-21T23:44:06.585Z</atom:updated>
            <content:encoded><![CDATA[<p>Port numbers are used every time we connect to a process on another machine… but can we get some back story here?</p><p>This is a deep dive to answer the question above, as part of a larger question: <a href="https://eddie-knight.medium.com/is-the-internet-magic-5f28da0ff240"><em>What happens when you type “google.com” into the browser and press enter?</em></a></p><p>The port number (like the socket) serves as an identifier for the process that we want to interact with after our connection reaches that target server.</p><p>In the early days of networking engineers would use ports arbitrarily, because the port served as a sub address, much like an apartment building number, the decision to use one port or another didn’t have a large impact on anyone outside of the system.</p><p>It was expected that anyone networking to the system would know how to use it and what ports to target.</p><p>Back then, the concept of networking and host to host software was obscure and frankly unpopular, but an ARPA working group was created to lay the foundation for what would eventually become the internet as we know it today.</p><p>During their initial working sessions, the group decided to publish their notes as a series of findings, critical questions and recommendations. Starting with the first release, these notes were known as requests for comment or RFCs.</p><p>This channel of communication is still used today as the primary means of communication for the internet engineering task force, the internet architecture board, and to some extent, the global community of computer network researchers in general.</p><p>Today, the RFC list is managed by the internet engineering task force, but that wasn’t always the case. After joining ARPA in 1969, John Postel became the RFC editor and he continued serving his editor until his death in 1998. In those years, John Postel became known as the God of the internet, much to his own chagrin.</p><p>On March 26th, 1972, John Postel and another influential engineer named Vint Cerf published an RFC related to the numbering of what we now call ports.</p><p>RFC 322 called on network engineers to document how their sockets were being used and to establish a catalog of socket numbers. The RFC asked engineers to write a letter or make a phone call to describe the function and socket numbers of network service programs at each host.</p><p>After the results of this survey were published in RFC 433, the community of network engineers began to harmonize their socket numbering for what they called useful public services.</p><p>Following this transition, a network engineer could reliably predict the behavior of each port that was exposed on a network.</p><p><a href="https://eddie-knight.medium.com/how-does-a-browser-use-dns-and-ip-9849060c9b38">Now let’s hop back to our journey from the browser to the internet</a>.</p><h4>If you want to see more articles like this, please hit the “like” button (or hold it down!) so I know to create more content like this in the future.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ebf11c093c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>