Ramblings

Introspective narcissism since the 2000s.

User Tools

Site Tools


internet

This is an old revision of the document!


Information Technology/Networking/
Internet

The internet is a loose collection of publicly available (ie. routable, connectable) computers. This definition on its own isn't very useful, but it will make sense shortly.

Much like you may have things on your device that you value (like photos, videos, music, word documents, powerpoint presentations, etc.), others may have things on their devices. Some of these people may, for one reason or another, want to share what they have with others. For example, I have a bunch of texts that I want to edit from anywhere and also be very easy to share and show to others. For this purpose, I put these texts on a computer in Karlsruhe, DE, which is quite literally what you are reading right now1). This computer is Karlsruhe is called a server. The possibilities are endless, but common services a server may provide are: Websites (ultracomfy.net, google.com, youtube.com) and file hosting (Google Drive, Onedrive). Most services fall into these two categories, often they're a bit of both. TikTok for example has a bunch of video files and presents them to you either on a website or in an app, which is just a very locked-down and customized internet browser.

1. What do you get from the internet?

In short, when you open a website, you connect to a computer, and that computer sends you files from its hard drive. The way these files work is no different from how files work on your own computer.

Most websites will send you the content of their website in .html format. html is similar to other file formats you may know such as .txt or .docx. Many older and/or simpler websites have a literal html sitting in a normal file directory. For example, let's imagine the computer responsible for example.com. It's just an example (example.com doesn't exist), but let's imagine someone set up a computer that they want to be reachable from the internet, and you can access it by typing example.com into your browser. The persons setting up that computer might place a .html file into D:\Website\index.html. When you connect to that computer, the computer will send back index.html which is what you will then see in your browser. On many older websites you will even see the name of the file in the URL bar: www.example.com/index.html 2).

On many websites, the forward slash in a URL actually denotes a file directory, so you get a glimpse of where a file may be located. So, if for example this:

example.com/index.html
D:\Server\index.html

Then

example.com/customers/1.html
D:\Server\customers\1.html

The forward slash in ultracomfy.net/internet denotes a directory, which lets you see in many cases where on the filesystem a file is located. So if www.example.com/index.html points to D:\Website\index.html, then www.example.com/customers/1.html points to D:\Website\customers\1.html. If you want, you can see this in action for yourself: When you right click the logo on this very website (the young link at the top left of the screen) and select “Open image in new tab”, you will see it will open in www.ultracomfy.net/_media/wiki/logo.png. /media/wiki/logo.png is the real file path on the real computer underneath. If this server were indeed in D:\Website\ then the full file path for this image would be D:\Website\media\wiki\logo.png.

For contrast, you can make your own website and load it into the browser.

<!DOCTYPE html>
<html>
<body>
Test
</body>
</html>

If you go to your Desktop, create a new file, call it Test.txt, copy and paste the text into it, save, rename it to Test.html and then double click, you will see it opens like a website in your browser. You will find that this is a website that is entirely empty except for one singular word: “Test”.

Notably, in the URL bar it will probably read something like this: file:///C:/Users/Username/Desktop/Test.html. You have just accessed a website with your browser that was on your own hard drive. The only difference between accessing a website on your own hard drive and accessing a website on the kajefhlkasjehflk

you could also right click anywhere on the website and select “Save Page As…”. If you save the website on your Desktop and then open ✎ Internet [Ramblings].htm, you will see the URL on the top now shows a local directory. Instead of ultracomfy.net/… it will probably show , depending on your configuration and assuming you're on Windows. The file:/// indicates that instead of working with data received from the internet, it is literally loading a local file (this is non-normal since your browser generally expects you to .

2. How do you get it?

When you look at your device, you will find that there isn't a cable running from your device all the way to Karlsruhe (in the exceedingly unlikely case that it actually is connected that way, you must be a datacenter employee and are slacking off. Get back to work.). Much more likely is that you are, say, on your phone, which is connected to WLAN. To be fair, there isn't a cable between your phone and the WLAN router either, but it still counts because they are able to communicate via radio waves. Only for a short distance, so don't think about just sending radio waves all the way to Karlsruhe, but it's far enough that your phone can exchange data with your WLAN router. This WLAN router, if it has an integrated modem, will be connected via wire into the wall. In the wall there is a cable that leads to a funny little box somewhere in or around the house where the internet cables of all the flats are wired together. From there, this box has a cable that goes underground and goes towards the street, where it joins the hundreds of other cables from other households towards the next junction. This junction might be situated on the next intersection, but it might be at the end of the block or neighborhood, or however your Internet Service Provider (ISP) has engineered your neighborhood's cable routes. Where the cables are laid depends very much on how your ISP has planned it out, in the same way that your electrical power provider constructs the power lines however they see fit. Nevertheless, this junction somewhere around your neighborhood will be connected to further junctions and to get towards Karlsruhe you will have to follow the cables “upstream”. At each junction there is a computer whose job it is to figure out the fastest way from where it is right now to where you want to go. Using tracert in the Windows command prompt you can see each of these computers as a signal you send travels from you to the destination machine.

