How the Internet Works — The Basics

The internet might seem magical, but at its core, it's just millions of computers connected by wires (and some wireless signals) sending messages to each other. When you open lumora.camp in your browser, your computer sends a message across the internet to another computer (a 'server') that has Lumora's files. That server reads the message, grabs the right files, and sends them back to your computer. Your browser then takes those files and draws the website on your screen. This whole process — from typing the address to seeing the page — takes less than a second, even though the server might be thousands of miles away!

When you type 'lumora.camp', your computer doesn't actually know where that is. Computers find each other using numbers called IP addresses (like 142.250.80.46), not names. So first, your computer asks a DNS (Domain Name System) server: 'Hey, what's the IP address for lumora.camp?' The DNS server looks it up and responds with the number. It's like looking up someone's phone number in a contacts list. That's why it's called the internet's phone book — it translates human-friendly names into computer-friendly numbers.

Now your computer knows the server's address, so it sends a request. This is called an HTTP request (HyperText Transfer Protocol — just a fancy name for the set of rules computers use to talk to each other on the web). The request says something like: 'Hi server at 142.250.80.46, I'd like the homepage of lumora.camp please.' It travels across the internet, hopping through multiple routers and cables (sometimes even undersea cables across oceans!) until it reaches the right server. There are different types of requests: • GET — 'Send me this page' (most common, happens when you visit a URL) • POST — 'Here's some data, save it' (happens when you submit a form) • PUT — 'Update this information' • DELETE — 'Remove this'

The server receives your request, figures out what you want, and builds a response. The response includes: • A status code — a number that says what happened: - 200 = 'Success! Here's your page' - 404 = 'Not found' (you've probably seen this one!) - 500 = 'Something broke on the server' • The content — usually HTML, CSS, and JavaScript files that make up the web page Your browser receives all of this, reads the HTML (structure), applies the CSS (styling), and runs the JavaScript (behavior). And just like that — a website appears on your screen!

Let's trace what happens when you visit lumora.camp: 1. You type 'lumora.camp' and press Enter (0.0 seconds) 2. Your computer asks DNS for the IP address (0.1 seconds) 3. DNS returns the IP address (0.2 seconds) 4. Your computer sends an HTTP GET request to that IP (0.3 seconds) 5. The request travels through cables and routers to the server (0.5 seconds) 6. The server processes the request and builds the response (0.6 seconds) 7. The server sends back HTML, CSS, and JS files (0.8 seconds) 8. Your browser renders the page on screen (1.0 seconds) All of this in about a second! And this happens for every link you click, every image that loads, and every video you stream.