3hree6ix9ine

Notice to all followers and followees: my timeline is an LGTV agenda-free zone. I'm not interested in being lectured, guilt-tripped or bombarded with dogmatic rhetoric. Healthy discussions are one thing; force-feeding ideologies is another. From now on any tweets, retweets, or quotes pushing this agenda will earn you a quick block. My timeline should be a sanctuary for thoughtful dialogue, not ideological grandstanding.

The infant is not innocent; it is voracious, omnipotent in its demands, indifferent to the mother's exhaustion, and it is exhaustively this creature, barely tamed, that civilisation must daily re-contain

You do not desire the unavailable because you lack confidence, you desire the unavailable because availability threatens the distance that keeps the fantasy intact and the disappointment at bay.

The resistance in analysis is not obstruction, it is loyalty. The patient protects the symptom because the symptom has been, however painfully, the most reliable structure in a structureless life

How DNS Actually Resolves a Domain Name You type google.com and hit Enter. Before a single packet leaves your machine, your computer has to figure out where google.com actually lives. It doesn't know by default. What follows is a chain of questions and answers that most people never think about, even though it happens hundreds of times a day. Step 1 >> Your OS checks its own memory first Before any network call happens, your operating system looks at its local DNS cache. This is just a small table stored in memory that holds domain-to-IP mappings from previous lookups. Every record in that cache has a TTL (Time To Live) a countdown, measured in seconds, set by whoever owns that domain. If the record is still fresh, your OS uses it immediately and stops right there. No network. No waiting. Done. If the TTL has expired, the record is gone from cache and the query has to travel further. Step 2 >> The Recursive Resolver picks up the job If your cache is cold, your OS sends the query to what's called a Recursive Resolver. This is a server specifically built to hunt down DNS answers on your behalf. Your Internet Service Provider (ISP) usually assigns you one automatically. You can also configure your device to use a public resolver. Google runs one at 8.8.8.8, and Cloudflare runs one at 1.1.1.1. The resolver checks its own cache first too. If it's already looked up google.com recently for another user, it can serve the answer from memory without going any further. This is why popular domains resolve faster; resolvers have them cached constantly. Step 3 >>The Root Name Servers: "We don't know, but we know who does" If the resolver draws a blank, it contacts the Root Name Servers. There are 13 logical root server addresses (labeled a.root-servers.net through m.root-servers.net), but each one of these addresses is actually served by hundreds of physical machines spread across the globe. The technology that makes this work is called Anycast > multiple machines share the same IP address, and your query automatically gets routed to the closest one. The thing is: the root servers don't know where google.com is, but they know exactly who's responsible for every .com domain. So, they tell the resolver: "Go ask the .com TLD servers." Step 4 >> The TLD Servers narrow it down TLD stands for Top-Level Domain = the last part of a domain name (.com, .org, .ng, .uk, etc.). For .com, the TLD name servers are operated by a company called Verisign. These servers don't know the specific IP for google.com either, but they hold a registry of which name servers are authoritative for every .com domain. So, they respond: "Google's authoritative name servers are the ones you want." Step 5 >> The Authoritative Name Server gives the final answer This is where the chain ends. The Authoritative Name Server is controlled by the domain owner - in this case, Google. It holds the actual DNS records. The resolver asks it for google.com, and it responds with the IP address: something like 142.250.x.x. This answer travels back to your OS, gets cached at every layer along the way (with the TTL attached), and lands in your browser. Step 6 >> TCP/IP takes over Now your browser has the IP address. DNS is done. From here, your browser opens a TCP connection to that IP, a TLS handshake happens if the site uses HTTPS, and the server starts sending the page back. The entire DNS portion root server to TLD to authoritative name server is called Iterative Resolution, because the resolver is iterating through layers of authority. On a fast connection, this whole chain wraps up in under 50 milliseconds. On repeat visits, it's often 0ms because the cache already has everything. That's the full picture. Every domain you've ever visited went through this exact process at least once.

@buildwtim The most enduring architectures are often those constructed to keep a memory out, rather than to let the world in. When the drive to succeed becomes a form of structural defense, every achievement acts as another brick in a fortress..

@Braithee sometimes ambition just hides old wounds behind loud trophies... wonder how many feel that deep down :(

What passes for ambition in the marketplace is frequently the compulsion to compensate, to accumulate in public what was taken in private, to build high enough that the old shame cannot see over the wall.

Shame is not guilt's synonym, it does not say you did something wrong; it says you are something wrong, and this distinction is the difference between a correctable act and an irreparable self.

You're basically paying for raw power + premium parts + brand name + cool design, all packed into one machine. Every single component in it is chosen to be the best at what it does, and "the best" never comes cheap. Most laptop companies buy parts from other factories and just put them together. Alienware often designs their own motherboards and power systems to fit inside their specific machines. Because these parts are custom and not used by everyone else, they cost more to make. You are paying for all that extra engineering work that went into making sure everything fits and works together perfectly.

Civilization asks us to sublimate; to take the raw, volcanic energy of the instincts and redirect it toward the cathedrals, the creations, the theorems. The art is magnificent. The cost is never refunded.

The fear of intimacy is not the fear of closeness, it is the fear of being seen accurately, from the inside, by someone whose judgment you have, against all wisdom, decided to value.

Abundance serves as the primary signature. A single note might be a fluke, but a scale is an intention. These other worlds exist because the source of all things does not know how to stop at "enough." They are the overflow of a cup that remains forever full, a spill of light into the dark. Think of a library where most of the books are yet to be opened. Their presence on the shelves gives the room its weight and its silence. Even if the pages are never read, the fact that they contain potential is what defines the space. They represent the "perhaps" and the "what if" of a mind that is larger than any single story. Balance is the silent engine of the whole. A void with only one point of light is a lonely accident. A void filled with countless spheres is a deliberate design. These distant places act as the anchor for the center, providing the necessary scale to see the smallness of the self. Distance is a form of mercy. By placing worlds beyond the reach of the hand, the heart is kept in a state of wonder. It is a physical limit that forces the gaze to stay upward. The existence of the unreachable ensures that the horizon of the soul never truly ends.

Would you personally go on the first crewed Starship flight if the risk of death was 50%?

people don’t understand this: there’s no such thing as a purely “self-made” man. even if he did build everything from the ground up solo, requiring zero outside assistance, he cannot on his own “bring about” his riches. it is a matter of metaphysical impossibility. for it is God who mediates. it is God who gives the “ok”. I need you to hear this: all you can do throughout the day is to sweat blood. then go to sleep, absolutely uncaring about the results of your work. God will bless you to the extent of your effort. if not today, tomorrow. if not tomorrow, then after. and on top of it a thousand other blessings you didn’t even know were a thing. just move, in your heart the belief that the miracle will happen.

bro is blunt. he won't need a towel because he mops 'em up too well.

Identity is not discovered; it is constructed, painfully, from the debris of every identification that failed, every love that withdrew, every mirror that returned an unfamiliar face.

you go dey trust police man. oju e a bo

Let me break down the technical jargons Every time you load a webpage, the OLT is doing several things at once: broadcasting encrypted downstream data to all ONUs, managing upstream time slots dynamically via DBA so no two homes transmit over each other, and accounting for the fact that each home sits a different distance away. The passive splitter in the middle does none of this work, it is just glass bending light. All the intelligence is in the OLT. When your upstream feels erratic under heavy load, that is the DBA under pressure. When a misconfigured ONU on your street could theoretically read your traffic, that is the AES-128 encryption layer doing the only thing standing between you and your neighbour's data.

Ranging There is one more problem to solve. Each ONU is a different physical distance from the OLT, some 200 metres away, some 15 kilometres. If the OLT assigned identical transmission timing to all of them, the farther ONUs would deliver their data late, causing collisions. The OLT handles this through ranging, it measures the exact round-trip propagation delay to each ONU and uses that to calculate a precise equalization delay value. Each ONU is then instructed to apply an offset before it begins transmitting, so from the OLT's perspective, all ONUs appear to be at the same distance. The network behaves as if every home is the same length of cable away..

OLT = Device That Feeds Hundreds of Homes From One Fiber Before your internet data travels down the fiber cable to your home, it first passes through a piece of device sitting silently in a cell site/data centre near you = the OLT. Understanding how it works explains why your connection behaves the way it does. 🧵🧵