Of course, there doesn't have to be a network junction at every road intersection (in fact, in most there isn't). So typically there will be some sort of long cables somewhere you might think of as “highways”. These may connect different cities or, in the case of the North America and Europe, deep sea cables connecting two entire continents. These typically transport the largest bulk of data traffic and are appropriately thick. Beware, though, that the constructor of the network may break up a highway at any point and place a computer somewhere in between, so just because you may see different computers in tracert doesn't necessarily mean that they are in different cities. If you are connecting to Karlsruhe from somewhere in the United States, your signal will likely be routed towards and then through the deep sea internet cables from New York City, United States, to somewhere in Europe, depending on how you get routed. From there, the signal will continue its route towards Germany.

The point is, what we think of as “the internet” has largely two components:

  1. One, the computer at the other end. Whether you're accessing a website, opening social media in an app, or playing an online video game, in each of these cases someone has prepared a computer somewhere with the kind of data your browser/app/game is looking for, and your browser/app/game gets that data by connecting to this computer.
  2. The second component is exactly this “connecting to it” part, which constitutes the thousands of miles of cables spanning our continents and the computers sitting at junctions deciding which way to route signals. For a connection to work, there must be an unbroken chain of data flow. You at home do this by plugging a router/modem-combination into the wall plug and then connecting to it wirelessly or by plugging cables from it to your computer (or other intermediary devices). Then the chain must continue to be unbroken in transit towards the target computer, which is why construction sites on roads have the tendency to disrupt the neighborhood's internet if they, in their construction effort, hit the cables underneath the road. Finally, much like yourself, the social media platforms have computers which are connected to “the wall” in much of a similar way as your devices are. The biggest difference is that they do it on a much, much larger scale than you do (as they typically operate hundreds of computers at once, in multiple locations), but functionally it is very similar (though datacenters at these scales get some special affordances to facilitate the large data flow expected here, your neighborhood connection isn't built to facilitate gigabytes or even terabytes of traffic per second).

This is also the difference between WLAN and mobile data. WLAN is facilitated by a router/modem-combination in someone's wall. Signals from your phone or computer go to that router/modem-combination and then follow the junctions and highways as detailed. When you turn off WLAN on your phone and enable mobile data, it instead radio's data to the nearest cell tower. It too is basically just a fancy receiving and sending installation of radio signals, but much much more powerful than your WLAN router at home (still not far enough to get you all the way to Karlsruhe, unless you're already there). When your phone radio's to that cell tower, the signal will be received by the dish at the top of the tower and be led all the way down and then underground through cables laid out. From there, it will feed into its local junctions.

Connection via WLAN and connection via cellular data are different, even if the end result might look quite similar on the surface. The primary difference is that they are often operated either by different companies, or by different subsections of the same company. For example, if you're a German you might have a broadband contract with Deutsche Telekom. They provide you with the cable in the wall and may own and operate the cables on the roads around your neighborhood, too3). Telekom, to a large degree, will also own some of the highways nearby and generally your traffic will be routed along Telekom-owned cables for a good while. However, your phone might have a SIM card and contract with Vodafone, so if you connect via cellular data, you will be connecting to a Vodafone cell tower4). They themselves will route you through cables that they own. The point is, the route your signal travels is very different when you access the internet from your WLAN as opposed to cellular data.

1)
The only difference between actual, literal text, and what you are reading right now is that this text is managed by a wiki software called DokuWiki, which is similar to but much simpler than MediaWiki, the software on which Wikipedia runs.
2)
Even on ultracomfy.net you would see the name of the file you're accessing, but there are ways to make URLs look nice so instead of ultracomfy.net/doku.php?id=internet you are seeing www.ultracomfy.net/internet (you can try either, they both work). doku.php in this case is the file you're accessing
3)
There is a bit of drama here with connection subcontracting where a different company (say, company B) can buy the rights to operate on company A's cables. Therefore, even if you have a contract with company B, the physical wires in and around your house are the business of company A and they're the ones you will be compaining to when it doesn't work.
4)
Or whoever they subcontracted from.
internet.1794908792.txt.gz · Last modified: by ultracomfy

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki