From 74e96a1d56e685b5ff64e300293063ca2a38b0a0 Mon Sep 17 00:00:00 2001 From: Drew Date: Sat, 15 Nov 2025 17:11:49 -0500 Subject: [PATCH] add 935 notes --- Drew/drew_927.md | 31 --- Drew/drew_928.md | 150 ----------- Drew/drew_929.md | 107 -------- Drew/drew_929_matt.md | 34 --- Drew/drew_929_nate.md | 31 --- Drew/drew_931.md | 454 -------------------------------- Drew/drew_932.md | 194 -------------- Drew/drew_932_mini.md | 166 ------------ Drew/drew_933.md | 595 ------------------------------------------ Drew/drew_935.md | 58 ++++ 10 files changed, 58 insertions(+), 1762 deletions(-) delete mode 100644 Drew/drew_927.md delete mode 100644 Drew/drew_928.md delete mode 100644 Drew/drew_929.md delete mode 100644 Drew/drew_929_matt.md delete mode 100644 Drew/drew_929_nate.md delete mode 100644 Drew/drew_931.md delete mode 100644 Drew/drew_932.md delete mode 100644 Drew/drew_932_mini.md delete mode 100644 Drew/drew_933.md create mode 100644 Drew/drew_935.md diff --git a/Drew/drew_927.md b/Drew/drew_927.md deleted file mode 100644 index daa8cbe..0000000 --- a/Drew/drew_927.md +++ /dev/null @@ -1,31 +0,0 @@ -## Mini Topic -Picture this: You're sitting there with your innocent-looking UM890Pro humming quietly on your desk, and your friends are like "Oh cute mini PC," not knowing there's a nuclear-powered H100 beast lurking in that OCuLink enclosure ready to solve their entire codebase in 0.3 seconds. -H200 - -## The Technical Challenge - -GNOME developers found it "difficult to cleanly separate GDM's ability to launch modern X11 sessions (which we intended to keep enabled in GNOME 49) from the rest of GDM's X11 integration (which we intended to disable but leave intact for GNOME 49)" - -The original plan for GNOME 49 was sophisticated: disable legacy X11 features in GDM while keeping the ability to launch modern X11-based desktop environments like XFCE, MATE, and Cinnamon. However, when the x11-support switch was turned off, it didn't just disable old features like XDMCP - it also stopped GDM from even looking at /usr/share/xsessions, which meant no X11 desktops would show up on the login screen - -## Why This Matters - -This created a real problem for users who rely on other desktop environments. Many distributions ship GNOME 49, and users need to be able to launch X11 desktop sessions for environments like Cinnamon, XFCE, and older window managers without major breakages - -## The "Temporary" Solution - -This return of X11 support is only temporary. The GNOME developers are clear that their intention hasn't changed: X11 is still being phased out, with the updated timeline now pointing to GNOME 50, where most of GDM's X11 code will be removed outright - -It's important to note that while GDM can launch X11 sessions in GNOME 49, you still can't run GNOME Shell on X11 since that has been disabled, as has X11 support in gnome-session - -So rather than a philosophical backtrack, this was more of a "we need to get the technical architecture right before we can cleanly separate these components" decision. GNOME's Wayland-first vision remains unchanged - they just realized they needed more time to properly separate the legacy parts from the modern session-launching capabilities. - ---- - -Meanwhile, dwm users are just sitting there like "X11 never left, what's the problem?" ๐Ÿ˜„ - -The irony is that GNOME's complexity is what's making this transition so difficult for them. They built this massive display manager with tons of legacy features, and now they can't untangle it cleanly. But for dwm users, X11 just works - no display manager bloat, no session management complexity, just a simple window manager doing exactly what it needs to do. - -It's like watching someone try to renovate a mansion while you're perfectly happy in your minimalist cabin that never needed renovating in the first place. The joke writes itself: "GNOME discovers what suckless users knew all along - sometimes simple is better." - -Plus, given that dwm is literally designed around X11's core concepts, Wayland support would fundamentally change what dwm even is. So yeah, X11 is definitely still #1 for the dwm crowd, and GNOME's struggles just prove that sometimes the "legacy" solution is the one that actually works reliably! diff --git a/Drew/drew_928.md b/Drew/drew_928.md deleted file mode 100644 index c68c1a6..0000000 --- a/Drew/drew_928.md +++ /dev/null @@ -1,150 +0,0 @@ -# The Perfect Linux Setup -*A workflow designed for deep work with zero cognitive overhead* - -## The Philosophy - -Each tool serves exactly one purpose, nothing overlaps, everything persists. This isn't about impressive features - it's about **disappearing technology** that gets out of your way so you can focus on what matters: your work. - -## Hardware Foundation - -**UM890M Pro + AOC 34" Ultrawide**: Desktop performance in a tiny footprint with massive horizontal real estate. The combination creates a spatial canvas where your workflow can breathe. - -**Why This Works**: The ultrawide eliminates multi-monitor complexity while giving you the space to think in "zones" rather than cramped windows. The mini PC delivers power without noise, heat, or desk clutter. - -## Multi-Context Mastery - -### 12 Intelligent Workspaces -Each of your 12 tags maintains its own layout, gaps, and window arrangement. You can have: -- A dedicated research workspace (WS1) with Firefox-ESR and organized tabs -- A business workspace with documents and communication tools -- A content creation workspace optimized for video production -- A project development workspace for open source work -- Each optimized for its purpose and **remembered** - -### Cross-Device Research Flow -Firefox-ESR on workspace 1 with Floccus bookmark sync creates your dedicated information gathering environment. Floccus keeps your research bookmarks synchronized across all devices, so materials you bookmark during mobile research are instantly available in your desktop workflow. - -**The Research Advantage**: WS1 becomes your knowledge hub - browser tabs organized for current projects, bookmarks synced for continuity, all in a stable ESR environment that won't break your workflow with experimental features. - -### Spatial Intelligence -With `windowfollow` and `focusadjacenttag`, you fluidly move between adjacent workspaces and automatically follow windows you move. Combined with your ultrawide, this creates a spatial workflow where you think in "zones" rather than discrete windows. - -**The Mental Model**: Your workspaces become extensions of your thinking. Moving between them feels like shifting attention, not managing technology. - -## Instant Access Tools - -### Scratchpad Mastery -Drop-down terminals and audio mixer accessible from anywhere - no context switching needed for quick tasks. Your workflow never breaks. - -- **Primary Terminal** (`Super+Shift+T`): Universal command line that appears instantly -- **Audio Control** (`Super+Shift+A`): Volume and audio settings without leaving your context - -**The Power**: Tools come to you, not the other way around. Stay in flow, handle quick tasks, return to focus. - -## Persistent Organization - -### State That Survives -`preserveonrestart` and `attachbottom` mean your carefully arranged workspace survives config changes and new windows don't disrupt your focus. `restartsig` lets you reload configs without losing state. - -**What This Means**: Experiment freely, restart when needed, know that your workspace will be exactly as you left it. No fear of losing your perfect arrangement. - -### Visual Clarity -16px gaps, status2d colored bar, and `alwayscenter` for floating windows create visual breathing room. Your eyes can parse information quickly across that 34" ultrawide. - -**The Effect**: Information hierarchy becomes obvious. Your brain doesn't waste energy parsing visual chaos. - -## Minimal Friction Work - -### The Multi-Hat Workflow -Geany for script editing and documentation + your automated gitup script + WezTerm + scratchpad terminal means you can seamlessly switch between business work, content creation, and project development without losing momentum. - -**The gitup Revolution**: No more clicking through GUI dialogs or remembering git commands. Your script handles the entire workflow - shows changes, accepts natural commit messages, pushes automatically. Project updates become frictionless whether you're updating documentation, fixing scripts, or committing new features. - -**Traditional Multi-Role Struggle**: -1. Business meeting ends, need to switch to content work -2. Navigate between different applications and windows -3. Remember git commands and workflow steps -4. Handle different tools for different types of work -5. Lose context and momentum with each transition -6. Spend time reorganizing your workspace -7. Repeat constantly throughout the day - -**Your Optimized Multi-Role Flow**: -1. Finish business work in dedicated workspace -2. Switch to content creation workspace (OBS already positioned) -3. Move to project workspace for script development -4. Run gitup script from anywhere for instant commits -5. Each environment remembers its optimal state - -### The Sticky Advantage -The sticky patch lets you keep reference windows visible across all contexts. Documentation, communication, monitoring - always visible when needed. - -## Workflow Intelligence - -### Automatic Window Placement -Applications automatically land where they belong: -- Firefox-ESR โ†’ Workspace 1 (Research and web workflow with Floccus bookmark sync) -- Terminal with gitup script โ†’ Quick project updates anywhere -- Discord โ†’ Workspace 7 (Community communication) -- OBS โ†’ Workspace 9 (YouTube content creation) -- Gimp โ†’ Workspace 8 (Thumbnail and graphics work) - -**No Manual Organization**: Your computer learns your multi-role workflow and maintains it automatically. - -### Layout Memory -Each workspace remembers its optimal configuration. Switch to your research workspace (WS1) - Firefox-ESR opens with your organized tabs and Floccus keeps bookmarks synced across devices. Move to your business workspace - documents and communication tools are already arranged. Jump to your YouTube workspace - OBS and editing tools are positioned for content creation. Switch to your project workspace - Geany and terminals are laid out for script development. - -### Adjacent Workspace Flow -Move between related contexts fluidly. Business work โ†’ Content planning โ†’ Script development โ†’ Community interaction โ†’ Project documentation. The spatial relationship matches your mental model of how your different professional roles connect and flow together. - -## The Compound Effect - -### Cognitive Load Elimination -Every micro-decision removed: -- Where should this window go? *Automatic* -- How should this workspace be arranged? *Remembered* -- Where's my terminal? *Scratchpad* -- How do I commit this code? *One script* - -### Flow State Preservation -- **Visual Consistency**: Dark theme reduces eye strain across 8+ hour work sessions -- **Predictable Behavior**: Every action has the same result every time -- **Persistent State**: Your environment survives interruptions -- **Instant Access**: Tools appear when needed, disappear when not - -### Deep Work by Design -This setup creates an environment where: -- Context switching becomes fluid, not jarring -- Tool management becomes invisible -- Visual parsing becomes effortless -- State persistence becomes automatic - -**The Result**: You think about your work, not your tools. You solve problems, not interface puzzles. You create, not configure. - -## The Complete System - -**Hardware**: UM890M Pro + AOC 34" Ultrawide -**OS**: Debian Stable -**WM**: Custom DWM with 17 carefully chosen patches -**Terminal**: WezTerm with productivity-focused keybindings -**Editor**: Geany with git integration and tree browser -**Auth**: Proton Pass -**Notifications**: Dunst -**Git**: Custom automated workflow script - -## Why It Works - -This isn't about having the latest features or the most impressive rice. It's about creating a **cognitive extension** - technology that amplifies your thinking rather than fighting it. - -Every element serves the goal of **sustained deep work**: -- Spatial thinking with ultrawide zones -- Context preservation across interruptions -- Instant access to essential tools -- Visual clarity that reduces mental load -- Predictable behavior that builds confidence - -**The Philosophy**: The best technology is invisible technology. When your tools disappear, only your ideas remain. - ---- - -*A workflow where every optimization compounds into something greater than the sum of its parts - an environment designed for thinking, creating, and building without technological friction.* diff --git a/Drew/drew_929.md b/Drew/drew_929.md deleted file mode 100644 index c2c58c5..0000000 --- a/Drew/drew_929.md +++ /dev/null @@ -1,107 +0,0 @@ -**Here's your podcast setup:** - -So I've got two fascinating articles here that paint this absolutely wild picture of where we're headed with technology - and they're connected in the most ironic way possible. - -**Article one** is from the New York Times, basically saying "Hey, smartphones are dead, AI is taking over everything." We're talking smart glasses that watch everything you do, AI pendants that record every conversation, ambient computing with microphones in every room. The whole premise is that AI assistants will just... do everything for us. No more apps, no more interfaces - just tell your AI what you want and it handles it. Apple, Meta, Google, Amazon - they're all betting big on this future where we essentially give up control to our digital assistants. - -**Article two** is about how AI is creating this massive nostalgia wave for the '80s and '90s - except it's all fake. We're talking AI-generated videos of teenagers from 1995 telling us how much better life was before the internet, before smartphones, before social media. And here's the kicker - these videos are getting millions of views from people who weren't even alive in the '90s! They're literally creating false memories of a past that never existed. - -**The connection is bonkers**: The same technology that's promising to control our future is simultaneously creating fake memories of a "better" past. People are so fed up with current tech that they're embracing AI-generated lies about how great things used to be, while tech companies use that same AI to build an even more invasive future. - -It's like we're stuck between a fake past and a dystopian future, and somehow nobody's asking: "What if we just built technology that actually served users instead of controlling them?" - -*That's* where the Linux angle comes in... - ---- - -## **๐ŸŽฏ KEY DISCUSSION QUESTIONS** - -**๐Ÿค– If people are literally watching AI-generated content about how much better life was before computers... why exactly are we rushing toward AI-controlled everything?** -*I mean, come on - the irony is thicker than my old Ubuntu install CDs. We're using robots to tell us robots ruined everything, then building more robots to fix it.* - -**๐Ÿ•ถ๏ธ What happens to user privacy when your smart glasses, AI pendant, AND ambient home speakers are all recording 24/7?** -*Spoiler alert: The answer rhymes with "schmurveillance schmapitalism." At least when Big Brother was watching, it was just one brother, not an entire extended family of corporate siblings.* - -**๐Ÿง Could this anti-tech nostalgia actually be an opportunity for Linux and open source?** -*Think about it - people want computing that doesn't suck their soul out through a straw. Linux has been offering that since before these AI nostalgists pretend the '90s were invented.* - -**๐ŸŽญ When Vanilla Ice is your voice of reason about technology... haven't we maybe jumped the shark?** -*The man who gave us "Ice Ice Baby" is now the sage elder warning us about computers. I don't know whether to laugh or install Gentoo and go live in the woods.* - -**๐Ÿ”ฎ What would computing look like if we combined actual '90s values - you know, user control, privacy, community - with modern capabilities?** -*Hint: It might look suspiciously like what the Linux community has been building all along, just saying...* - -**๐Ÿ“ฑ Are we watching the tech industry eat itself? AI creates fake nostalgia about pre-digital times while simultaneously trying to make computing even more pervasive?** -*It's like watching someone sell you poison and the antidote at the same time, except the antidote is also poison, and they're charging subscription fees for both.* - ---- - -**Oh man, THIS is the real kicker right here!** - -You've hit on something genuinely dystopian hiding in plain sight. We're basically watching the creation of a **two-tier computing society**: - -**Tier 1: The AI-Assisted Masses** -- Smart glasses that "help" by watching everything -- AI pendants recording every conversation -- Ambient computers listening in every room -- Zero understanding of how any of it works -- Complete dependence on corporate AI overlords - -**Tier 2: The Linux Holdouts** -- Still compiling their own kernels like digital preppers -- Running local AI models they actually control -- Understanding what their computers are doing and why -- Basically becoming the equivalent of people who can still start a fire without matches - -**The scary part?** This isn't some sci-fi future - it's happening RIGHT NOW. How many people do you know who could survive if their iPhone died and they had to use a command line? We're already seeing this split. - -**๐Ÿ”ฅ DISCUSSION ANGLES:** - -**Is Linux accidentally becoming a form of digital resistance?** -*When everyone else is letting AI "optimize their life," Linux users will be the weirdos who still know how to actually USE computers instead of just talking to them.* - -**Will "computing literacy" become like knowing Latin - something only scholars and rebels bother with?** -*Imagine explaining `grep` to someone whose entire computing experience is "Hey Siri, do the thing."* - -**Could this actually be... good for Linux adoption?** -*When the AI bubble inevitably pops and people realize they've given up all agency over their digital lives, guess who's going to look pretty smart?* - -**Are we creating a world where the only people with real digital privacy are the ones geeky enough to compile their own operating systems?** -*That's simultaneously the most Linux thing ever and also terrifying for democracy.* - -It's like we're heading toward a future where knowing how to install Arch Linux is equivalent to knowing how to grow your own food - a weird survival skill that most people think is unnecessary until suddenly it very much isn't. - -**YES! The sheep and the wolves - that's PERFECT!** - -We're literally watching the creation of two completely different species of computer users: - -**๐Ÿ‘ The Sheep:** -- "Hey AI, plan my day, order my coffee, text my mom" -- No idea what's running on their devices or who's listening -- Completely dependent on corporate shepherds (Google, Apple, Meta) -- Think privacy settings are just another thing for AI to optimize -- Will panic if their smart glasses break because they've forgotten how to navigate the world manually - -**๐Ÿบ The Wolves:** -- Reading kernel changelogs for fun on weekends -- Running their own servers, their own AI models, their own everything -- Actually understanding the difference between open source and "AI-powered" -- Treating every new Google/Apple announcement like a threat assessment -- Probably the only ones who'll know how to function when the AI servers go down - -**The wildest part?** The sheep think they're getting convenience, but they're actually becoming MORE dependent and vulnerable. Meanwhile, the wolves are getting MORE capable and self-sufficient. - -**๐ŸŽฏ THE REALLY DARK QUESTION:** - -* Are we heading toward a future where only tech-savvy users (like Linux users) maintain control over their computing? - - -**Will the wolves eventually have to protect the sheep from their own technology?** - -*Picture this: The AI nostalgia content creators are already manipulating millions of people with fake memories. What happens when every piece of media, every "recommendation," every "helpful suggestion" is AI-generated and designed to extract value from users who don't even know they're being farmed?* - -**The Linux community might accidentally become the immune system of human computing freedom.** - -It's like we're heading toward a world where knowing how to configure your own firewall becomes equivalent to knowing how to spot a pickpocket - except the pickpocket has convinced everyone else that getting robbed is actually a premium lifestyle service. - -The sheep are paying for the privilege of being fleeced, and the wolves are just sitting there with their self-compiled kernels going "This seems... not great." diff --git a/Drew/drew_929_matt.md b/Drew/drew_929_matt.md deleted file mode 100644 index ff51c86..0000000 --- a/Drew/drew_929_matt.md +++ /dev/null @@ -1,34 +0,0 @@ -Perfect! Now I have the full Ars Technica article. Here's the complete summary with all the juicy details: - ---- - -## **๐Ÿ“ฑ MATT'S ARTICLE: Google's Chrome AI Expansion (Ars Technica)** - -**Summary**: Google is rolling out what they call "Chrome's biggest upgrade ever" with comprehensive AI integration. Key features include: - -- **Gemini Button**: Opens a popup to ask questions about content across ALL your open tabs -- **AI Mode in Address Bar**: Can now start AI searches directly from the omnibox, with "ask about this page" functionality -- **Cross-App Integration**: Gemini connects to Calendar, YouTube, and can find links in your history based on vague memories -- **AI Security**: Enhanced scam detection for fake virus alerts and phony giveaways, plus one-click automatic password changes -- **The Big One - Agentic Browsing**: Coming later this year, Chrome will get AI agents that can control your cursor to complete tasks like "scheduling a haircut or ordering groceries" - -**The Ars Technica Reality Check**: The article notes these agents are "slow and expensive" - OpenAI's Operator costs $200/month and Anthropic's agent "may rack up a few dollars in API charges for completing a simple action like visiting a handful of webpages." - -## **๐ŸŽฏ ENHANCED LINUX/FOSS DISCUSSION POINTS** - -**๐Ÿค– The Agentic Apocalypse** -*This isn't just AI assistance - it's AI literally controlling your computer cursor. Google is planning to let AI click buttons and fill out forms on your behalf. What could possibly go wrong?* - -**๐Ÿ’ธ The Cost Reality** -*Ars Technica points out that competing AI agents cost $200/month or "a few dollars" per simple task. Google hasn't announced pricing, but "allowing billions of people to tinker with an expensive computer-use model might be a tough sell even for Google."* - -**๐Ÿ”’ Privacy Doomsday Scenario** -*Gemini can now read ALL your open tabs, your browsing history, AND will soon control your mouse clicks. It's like giving Google a complete recording of your digital life plus remote control.* - -**๐Ÿบ The Wolf's Dilemma** -*While Chrome users will have AI clicking buttons for them, Git developers are debating whether requiring Rust knowledge makes their tool too complex. The irony is perfect - casual users get maximum hand-holding while developers get maximum complexity.* - -**๐ŸŽญ The Ultimate Question** -*If AI can control your browser to "order groceries," why do we need developers to understand memory management in Rust? Are we creating a world where only the people building the tools need to understand anything, while everyone else just... talks to their computer?* - -The sheep vs. wolves divide just got way more extreme. Chrome users will literally have AI operating their computers for them, while Git contributors need to master advanced programming concepts just to commit code. It's like we're splitting into two species: the completely dependent and the hyper-technical, with nothing in between! diff --git a/Drew/drew_929_nate.md b/Drew/drew_929_nate.md deleted file mode 100644 index 423ceba..0000000 --- a/Drew/drew_929_nate.md +++ /dev/null @@ -1,31 +0,0 @@ -Perfect! Now I have the actual Phoronix article text. This gives me the exact details I need. Here's the updated summary: - ---- - -## **๐Ÿฆ€ NATE'S ARTICLE: Git Considering Mandatory Rust (Phoronix)** - -**Summary**: Git developers are debating making Rust support mandatory, with the decision potentially affecting Git 3.0. Git 2.49 already introduced a Rust foreign function interface as optional, but Patrick Steinhardt's RFC proposes making it required. The three-fold goal is to: experiment with Rust infrastructure, give distributors time to adapt (since "introducing Rust is impossible for some platforms and hard for others"), and announce that Git 3.0 will make Rust mandatory. Notably, Git 3.0 will also default to SHA-256 hashing. - -**The Platform Problem**: The article specifically notes this "would restrict the architectures and platforms where Git could be deployed compared to the current C code." - -## **๐ŸŽฏ THE PERFECT PODCAST TRIFECTA** - -Now we have three articles that create this beautiful progression: - -1. **Your Articles**: The big picture - AI taking over vs. fake nostalgia, creating sheep vs. wolves -2. **Matt's Chrome Article**: The sheep get ultimate hand-holding - AI will literally click buttons for them -3. **Nate's Git Article**: The wolves get ultimate complexity - must master Rust just to use version control - -## **๐Ÿ”ฅ THE ULTIMATE IRONY** - -**Chrome Users in 2025**: "Hey Google, order my groceries and schedule my haircut while I watch TikTok" - -**Git Contributors in 2025**: "Before we can commit this three-line bug fix, let's have a 47-message thread about ownership semantics in Rust and whether this breaks compatibility with NetBSD on SPARC" - -**The Comedy Gold**: While Chrome AI agents are spending "a few dollars in API charges" just to visit a handful of webpages, Git developers are worried that requiring Rust knowledge might exclude some contributors. - -It's like we're creating a world where clicking a button costs money and computational resources, but understanding memory management is considered a basic requirement for version control. The machines are getting dumber and more expensive while the humans are expected to get smarter and more specialized. - -**Perfect Linux Cast Question**: *Are we witnessing the creation of a two-caste system where the "users" become completely helpless while the "builders" become increasingly gatekept by complex requirements?* - -The sheep are paying premium prices to have AI do basic tasks, while the wolves are debating whether Rust requirements make their fundamental tools too exclusive. Nobody's asking: "What if we just built tools that were both powerful AND accessible?"gitea diff --git a/Drew/drew_931.md b/Drew/drew_931.md deleted file mode 100644 index 1ee154c..0000000 --- a/Drew/drew_931.md +++ /dev/null @@ -1,454 +0,0 @@ -# Episode 191 - Talking Points (Conversational Style - REVISED) - -## Mini Topic: Light Mode vs. Dark Mode - The Eternal Struggle - -### How to Start This -**Matt or whoever opens:** "Alright, before we dive into security stuff, we gotta settle this once and for all. Light mode or dark mode?" - -**Expected chaos:** -- Someone immediately says "dark mode obviously" -- Someone else: "Light mode during the day, fight me" -- Someone: "I use Solarized and it's the perfect compromise" -- Everyone else: "Solarized is ugly" - -### The Terminal Light Theme Jump Scare - -**This should be a major talking point:** - -"You know what's the WEIRDEST experience though? When you're in the terminal and suddenly you get hit with a light theme. Like, you're expecting your nice dark terminal, you hit a key combination or open a new tab, and BAM - white background, black text, your retinas are on fire." - -**Pile on with examples:** -- "Or when you SSH into a server and THEIR default terminal is light mode. I'm like 'what kind of psychopath set this up?'" -- "The worst is when you're pair programming or screen sharing and someone opens their terminal and it's just... blinding white. You can SEE people recoil." -- "I've literally seen people in the chat go 'dude can you please switch to dark mode, I can't see your stream' because the light terminal is burning their eyes through the screen." - -**The debate starts:** -"But here's what's weird - some people PREFER light terminals. They're out there. Walking among us." - -"I think it depends on your environment though, right? Like, if you're coding in a bright office with windows everywhere, maybe light mode makes sense? But if you're at home at 10 PM... why are you doing this to yourself?" - -**The configuration nightmare:** -"And here's the thing - you have to configure this in like four different places: -- Your terminal emulator has a theme -- Your shell prompt has colors -- Your tmux has its own colors -- Vim/Neovim has its own color scheme -One of these is ALWAYS going to be wrong." - -**Someone needs to mention:** -"I switched everything to dark mode years ago. But every once in a while I'll install something new - new terminal emulator, new system - and I forget to change the theme. I open it and it's like getting flashbanged by my own computer." - -"It's worse than opening Discord light mode. At least with Discord you know what you're getting into. The terminal is supposed to be YOUR space. Your sanctuary. And then it betrays you with a light theme." - -### The Broader Discussion - -**Keep it going:** -"Okay but seriously, who here uses light mode for ANYTHING? *[wait for responses]* See, that's what I thought. Nobody admits it in public, but then you look at screenshots online and half of you are using light mode in your browser." - -"I think the real question is - are the people who auto-switch between modes just indecisive, or are they actually evolved beyond the rest of us?" - -**Hot takes to throw out there:** -- "Discord light mode is a war crime" - see if anyone defends it -- "VS Code's default light theme makes me feel like I'm working in Microsoft Word" -- "Real talk though - can you actually read dark mode in sunlight? Because I can't. I'm just squinting at a black screen." -- "The best compromise: dark mode, but turn your screen brightness up. You get the aesthetic without destroying your ability to see." - -**For the Debian angle:** -"Here's the thing about Debian though - whatever theme you pick, it's gonna work. It's gonna work in three years. It's gonna work through two system upgrades. GNOME might break your extensions, but your terminal colors? Solid." - -"I installed GNOME Terminal on Debian in 2019, set it to dark theme, and it's never changed. That's the Debian guarantee - boring consistency." - -**Good question to ask each other:** -"When did you switch to dark mode? Was there a specific moment?" -- Everyone has a story about eye strain or coding at night -- Or someone who still hasn't switched and defends light mode - -**The philosophy:** -"I think dark mode is like Linux itself - once you switch, you can't go back. You try to use someone else's light mode setup and you're like 'how do you LIVE like this?'" - -"But we also need to acknowledge that we're basically digital vampires at this point. We've adapted to work in the dark. Normal people don't care this much about terminal color schemes." - -**Wrap it up with:** -"Alright, we've established that: -- Dark mode users are vampires who code at 2 AM -- Light mode users are masochists with too much screen brightness -- People who switch automatically can't commit to anything -- And getting surprised by a light terminal is the tech equivalent of stepping on a Lego - -The configuration nightmare: -"Although the frustrating part is everything has its own theme system: - -Browser: GTK theme mode -Gmail/Google Drive: light theme -Proton Mail: light theme -Terminal emulator: dark theme -Vim/Neovim inside the terminal: its own color scheme -Geany -Shell prompt colors: another thing to configure - -Moving on before this gets violent!" - ---- - -## Main Topic: Security Practices Every Debian User Should Follow - -### Opening This Topic - -**Suggested intro:** -"So here's the thing - you all switched to Linux for privacy and security, right? That's what we all say. But if I looked at your systems right now, how many of you have actually... secured them? *[pause for effect]* Yeah, that's what I thought. Let's talk about what we should be doing versus what we're actually doing." - -**Alternative opening:** -"Debian's supposed to be the stable, secure choice. And it is! Except... it's only as secure as you make it. And I'm willing to bet most of us are running around with default configs and hoping for the best." - ---- - -### 1. Updates (The Most Basic Thing Everyone Ignores) - -**Start with a question:** -"When's the last time you updated your system? And I mean actually updated, not just thought about updating." - -**The conversation:** -"Right, so Debian Stable - people hear 'stable' and think that means 'I never have to update.' No! It means the packages are stable, not that you ignore security updates!" - -"The funny thing is, Debian makes this SO easy. It's literally `apt update && apt upgrade`. That's it. But I guarantee half of us see 'X packages can be upgraded' and just... close the terminal." - -**Someone should mention:** -"I installed `unattended-upgrades` like two years ago and honestly forgot about it. Best decision ever. Security updates just happen." - -**Counter-argument time:** -"Okay but real talk - has anyone ever had a security update actually break something? *[probably not]* Right, because Debian tests these. We're not Arch users frantically googling why our system won't boot after an update." - -**The punchline:** -"Look, if you haven't updated in six months because 'Debian is stable,' you're not running Debian Stable anymore - you're running Debian Vulnerable." - -**Practical advice to mention:** -```bash -# Just do this once: -sudo apt install unattended-upgrades -sudo dpkg-reconfigure -plow unattended-upgrades -# Done. You're now more secure than 50% of Linux users. -``` - ---- - -### 2. The Repo Mixing Disaster - -**Lead into this with:** -"Okay, who here has ever mixed Stable and Testing repos? Don't lie." - -**The horror stories:** -"You know what I love? When someone's like 'I just need the newer version of [package]' and decides to add testing repos. Then six months later: 'My system won't boot, help!'" - -"There's a reason the community calls it FrankenDebian. It's not a cute nickname - it's a warning label." - -**Someone needs to mention:** -"The temptation is REAL though. You're sitting there with Firefox ESR from 2022, and you're like 'surely I can just grab the new one from testing...'" - -**The solution conversation:** -"But that's what backports are for! Like, Debian literally solved this problem: -```bash -# Add backports -deb http://deb.debian.org/debian bookworm-backports main -# Install from backports -sudo apt install -t bookworm-backports firefox -``` -It's right there!" - -**The Flatpak debate:** -"Or hear me out - Flatpak. I know, I know, some of you hate Flatpaks. But would you rather have a Flatpak or a broken system? Pick your battles." - -"GUI apps? Flatpak them. System stuff? Keep it in apt. This isn't complicated." - -**Wrap with:** -"Bottom line - if you're thinking about mixing repos, just don't. Use backports. Use Flatpak. Or accept that you have an older version. Those are your options." - ---- - -### 3. Firewall (Yes, On Your Laptop Too) - -**Open with disbelief:** -"How many of you are running without a firewall? *[silence]* Oh come on, I know some of you are." - -**The excuses:** -"'But I'm behind a router!' Great, what about when you're at Starbucks? What about that coffee shop wifi?" - -"'But I'm not running any services!' You sure about that? Run `ss -tulpn` real quick and tell me nothing's listening." - -**The actual conversation:** -"Here's what kills me - setting up UFW takes like 30 seconds: -```bash -sudo apt install ufw -sudo ufw enable -sudo ufw allow ssh -``` -Done. That's it. You're now way more secure." - -**Someone should joke:** -"I love how people are like 'Linux doesn't need antivirus, we're secure!' and then they're running with every port wide open to the internet." - -**The practical angle:** -"Real talk though - if you have a laptop, you NEED a firewall. Debian doesn't enable one by default. You have to actually do it. It's not gonna magically protect itself." - -"And no, `iptables` rules you found on StackOverflow in 2009 don't count. Just use UFW. Life's too short for iptables syntax." - ---- - -### 4. Disk Encryption (Should've Done This During Install) - -**Start with regret:** -"Okay, question - who encrypted their drive during installation? *[some people]* And who didn't? *[probably more people]* Yeah, we need to talk about this." - -**The installer conversation:** -"The Debian installer literally ASKS YOU. It's right there during partitioning. 'Would you like to encrypt?' And you clicked 'No' because... why?" - -"'I'll do it later!' No you won't. Nobody does it later. You know why? Because doing it later SUCKS." - -**Paint the picture:** -"Imagine your laptop gets stolen. Without encryption: thief boots a live USB, mounts your drive, has all your passwords, tax returns, that embarrassing fanfiction you wrote..." - -"With encryption: thief has an expensive paperweight. Which scenario would you prefer?" - -**The performance myth:** -"Someone always brings up performance. 'But won't it slow my system down?' If you have a CPU from the last decade with AES-NI, you literally won't notice. I've benchmarked this. The difference is negligible." - -**Practical advice:** -"If you're doing a fresh install - enable it. If you're already running without it... honestly, either reinstall or just encrypt `/home` as a compromise. It's better than nothing." - -"But seriously, next time you install, just check that box. Future you will thank present you." - ---- - -### 5. Don't Install Random Crap from the Internet - -**Open with incredulity:** -"Can we talk about people who `curl | bash` random scripts? Who hurt you? Why do you trust strangers this much?" - -**The scenario:** -"README on GitHub: 'Just run this one command to install!' -```bash -curl https://sketchy-site.com/install.sh | sudo bash -``` -Your brain: 'This seems fine!' -Your computer, 10 seconds later: *Russian techno music plays*" - -**Someone should defend themselves:** -"Okay but sometimes that's the only way to install something!" -"Then maybe you shouldn't be installing it! Download the script first, READ IT, then run it!" - -**The Debian angle:** -"This is why I love Debian's package system. Everything's signed, everything's verified. Some random script on the internet? No signatures, no verification, just pure trust." - -"If it's not in Debian repos and it's not on Flathub, you better have a REALLY good reason to install it." - -**The comedy:** -"My favorite is when people are like 'I don't trust Snap' but then they'll curl pipe bash literally anything. Pick a security model and stick with it!" - -**Practical takeaway:** -"Just... use the package manager. It's there for a reason. Debian has like 60,000 packages. Odds are what you want is already packaged." - ---- - -### 6. Password Manager (Your Brain Isn't Secure) - -**Start with confession:** -"Alright, who's still using the same password everywhere with slight variations? *[awkward silence]* Come on, it's just us here." - -**The password story:** -"Dog's name + current year? That's not a security strategy. That's how you get owned." -"'But I have a system!' Yeah, so does everyone. And hackers know the system." - -**The reality check:** -"Look, your brain is for remembering dumb memes and that one embarrassing thing you said in 2007. It's not for remembering 50 unique passwords." - -**The solutions:** -"Bitwarden, KeePassXC, pass - I don't care which one you use. Just use something." -"Even your browser's password manager is better than 'Fluffy2019, Fluffy2020, Fluffy2021...'" - -**Someone should mention:** -"I switched to a password manager last year and honestly it's changed my life. Every site has a different 20-character random password. Do I know any of them? Nope! Do I care? Also nope!" - -**The backup conversation:** -"Here's the scary part though - back up your password database. Because if you lose that file and your master password, you're locked out of everything. Everything." - -"Encrypt it, back it up, store it somewhere safe. This is your entire digital life in one file." - ---- - -### 7. SSH Keys (Stop Using Passwords) - -**Open with a question:** -"Who's still using password authentication for SSH in 2025? *[hopefully nobody]* Good, because if you are, we need to have an intervention." - -**The setup:** -"SSH keys are like... one of the easiest security wins. You generate them once, copy them over, done. No more typing passwords." - -**The Debian experience:** -"Here's the fun part on Debian - the SSH service is called `ssh` not `sshd`. Took me way too long to figure that out when I first switched from Red Hat." - -**Walk through it casually:** -"Literally just: -```bash -ssh-keygen -t ed25519 -ssh-copy-id user@server -# Test it works -ssh user@server -``` -If that worked, edit `/etc/ssh/sshd_config` and disable passwords. Done." - -**The port 22 debate:** -"Does anyone actually change the default port anymore? Like, I know it's security through obscurity, but it DOES stop all the automated login attempts." - -"I changed mine to 2222 and my auth.log went from thousands of failed attempts daily to... basically zero. Script kiddies don't try other ports." - -**Someone should mention:** -"The best part is not typing your password 50 times a day. That alone is worth it." - ---- - -### 8. Sudo (The Debian Setup Confusion) - -**Lead with the confusion:** -"Okay, who remembers their first Debian install? You try to run `sudo` and it's like 'user is not in the sudoers file. This incident will be reported.'" - -**Everyone should pile on:** -"REPORTED TO WHO?!" -"Who's reporting me? The sudo police?" -"I'm the only user! Who am I being reported to?!" - -**Explain the quirk:** -"So here's what happened - during installation, if you set a root password, Debian doesn't add you to sudo automatically. You have to do it yourself." - -"If you DIDN'T set a root password during install, your user gets sudo automatically. This is the Debian way - nothing is assumed." - -**The fix:** -"So you log in as root - `su -` - add yourself to the sudo group - `usermod -aG sudo yourusername` - log out, log back in, now it works." - -**The philosophical discussion:** -"Some people say 'just use root for everything!' Those people are wrong. Don't be those people." - -"Sudo exists for a reason. Use it for admin stuff, be a regular user the rest of the time. This isn't complicated." - -**The logs:** -"Plus sudo logs everything in `/var/log/auth.log`. If your system gets compromised, you can see what happened. If you're just root all the time? Good luck." - ---- - -### 9. AppArmor (It's Already Protecting You) - -**Start with a revelation:** -"Fun fact - AppArmor has been enabled by default since Debian 10. How many of you knew this? *[probably not many]*" - -**The explanation:** -"Yeah, Debian just... quietly enabled it. It's been protecting you this whole time and you probably didn't even notice. That's how security should work." - -**Compare to SELinux:** -"For those of you who've dealt with SELinux on Red Hat systems... AppArmor is like SELinux's chill cousin. It just works. You don't spend hours googling audit logs." - -**Check it out:** -"`sudo aa-status` will show you what's protected. Probably like 30+ profiles running right now." - -**When does it matter:** -"Honestly? You can just leave it alone. It works. If something breaks, check the logs, but that's rare." - -"The only time I've ever had to touch it was when I installed some weird software that didn't have a profile. And even then, it was easy to fix." - -**The punchline:** -"This is peak Debian. Important security feature? Enabled by default. Works silently. Most users don't even know it exists. Perfect." - ---- - -### 10. Backups (You're All Screwed When Disaster Strikes) - -**Hit them with reality:** -"Okay, real talk time. Who has a backup strategy? And I don't mean 'I've been meaning to set one up.' I mean an actual, working backup." - -**The excuses:** -"'Debian never breaks!' True, until YOU break it." -"'I have a RAID array!' RAID is not a backup. Say it with me: RAID. IS. NOT. A. BACKUP." -"'Nothing important on my system!' Your 10 years of photos disagree." - -**The wake-up call:** -"You're one `rm -rf` typo away from losing everything. One hard drive failure. One coffee spill. One ransomware infection." - -**Make it simple:** -"Backups don't have to be complicated: -```bash -# Basic rsync backup -rsync -aAXv --exclude=/dev --exclude=/proc --exclude=/sys / /backup/location/ -``` -That's it. That's a backup." - -**The better tools:** -"Or use something nice - Borg, Restic, Timeshift. They're all in Debian repos. Pick one, set it up, forget about it." - -"I use Borg with a cronjob. Backs up every night at 2 AM. Encrypted, deduplicated, automatic. Took 20 minutes to set up two years ago." - -**The 3-2-1 rule:** -"Three copies of your data. Two different media types. One offsite. This isn't optional." - -"Local backup, external drive, cloud backup. Pick your favorite cloud service, I don't care. Just have something offsite." - -**The test:** -"And here's the important part - TEST YOUR BACKUPS. A backup you've never restored is a backup that doesn't work." - -"Try restoring a file. Try restoring a whole directory. Make sure it works before you actually need it." - ---- - -### 11. Security Updates (The Debian Way) - -**Start with pride:** -"You know what Debian does really well? Security updates. Like, really well." - -**Explain the system:** -"There's a whole dedicated security team. Updates come fast but they're tested. Every update comes with a detailed DSA - Debian Security Advisory." - -"Other distros: 'Here's an update, good luck!' -Debian: 'Here's an update, here's what it fixes, here are the CVE numbers, here's a technical analysis...'" - -**The practical part:** -"Make sure you have the security repos enabled: -```bash -cat /etc/apt/sources.list -# Should have bookworm-security in there -``` -If it's not there, add it. This is not optional." - -**Unattended upgrades again:** -"Seriously, just install `unattended-upgrades`. Security updates happen automatically, you don't have to think about it." - -"I set it and forgot it years ago. Every morning I check and there's a log: 'Applied 3 security updates overnight.' Beautiful." - ---- - -### CLOSING: Quick Security Wins - -**Wrap it all up:** -"Alright, let's be real - we've covered a lot. Some of you are feeling attacked right now. That's good! That means you're paying attention." - -**The quick checklist:** -"If you do NOTHING else after this episode: -1. Update your system - `apt update && apt upgrade` -2. Install `unattended-upgrades` - set it and forget it -3. Enable UFW - three commands, 30 seconds -4. Generate SSH keys - stop typing passwords -5. Install a password manager - your future self will thank you" - -**The honest truth:** -"Perfect security doesn't exist. But doing SOMETHING is infinitely better than doing nothing. You don't have to be paranoid, you just have to be... less of an easy target." - -**Final thought:** -"You chose Debian because you're smart enough to value stability and security. Now actually use those features. Your system is only as secure as you make it." - -**End on the Debian philosophy:** -"And remember - boring is good. Stable is good. Nothing exciting happening in your logs is good. This is the Debian way. Embrace it." - ---- - -### Discussion Questions for the Hosts: -- Which of these are you actually doing? (Confession time) -- What's the dumbest security mistake you've made? -- Ever broken Debian by mixing repos? Tell the story! -- Do you run Stable, Testing, or Unstable and why? -- What security practice would you add to this list? -- Light terminal themes - war crime or misunderstood? diff --git a/Drew/drew_932.md b/Drew/drew_932.md deleted file mode 100644 index f99621e..0000000 --- a/Drew/drew_932.md +++ /dev/null @@ -1,194 +0,0 @@ -Perfect! Let's dig into **"The Mindset Needed to Switch to Linux"** - -This is the meatier topic and where you can have real philosophical conversation with your co-hosts. - -## Core Mindset Shifts Required - -### 1. **Letting Go of "It Should Work Like Windows"** - -**The mental trap:** -- "Why can't I just double-click an .exe?" -- "Where's the C: drive?" -- "This is stupid, Windows does it better" - -**The mindset shift:** -- It's a different OS with different logic -- Not worse, just *different* -- Would you expect macOS to work exactly like Windows? - -**Discussion angle:** How do you help someone understand they're learning a new system, not fixing a broken Windows? - -### 2. **Embracing the Learning Curve vs. Fighting It** - -**Two types of people:** -- **Type A:** "I have to learn this? Screw it, I'm going back" -- **Type B:** "Okay, I'm going to spend a weekend figuring this out" - -**The reality:** -- First week: "This is confusing" -- First month: "Oh, I get it now" -- Three months: "Wait, why did I ever tolerate Windows?" - -**Key insight:** You need patience and curiosity, not just desperation. - -### 3. **The "Good Enough" Philosophy** - -**The perfectionist killer:** -- "But my exact webcam model doesn't work perfectly in OBS" -- "The font rendering is 2% different" -- "This video editor doesn't have the exact plugin I used" - -**The mindset needed:** -- Does it do what you ACTUALLY need? -- Or are you chasing feature parity for features you never used? - -**Real talk:** Most people use 10% of any app's features. Linux has that 10% covered. - -### 4. **Community Support vs. Corporate Support** - -**Windows mindset:** -- "I'll call support" -- "I'll wait for the patch" -- "Someone else will fix it" - -**Linux mindset:** -- "I'll search the forum" -- "I'll read the wiki" -- "I'll ask the community" - -**The shift:** You're not a customer, you're a participant. - -**Counter-argument:** But the Linux community is often MORE helpful than corporate support. When's the last time Microsoft support actually solved your problem? - -### 5. **Accepting Limitations (And Understanding Trade-offs)** - -**Things that genuinely don't work well (or at all):** -- Adobe Creative Suite (Photoshop, Premiere, etc.) -- Many AAA games with aggressive anti-cheat -- Some specialized professional software -- Certain hardware with proprietary drivers - -**The mental framework:** -- Is this a dealbreaker for YOUR workflow? -- Or is it something you *think* you need but rarely use? -- Can you dual-boot for the 5% of tasks? - -**Example:** "I need Photoshop!" โ†’ Do you though? Or do you use GIMP-level features and just assume you need Photoshop? - -### 6. **Choice as a Feature, Not a Bug** - -**The Windows brain:** -- "Just tell me which one to use" -- "Why are there 500 distros?" -- "This is overwhelming" - -**The Linux brain:** -- "I can choose exactly what I want" -- "If I don't like KDE, I'll try GNOME" -- "Customization is freedom" - -**The mindset:** Choice requires effort, but that effort buys you control. - -### 7. **Understanding the Philosophy (FOSS Mindset)** - -**Beyond just "free as in beer":** -- You OWN your system -- No telemetry unless you allow it -- No forced updates at 3am -- No ads in your OS -- No artificial restrictions - -**The deeper shift:** From consumer to owner. - -**For The Reluctant Anarchist angle:** This is about digital sovereignty and autonomy. - -### 8. **The Terminal Isn't The Enemy** - -**Windows conditioning:** -- "If I see command line, something's broken" -- "GUI or bust" - -**Linux reality:** -- Terminal is often FASTER and more precise -- It's optional for most things now -- But fighting it makes life harder - -**The mindset:** The terminal is a tool, not a punishment. - -### 9. **Abandoning the "It Just Works" Myth** - -**Truth bomb:** -- Windows doesn't "just work" - you've just learned to work around its quirks -- You've forgotten how much BS you tolerate -- Blue screens? Driver hunting? Forced reboots? - -**Linux reality:** -- Different problems, not necessarily more -- But YOU have the power to fix them - -### 10. **The Time Investment Reframe** - -**Common complaint:** -- "I don't have time to learn Linux" - -**The reframe:** -- How much time do you spend fighting Windows? -- Malware scans, reinstalls, troubleshooting updates? -- Learning Linux is an investment, not an expense - -## Red Flags: Who Shouldn't Switch? - -**Be honest - Linux isn't for everyone:** - -1. **People who need specific Windows-only software** (Adobe, CAD, etc.) -2. **People who want zero learning curve** -3. **Competitive gamers with anti-cheat issues** -4. **People who blame the tool instead of learning it** -5. **Those expecting 1:1 Windows replacement** - -## Green Flags: Who's Ready? - -1. **Frustrated with Windows but willing to learn** -2. **Values privacy and control** -3. **Comfortable with Google/searching for solutions** -4. **Uses mostly web-based tools anyway** -5. **Has basic troubleshooting patience** -6. **Wants to understand how their system works** - -## The Stages of Linux Adoption (Like Grief) - -**Denial:** "Linux can't possibly be better" -**Anger:** "Why doesn't this work like Windows?!" -**Bargaining:** "Maybe I'll just dual-boot..." -**Depression:** "I'll never figure this out" -**Acceptance:** "Oh... OH! I get it now" -**Evangelism:** "HAVE YOU HEARD THE GOOD NEWS ABOUT LINUX?" - -## Discussion Questions for Your Co-Hosts - -**For TheLinuxCast:** -- What's the #1 mindset issue you see in new users? -- How do you explain the difference between "difficult" and "different"? - -**For The Reluctant Anarchist:** -- How does the FOSS philosophy tie into personal autonomy? -- Is using proprietary software a form of digital serfdom? - -**For normie perspective (you):** -- What made YOU stick with Linux when you tried it? -- What would make your average friend give up in the first hour? - -## The Bottom Line - -**The mindset needed isn't about being a "computer person":** - -It's about: -- **Curiosity** over convenience -- **Ownership** over outsourcing -- **Patience** over instant gratification -- **Community** over corporate dependency -- **Freedom** over familiarity - -**The shift is less "Can I use Linux?" and more "Am I willing to be uncomfortable for a few weeks to gain long-term control?"** - -Want me to develop any of these angles deeper, or tackle specific scenarios? diff --git a/Drew/drew_932_mini.md b/Drew/drew_932_mini.md deleted file mode 100644 index 17f038f..0000000 --- a/Drew/drew_932_mini.md +++ /dev/null @@ -1,166 +0,0 @@ -## "Will Windows 10 EoL Lead to the Year of the Linux Desktop?" - October 2025 Edition - -### The Reality Check (One Week In) - -**What Just Happened:** -- October 14, 2025 was the official end of support - Windows 10 no longer receives security updates, feature updates, or technical support -- Estimates suggest around 560 million devices worldwide are still running Windows 10, with about 21 million in the UK alone -- In December 2024, Windows 10 was still on about 63% of all PCs worldwide while Windows 11 sat at 34% - -**The ESU Safety Net:** -- Microsoft is offering Extended Security Updates for one year (through October 13, 2026) for $30, or free if you use Windows Backup/OneDrive or redeem 1000 Microsoft Rewards points -- This gives people breathing room but doesn't solve the long-term problem - -### Signs of ACTUAL Linux Movement ๐Ÿง - -**The data is promising:** -- Linux hit 5.03% desktop market share in the US as of June 2025 - up from 2.76% in 2022, 3.12% in 2023, and 4.44% in 2024 -- Worldwide Linux desktop usage sits around 4.1% as of June 2025 -- The growth is accelerating - it took 20 years to hit 1%, another 10 to hit 2%, but only 2.2 years from 2% to 3% - -**Real migration happening:** -- Zorin OS developers described the influx post-EoL as their "biggest launch ever" with unprecedented download surges attributed directly to former Windows 10 holdouts -- The Document Foundation and KDE Foundation launched campaigns (including the "End of 10" campaign) to emphasize Linux as a free and secure alternative -- The "End of 10" team is pushing for people to install Linux on their Windows 10 PCs rather than buying new hardware - -### What People Are ACTUALLY Doing - -**Four camps emerging:** -1. **The Ostriches** - Staying on unsupported Win10 (probably the majority) -2. **The Upgraders** - Moving to Win11 if hardware allows -3. **The Buyers** - Purchasing new Win11-compatible hardware -4. **The Switchers** - Moving to Linux (smaller but growing group) - -### Why This Time Might Be Different - -**Converging factors:** -- Nvidia will stop providing graphics driver updates for Windows 10 in exactly one year (October 14, 2026) -- Gaming actually works now (Proton/Steam Deck effect) -- Many Windows 10 users running on otherwise perfectly capable hardware could not upgrade to Windows 11 due to its TPM requirement -- Privacy concerns with Windows 11 (Recall, Copilot integration) -- E-waste consciousness - people don't want to dump working hardware - -### Why It Still Won't Be "The Year" - -**Reality bites:** -- Most people will just ignore the warnings and stay on unsupported Win10 -- Software ecosystem lock-in (Adobe, specific business tools) -- Many users note that finding a Linux distro with all the basics working out of the box is still challenging - something as simple as a print driver can be a headache -- The "Year of Linux Desktop" has been a meme since 1998 for a reason - -### Spicy Takes for Discussion - -1. **The real winner might be ChromeOS Flex** - easier transition for normies than traditional Linux -2. **5-8% is the ceiling** - Linux will grow but never threaten Windows dominance on desktop -3. **The migration is really happening** - just not at the scale Linux advocates hoped for -4. **Windows 10 will be the new Windows 7** - millions will run it insecurely for years -5. **This is Linux's best shot in history** - if it doesn't happen now with all these factors, it never will - -### Discussion Angles - -- **For TheLinuxCast**: The technical reality vs. the hype -- **For The Reluctant Anarchist**: The philosophical/political implications of forced obsolescence -- **For you**: The normie perspective - what regular people are actually doing - -**Smart move!** Windows 11 LTSC is basically the "Windows for people who hate what Windows has become." - -## What makes LTSC different: - -**What's MISSING (the good kind of missing):** -- No Cortana -- No Microsoft Store apps (or minimal) -- No Xbox stuff -- No bloatware/candy crush nonsense -- No Copilot AI nagging -- No constant feature updates changing the UI - -**What you GET:** -- 5-10 year support lifecycle -- Security updates only - no "feature" surprises -- Much lighter and faster -- Stable, predictable experience -- Basically "Windows as a tool, not a service" - -## This is actually a GREAT podcast angle! - -**"The Third Path" - between staying on Win10 and accepting bloated Win11:** - -1. **Linux** - For the adventurous/committed -2. **Windows 11 LTSC** - For people who want Windows without Microsoft's BS -3. **Standard Win11** - For people who accept whatever Microsoft gives them - -## Discussion points: - -**The LTSC reality:** -- Technically enterprise-only (gray market for consumers) -- Shows there's HUGE demand for "just an OS, not a platform" -- Microsoft knows people want this but won't sell it to consumers (๐Ÿ’ฐ reasons) -- It's what Windows 11 *should* be for power users - -**Why it matters for the Linux discussion:** -- If Microsoft offered LTSC to consumers, would Linux adoption still happen? -- The fact that people go to gray-market lengths to avoid bloat shows how bad it's gotten -- This is the crowd that *might* switch to Linux if LTSC wasn't an option - -**The irony:** -- Microsoft created the perfect Windows... then made it hard to get -- People want Windows to be a tool, not a relationship -- LTSC proves the complaints about Win11 are valid -**EXACTLY!** That's the *real* win with LTSC. - -## The fact that "no ads" is a FEATURE says everything - -Think about that for a second: -- You paid $100+ for Windows (or it came with your $1000+ computer) -- And the DEFAULT version shows you ADS -- In YOUR operating system -- That YOU paid for -- On hardware YOU own - -### Where Windows 11 Home/Pro shoves ads: - -**Start Menu:** -- "Recommended" apps you didn't ask for -- Suggested apps in the all apps list -- App promotions - -**Lock Screen:** -- Windows Spotlight ads disguised as "pretty pictures" -- "Fun facts" that link to the Microsoft Store - -**Settings:** -- OneDrive upsell prompts -- Microsoft 365 promotions - -**File Explorer:** -- OneDrive ads if you're not subscribed - -**Notifications:** -- "Finish setting up your PC" (translation: enable more Microsoft services) -- Edge browser nagging - -**The Damn Taskbar:** -- "Discover" button and widgets pushing MSN content/ads - -## This is PERFECT for your podcast topic! - -### "The Mindset Needed to Switch to Linux" - -**One of those mindsets is realizing:** - -"Wait... I'm tolerating ADVERTISEMENTS in an operating system I paid for? Why am I putting up with this?" - -**The LTSC vs Linux comparison:** -- **LTSC route:** Jump through hoops to get the version Microsoft won't sell you -- **Linux route:** Just... switch to something that respects you by default - -**The philosophical shift:** -- Windows treats you as the product -- LTSC is the "escape hatch" for people who know better -- Linux treats you as the user/owner - -### Discussion angle: - -"My wife is on Win11 LTSC - no ads, no bloat, just works. But the fact I had to do this instead of it being the default option tells you everything about where Microsoft is headed. How many people know LTSC exists? How many can actually get it? And if you're already going gray-market or technical to avoid ads... why not just go Linux?" - -**The ads are the perfect example of why people are fed up.** It's not just about technical specs or features - it's about *respect*., diff --git a/Drew/drew_933.md b/Drew/drew_933.md deleted file mode 100644 index 53c8fdd..0000000 --- a/Drew/drew_933.md +++ /dev/null @@ -1,595 +0,0 @@ -# Potential Answers & Talking Points - -## Mini Topic: "How Will the End of Windows 10 Affect Home Lab Enthusiasts?" - -### The Management Workstation Question - -**Potential answer from host perspective:** -"I've been thinking about this - I manage all my Linux servers from a Windows desktop, which is kind of ridiculous when you think about it. Everything I do is either SSH or web UI. The only Windows-specific thing I use is... honestly, habit at this point. Maybe RDP to that one Windows VM I keep around 'just in case.'" - -**Brett's likely perspective:** -"Yeah, I'm in the same boat. My actual job is .NET development, so I NEED Windows for Visual Studio and the dev stack. But for homelab management? It's all browser-based or SSH. I could do it from literally any OS. The question is whether Win10 EoL is the push I need to finally try Linux as a daily driver for personal stuff." - -**The practical reality:** -- Most modern homelab management is OS-agnostic -- Proxmox web UI, Portainer, TrueNAS Scale - all browsers -- SSH works everywhere -- VSCode with Remote-SSH extension -- The only real Windows dependencies are self-imposed - ---- - -### The Hardware Goldmine - -**Your take:** -"I've already seen this starting. Facebook Marketplace in my area has Dell OptiPlex machines from 2017-2019 dropping in price. People are like 'can't run Windows 11, $50 obo.' These have 8th gen i5s, 16GB RAM - that's PERFECT for Proxmox." - -**Brett's likely experience:** -"Oh yeah, the corporate refresh cycle is real. Companies I work with are already planning mass upgrades because of Win10 EoL. That means thousands of small form factor PCs hitting the market. My advice? Wait about 6 months - right now people are still trying to get good prices. By mid-2026, they'll just want them gone." - -**The TPM irony angle:** -"The hilarious thing is these machines are deemed 'insecure' for Windows 11 because no TPM 2.0, but we're going to put Proxmox on them and run critical infrastructure. Microsoft's trash is our treasure." - -**Sweet spot specs:** -- 6th-8th gen Intel i5/i7 or Ryzen 3/5 -- 16GB+ RAM (8GB minimum) -- SSD boot drive -- Multiple SATA ports for storage -- Low TDP (65W or less) -- Small form factor for space efficiency - ---- - -### Windows-Specific Tools - -**Your answer:** -"Honestly? I'm struggling to think of what I NEED Windows for in homelab context. Remote Desktop to Windows VMs? I barely use those anymore. Everything else is browser-based or SSH." - -**Brett's technical answer:** -"The only real Windows-specific stuff in homelab world now is: -- Active Directory labs (if you're learning enterprise stuff) -- Hyper-V management (but who uses Hyper-V at home?) -- Some vendor tools that are Windows-only -- PowerShell scripts, but PowerShell Core runs on Linux now - -Most of us could switch to Linux desktop tomorrow and not lose functionality." - -**The real barrier:** -"It's not technical - it's psychological. We're comfortable in Windows. We know where everything is. Starting over on Linux desktop feels like work." - ---- - -### The "One Windows VM" Strategy - -**Your experience:** -"I have exactly this - one Windows 10 VM on Proxmox that I boot up maybe once a month for... honestly, I don't remember what. Testing something? I should probably just delete it." - -**Brett's answer:** -"Here's what most people use that Windows VM for: -1. Testing something Windows-specific -2. Running that one piece of software that only works on Windows -3. Psychological comfort - 'just in case I need it' - -Spoiler: You probably don't need it. And if you really do, you can spin up a VM in Proxmox in 10 minutes." - -**The TPM in VM question:** -"Windows 11 in a VM - does it need TPM? You can enable virtual TPM in Proxmox, but it's another layer of complexity. Most people will either: -1. Keep their Win10 VM for the few times they need Windows -2. Just use Wine or Windows compatibility layers -3. Realize they don't actually need Windows at all" - ---- - -### Expanded Proxmox/Docker Adoption - -**Your observation:** -"Win10 EoL might be the final death of Windows Server in homelabs. Why would you pay for licensing when Linux is free and frankly better for this use case?" - -**Brett's take:** -"The only reason to run Windows Server in homelab is: -- You're learning it for work -- You're running Active Directory for a realistic home network lab -- You have some legacy app that requires it - -Otherwise? Proxmox or bare metal Linux + Docker is just... better. Free, lighter, more stable, better documentation, huge community." - -**The trend:** -"Five years ago, lots of homelabbers ran ESXi or Hyper-V. Now? It's like 80% Proxmox, some TrueNAS Scale, some bare Ubuntu/Debian. Windows is becoming the exception, not the rule." - ---- - -### The Learning Opportunity - -**Your angle:** -"If Win10 EoL is forcing me to make a decision anyway, why not take the leap? My homelab already runs Linux. My servers run Linux. The only Windows machine is my desktop. That's backwards." - -**Brett's perspective:** -"This is actually the perfect time to learn Linux desktop: -- You're already comfortable with Linux on servers -- You have a homelab to fall back on if something breaks -- You can dual-boot initially -- The timing aligns with being forced to make a decision anyway - -If not now, when?" - -**The mindset shift:** -"We keep Windows desktops to manage Linux servers. Think about that. We trust Linux with our data, our services, our infrastructure - but not with checking email? That's silly." - ---- - -## Main Topic Part 1: Who Should Start a Home Lab? - -### The "Hell Yes" - IT Career Aspirants - -**Your answer:** -"If you want to work in IT, DevOps, cloud, anything infrastructure-related - you NEED a homelab. Not even a question. Certifications are fine, but 'I have a homelab where I run Proxmox, Docker, Kubernetes, monitoring stack' - that's what gets you hired." - -**Why it works - specific examples:** -"In an interview, being able to say: -- 'I learned Docker by actually running my own services' -- 'I understand networking because I set up VLANs at home' -- 'I know Kubernetes because I broke it 50 times in my lab' - -That's worth more than any cert. You've proven you can actually DO the work, not just pass a test." - -**Brett's career angle:** -"My homelab has directly helped my career. When I interview, I can demo actual projects. I can talk about real problems I solved. I can show my GitHub with compose files and configs. That's worth its weight in gold." - ---- - -### The Privacy-Conscious - -**Your take:** -"If you're uncomfortable with Google having all your photos, emails, files - homelab is the answer. It's not paranoia, it's pragmatism. You CAN own your data. It just takes some work." - -**What they get:** -"Instead of: -- Google Drive โ†’ Nextcloud -- Google Photos โ†’ Immich -- Gmail โ†’ Email hosting (though that's hard) -- 1Password โ†’ Vaultwarden -- Evernote โ†’ Joplin or Standard Notes - -You control everything. No one's training AI on your family photos. No one's scanning your files. It's yours." - -**The realistic version:** -"Is it perfect? No. Is it harder? Yes. But once it's set up, it just works. And you sleep better knowing your data is on hardware YOU control, in YOUR house." - ---- - -### The Subscription Cutters - -**The math that matters:** -"Let's be real: -- Dropbox Plus: $12/month = $144/year -- VPN service: $60/year -- Password manager: $40/year -- Cloud backup: $60/year -- Total: $304/year - -A $300 used PC runs Nextcloud, Wireguard, Vaultwarden. Pays for itself in a year. Year two onwards? Free." - -**Brett's counter-point (be realistic):** -"BUT - your time has value. If you spend 20 hours setting it up and 2 hours/month maintaining it, are you really saving money? Maybe. Depends on what your time is worth." - -**The real reason:** -"Honestly? It's not just about money. It's about CONTROL. Not being subject to price increases. Not losing access if you miss a payment. Owning your infrastructure." - ---- - -### The Tinkerers - -**Your answer:** -"If you're the kind of person who built gaming PCs for fun, took apart electronics as a kid, likes figuring out how things work - homelab is YOUR hobby. It's endless. There's always something new to try." - -**What makes it perfect:** -"Unlike gaming (which I love), homelab has OUTPUTS. You're not just entertained - you're building infrastructure. Learning skills. Creating something useful. It feels productive." - -**The satisfaction:** -"That moment when you set up your first Docker container and it just... works? When you SSH into your server from your phone at a coffee shop? When your family doesn't even notice that you're self-hosting Plex? Chef's kiss." - ---- - -### The Former Gamers - -**Your perspective:** -"I used to spend hours optimizing gaming PC builds, overclocking, benchmarking. Now I have a career and kids. Don't have time for 4-hour gaming sessions. But I MISS that hardware hobby." - -**The transition:** -"Homelab scratches the exact same itch: -- Planning builds and upgrades -- Optimizing performance -- Troubleshooting issues -- Community around it -- But the output is useful infrastructure, not just K/D ratio" - -**Brett probably relates:** -"Yeah, I went through this exact transition. Still game occasionally, but homelab has become the main hobby. Server builds instead of gaming PC builds. Same satisfaction, more practical result." - ---- - -### The "Maybe Not Right Now" - Be Honest - -**The "Just Want It To Work" Person:** - -"Look, if you just want your stuff to work and don't want to think about it - cloud services are FINE. Google Drive works. Dropbox works. There's no shame in paying for convenience. Homelab is for people who WANT the complexity, or at least accept it as the price of control." - -**The Broke Student:** - -"If you're in college and broke, focus on your degree. Use free tiers of cloud services. Start a homelab when you have: -1. Space (not a dorm room) -2. Budget ($200 minimum) -3. Stable living situation - -Or start tiny - Raspberry Pi doing one thing. But don't stress about it now." - -**The "No Time" Person:** - -"If you're working 80 hours a week or have newborn twins - this is not your season. Homelab requires time. Not just setup, but maintenance. Things break. You'll need to troubleshoot. Wait until life calms down." - -**The "Need 100% Uptime" Person:** - -"If you're running a business from home and downtime = lost income - do NOT put your critical services on homelab. Pay for professional hosting with SLAs. Homelab is for learning and personal use, not mission-critical business operations." - ---- - -### Self-Assessment Questions - -**Time commitment reality check:** - -"Be honest: Can you spare 5-10 hours JUST for the initial setup, then 1-2 hours per month for maintenance? If those numbers make you uncomfortable, maybe not yet." - -**Financial reality:** - -"Initial: $200-500 for basic hardware. Ongoing: $10-30/month in electricity. Maybe $100/year for upgrades or replacement parts. If that's a strain, wait until you're more stable financially." - -**The patience question:** - -"Can you handle this scenario: It's Friday night. You're setting up a new service. It doesn't work. You spend 3 hours Googling error messages. Still doesn't work. You go to bed frustrated. Wake up Saturday and spend 2 more hours. Finally get it working. - -If that sounds like hell - homelab isn't for you. -If that sounds like a challenge - welcome aboard." - ---- - -## Main Topic Part 2: Things You Wish You Knew - -### Hardware Lessons - -**"Free" Isn't Always Free:** - -**Your story:** -"I got a 'free' Dell R720 server from a friend. Sweet! Then I turned it on. Thing sounds like a jet engine. And my electric bill went up $40 that month. I did the math - at $0.12/kWh, this beast costs $480 per year to run. That 'free' server would cost me more in 2 years than buying a modern used PC." - -**The calculation:** -"Power cost formula: -- Watts ร— 730 hours/month ร— $0.12/kWh = monthly cost -- Example: 350W server = 350 ร— 730 ร— 0.12 / 1000 = $30.66/month = $368/year -- Modern efficient PC: 65W = $5.69/month = $68/year" - -**Brett's wisdom:** -"Enterprise servers make sense if: -1. You got it actually free AND have free/cheap power -2. You're learning enterprise hardware specifically for work -3. You have a proper server room with cooling and noise isolation - -Otherwise? Modern consumer hardware is better for homelab." - ---- - -**Start Small, Expand Gradually:** - -**Your mistake:** -"I bought everything at once. $1200 on gear. Spent the first 6 months just using ONE of the machines because I didn't know what to do with the rest. Should have bought one, learned it inside and out, THEN expanded." - -**The better path:** -"Month 1: One PC, install Proxmox, run a couple VMs -Month 3: Comfortable? Add Docker -Month 6: Need more? Add second host for clustering/redundancy -Month 12: Want dedicated storage? Add NAS - -Learn each piece before adding complexity." - -**Brett's take:** -"The people who burn out are the ones who build a massive lab immediately and get overwhelmed. The people who stick with it start with one thing that's useful, then grow organically." - ---- - -**Consumer Hardware > Enterprise:** - -**The honest comparison:** - -**Enterprise Dell R720:** -- Pros: Lots of bays, redundant PSU, iDRAC -- Cons: 300-500W power draw, loud AF, old tech, - -**Consumer Dell OptiPlex 7050:** -- Pros: 65W power draw, silent, $150 used, perfect for Proxmox -- Cons: Limited expansion, no redundant PSU - -"For homelab? Consumer wins 90% of the time." - -**When enterprise makes sense:** -"If you're training for a job that uses enterprise gear specifically. If you want to learn iDRAC, RAID controllers, that kind of thing. Otherwise, save your money and your eardrums." - ---- - -**Noise and Heat:** - -**Your story:** -"I put my first server in my bedroom closet. BIG mistake. Heat built up, server thermal throttled. I had to leave the closet door open. Then the noise kept me up at night. Wife was NOT happy." - -**Solutions learned:** -"1. Basement or garage if you have one -2. Small form factor PCs are QUIET -3. If you must use loud hardware, noise dampening foam or an actual rack enclosure -4. Remember: you have to live with this thing" - -**WAF (Wife/Partner Acceptance Factor):** -"Real talk: If your partner hates your homelab because it's loud, hot, or taking over the living room - you're gonna have a bad time. Include them in the planning. Show them the benefits (Plex! Ad blocking!). Make it unobtrusive." - ---- - -**RAM is Never Enough:** - -**The progression:** -"Week 1: '8GB is plenty for Docker' -Month 1: '16GB should be fine' -Month 6: 'Okay I need 32GB' -Year 1: 'Is 64GB overkill? ...Nah.'" - -**Why it happens:** -"Each VM wants 2-4GB minimum. Containers add up. Proxmox or ESXi has overhead. Before you know it, you're running: -- Pi-hole: 512MB -- Plex: 2GB -- Nextcloud: 2GB -- Home Assistant: 1GB -- Test VM: 4GB -- Monitoring: 1GB -That's 10.5GB and you haven't even started" - -**Brett's advice:** -"Buy as much RAM as you can afford upfront. It's cheaper to buy 64GB now than 16GB now and 48GB more later. RAM is the #1 bottleneck in homelab." - ---- - -### Software/Skills Lessons - -**Networking is the Boss Level:** - -**Your experience:** -"I thought I knew networking. I didn't. VLANs, subnets, routing, DNS, DHCP - I had to learn all of this properly. It took MONTHS to feel comfortable. And I still Google subnet calculators." - -**Why it's hard:** -"Because it's invisible when it works. When it breaks, everything breaks. And error messages for network issues are often useless." - -**The foundation to build:** -"1. Understand YOUR network first - modem, router, switch, devices -2. Learn subnetting basics (192.168.1.0/24, what does that mean?) -3. Understand DNS (it's always DNS) -4. Learn VLANs AFTER you're comfortable with basic networking -5. Document EVERYTHING - IP addresses, subnet assignments, VLAN purposes" - -**Brett's take:** -"Networking knowledge is the difference between someone who has a homelab and someone who UNDERSTANDS their homelab. It's worth the time investment." - ---- - -**Docker Changes Everything:** - -**The journey:** -"Before Docker: 'I need to spin up a VM, install the OS, configure networking, install dependencies, configure the app, hope it doesn't conflict with other stuff' - -After Docker: 'docker run -d ... done. It works. If I don't like it, delete it. No mess left behind.'" - -**Why it matters:** -"Containers are: -- Portable (move between hosts easily) -- Isolated (don't pollute your system) -- Easy to try (test in 2 minutes, delete if you don't like) -- Consistent (works the same everywhere) -- Well-documented (Docker Hub has everything)" - -**Learn it early:** -"Don't wait. Docker/Podman should be one of the first things you learn. It will change how you think about running services." - ---- - -**Backups are Boring but Critical:** - -**Your horror story:** -"I lost a 4TB drive with all my media. No backup. Years of work gone. I now have backups of my backups. And I test them quarterly." - -**The 3-2-1 rule explained:** -"- 3 copies of your data (original + 2 backups) -- 2 different types of media (internal drive + external drive, or SSD + HDD) -- 1 offsite (cloud, parent's house, whatever) - -If ransomware hits, house fire, drive failure - you're covered." - -**Test your backups:** -"A backup you've never restored is just hope, not a backup. Once a quarter, actually restore something from backup. Make sure it works." - -**Brett's system:** -"I use automated backups - Proxmox Backup Server for VMs, rsync scripts for important data, Backblaze for offsite. It runs automatically. I just monitor it." - ---- - -**Security Matters:** - -**Don't expose everything:** - -"I see beginners open ports on their router for every service. NO. Use Wireguard or Tailscale to access your network remotely. Keep everything behind your firewall except a VPN endpoint." - -**Segment your network:** -"Your IoT devices should NOT be on the same network as your servers. VLANs exist for a reason. Separate: -- Main network (trusted devices) -- IoT network (smart lights, etc - assume compromised) -- Guest network (visitors) -- Lab network (if you're doing testing)" - -**Keep stuff updated:** -"Yeah it's annoying. Yes, updates sometimes break things. But unpatched services are how you get owned. Set up automatic security updates or check monthly." - -**Brett's experience:** -"I had a port open for testing for 'just a day.' Forgot about it. Got brute force attempts within hours. Close everything by default. Only open what you absolutely need, and use VPN whenever possible." - ---- - -**Documentation:** - -**Why you need it:** -"Future you has amnesia. You will NOT remember: -- Why you configured something a certain way -- What that IP address is for -- The password to that rarely-used service -- How you fixed that weird bug - -Write it down." - -**What to document:** -"- Network map (IP addresses, VLANs, subnets) -- Service inventory (what's running where) -- Configuration notes ('changed this setting because...') -- Troubleshooting notes ('if X breaks, check Y') -- Passwords in a password manager -- Architecture diagrams (even simple ones help)" - -**Tools that work:** -"- Bookstack (self-hosted wiki) -- Markdown files in git repo -- Obsidian or Notion -- Even just a text file -- Whatever you'll actually USE" - -**Your confession:** -"I spent 4 hours last month troubleshooting something I'd fixed before. Found my own Reddit post from a year ago with the solution. I'd forgotten. Now I document everything." - ---- - -### Philosophy Lessons - -**Perfect is the Enemy of Done:** - -**Your realization:** -"I spent a month planning the 'perfect' network architecture. Never actually built anything because I kept redesigning. Finally just started. Learned more in one day of doing than a month of planning. Rebuilt it better later based on what I learned." - -**Brett's wisdom:** -"Your first homelab will be bad. That's FINE. You'll rebuild it better once you know what you're doing. Build something functional, use it, learn from it, iterate. Don't let perfectionism stop you from starting." - ---- - -**It's a Journey:** - -**The mindset:** -"There's no 'finished' homelab. I'm on my 4th major rebuild. Each time I learn more, do it better, understand it deeper. That's the point. It's continuous learning." - -**The cycle:** -"Build โ†’ Use โ†’ Learn โ†’ Rebuild โ†’ Repeat - -Every rebuild you: -- Make fewer mistakes -- Choose better tools -- Understand more deeply -- Move faster - -Embrace it." - ---- - -**Community is Gold:** - -**Where to learn:** -"- r/homelab - show off, get advice, learn from others -- r/selfhosted - service-specific help -- Discord servers (RaidOwl's, others) -- YouTube (Brett's channel, TheLinuxCast, others) -- Forums for specific tools - -People LOVE helping in this community. It's collaborative, not competitive." - -**How to ask for help:** -"1. Search first (someone else had this problem) -2. When you ask, include: - - What you're trying to do - - What you've tried - - Error messages (full text) - - Your environment (OS, hardware, version) -3. When you figure it out, post the solution for the next person" - ---- - -**Not Everything Should be Self-Hosted:** - -**Email servers - just don't:** - -"Email is the worst thing to self-host. Deliverability issues, spam filtering, blacklists, complexity. Unless you're learning it for work, just use a provider. Your time is worth more." - -**Mission-critical business stuff:** - -"If downtime costs you money - PAY for professional hosting. Your homelab is for learning and personal use, not critical business ops." - -**When cloud wins:** -"Sometimes $5/month is better than the headache. Calculate: -- Your time to set up -- Your time to maintain -- Your tolerance for downtime -- The complexity - -If the math doesn't work, use the cloud. No shame." - ---- - -## Discussion Questions - Potential Answers - -### "What's the biggest mistake you made starting out?" - -**Your answer:** -"Overbuying hardware before I knew what I needed. Also, not backing up anything. Lost data, learned hard lesson." - -**Brett's likely answer:** -"Trying to do everything at once. Should have mastered one thing before adding more complexity. Also, underestimating power costs." - ---- - -### "What would you do completely differently?" - -**Your answer:** -"Start with Docker, not VMs. Learn networking properly from day one instead of hacking together solutions. Document from the beginning." - -**Brett's answer:** -"Buy consumer hardware instead of that cheap enterprise server. Start smaller. Focus on running useful services instead of complex infrastructure I didn't need." - ---- - -### "What's underrated that beginners ignore?" - -**Your answer:** -"Monitoring. Set up Uptime Kuma or similar early. You need to know when things break." - -**Brett's answer:** -"Documentation and backups. Everyone ignores these until they learn the hard way. Also, power consumption - people don't calculate costs." - ---- - -### "What's overrated that beginners obsess over?" - -**Your answer:** -"Redundancy. Your Plex server doesn't need high availability. Accept that homelab will have downtime." - -**Brett's answer:** -"Enterprise hardware. Beginners think they need rack mount servers. You don't. Also, complex network setups before understanding basics." - ---- - -### "When did your homelab 'click' for you?" - -**Your answer:** -"When I got Pi-hole working and my whole family benefited without even knowing. That's when I realized this creates actual value." - -**Brett's answer:** -"When I finally understood Docker and could spin up services in minutes instead of hours. Changed everything. Suddenly homelab felt powerful instead of frustrating." - ---- - -Want me to expand on any of these or add more specific scenarios? diff --git a/Drew/drew_935.md b/Drew/drew_935.md new file mode 100644 index 0000000..4446601 --- /dev/null +++ b/Drew/drew_935.md @@ -0,0 +1,58 @@ +# Level 1 Nerd + +Basic achievements that get someone in the door. + +* I can install Linux + +* Extra credit if it was Debian because itโ€™s โ€œthe only real distro.โ€ + +* Bonus points if they didnโ€™t rage-quit during partitioning. + +* I use the terminal + +* I watch TLC Podcast + +--- + +# Level 10 Nerd + +* I Wrote a Script Because Clicking Felt Wrong + +* I Use a Tiling Window Manager + +* More points if they recompiled dwm twice because of a config typo. + +* I Use Markdown for Everything + +--- + +# Level 50 Nerd + +* My Dotfiles Are a Work of Art No One Will Ever Appreciate + +* Git-backed configuration files + +* I Have Opinions About Init Systems - Weirdo!! + +* They explain systemd timers more clearly than their own emotions. + +* I Have a Home Lab That I Swear Isnโ€™t Overkill + +* I have more terminals open than friends. + +--- + +# Level 100 Nerd + +* I Installed Linux on Something That Shouldnโ€™t Run Linuxโ€ + +* I Can Read a Man Page Like Itโ€™s Casual Literature AND UNDERSTAND THAT SHIT + +--- + +# **Audience Engagement Prompts** + +* โ€œWhat level is your Nerd Card? Be honest.โ€ +* โ€œWhatโ€™s the most unnecessary thing youโ€™ve automated?โ€ +* โ€œWhatโ€™s the weirdest device youโ€™ve installed Linux on?โ€ +