Loading video...

Video Failed to Load

Go Home

THIS WHOLE 3-NODE CLUSTER RUNS PROXMOX, CEPH AND KUBERNETES - ON 10 WATTS TOTAL. that clip is three zima boards wired to one little switch, and the power meter reads 10 watts for the entire thing. on those three tiny fanless boards: proxmox running a real cluster, three nodes...

RetroChainer's profile picture

RetroChainer

6,168 subscribers

42,348 views • 1 month ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

5 Comments

raj singh's profile picture
raj singh1 month ago

Move to talos thank me later

Dexigal's profile picture
Dexigal1 month ago

While some people are paying for VPS and server racks, someone has built a full-fledged datacenter on a shelf

Kai Lennox's profile picture
Kai Lennox1 month ago

The crazy part isn’t the size. It’s that the same concepts behind massive data centers can now run on a shelf

vesper's profile picture
vesper1 month ago

For what purpose do u need that?

tom vergara's profile picture
tom vergara1 month ago

みんなの今一番おすすめの映画やアニメは何ですか？教えて。結構大事なことだと思うんだ。 💬😎

Related Videos

YOU DON'T NEED A SERVER RACK. SIX USED MINI PCS AND A $60 CISCO SWITCH WIRE INTO A HOME CLUSTER ON YOUR DESK. that clip is six tiny mini-pcs stacked and patched into one cisco business 110 switch, red cables, a single power strip. each box is a full x86 computer, the kind offices dump by the pallet. used, they run $30 to $60 each. six of them plus the switch is a real cluster for a couple hundred dollars. what a stack like this runs: proxmox or kubernetes spread across all six nodes pi-hole, a nas, home assistant, docker services, each on its own node a local model or two on the boxes with enough ram the trick isn't raw power, it's separation. one node dies, the cluster keeps going. one service crashes, it doesn't drag the rest down. no server rack, no datacenter noise, no monthly cloud bill. the uncomfortable part isn't that it's cheap. it's that the "real infrastructure" you were told needs a rack and a budget fits on a desk and boots off a power strip. follow RetroChainer for more ways to build real infrastructure for pocket money, and bookmark this before the next office dumps its mini pcs.
0:22

YOU DON'T NEED A SERVER RACK. SIX USED MINI PCS AND A $60 CISCO SWITCH WIRE INTO A HOME CLUSTER ON YOUR DESK. that clip is six tiny mini-pcs stacked and patched into one cisco business 110 switch, red cables, a single power strip. each box is a full x86 computer, the kind offices dump by the pallet. used, they run $30 to $60 each. six of them plus the switch is a real cluster for a couple hundred dollars. what a stack like this runs: proxmox or kubernetes spread across all six nodes pi-hole, a nas, home assistant, docker services, each on its own node a local model or two on the boxes with enough ram the trick isn't raw power, it's separation. one node dies, the cluster keeps going. one service crashes, it doesn't drag the rest down. no server rack, no datacenter noise, no monthly cloud bill. the uncomfortable part isn't that it's cheap. it's that the "real infrastructure" you were told needs a rack and a budget fits on a desk and boots off a power strip. follow RetroChainer for more ways to build real infrastructure for pocket money, and bookmark this before the next office dumps its mini pcs.

RetroChainer

95,267 views • 1 month ago

THIS IS WHERE "THE CLOUD" ACTUALLY LIVES - A ROOM OF DELL STORAGE ARRAYS YOU RENT A SLIVER OF EVERY MONTH. that clip is a real datacenter aisle, rack after rack of dell powerstore arrays, every hexagon panel packed with drives. this is "the cloud." not a metaphor, this room, plus the power, cooling and staff keeping it alive. when you pay for cloud storage, you rent a few gigabytes of these arrays. forever. the bill grows with every photo. here's the part they'd rather you not connect. these enterprise drives run on a schedule. data centers swap them out long before they fail, by the pallet. those decommissioned drives get tested and resold as recertified, the same 20tb enterprise disk for a fraction of new. so the exact hardware humming in this room ends up in a nas on your desk, minus the monthly rent. no cloud subscription, no data on someone else's array, no bill that grows with your library. the uncomfortable part isn't that the cloud is huge. it's that "the cloud" was always just this room, and you can buy a piece of it once instead of renting it forever. follow RetroChainer for what the cloud doesn't want you to picture, and bookmark this before your next storage renewal.
1:10

THIS IS WHERE "THE CLOUD" ACTUALLY LIVES - A ROOM OF DELL STORAGE ARRAYS YOU RENT A SLIVER OF EVERY MONTH. that clip is a real datacenter aisle, rack after rack of dell powerstore arrays, every hexagon panel packed with drives. this is "the cloud." not a metaphor, this room, plus the power, cooling and staff keeping it alive. when you pay for cloud storage, you rent a few gigabytes of these arrays. forever. the bill grows with every photo. here's the part they'd rather you not connect. these enterprise drives run on a schedule. data centers swap them out long before they fail, by the pallet. those decommissioned drives get tested and resold as recertified, the same 20tb enterprise disk for a fraction of new. so the exact hardware humming in this room ends up in a nas on your desk, minus the monthly rent. no cloud subscription, no data on someone else's array, no bill that grows with your library. the uncomfortable part isn't that the cloud is huge. it's that "the cloud" was always just this room, and you can buy a piece of it once instead of renting it forever. follow RetroChainer for what the cloud doesn't want you to picture, and bookmark this before your next storage renewal.

RetroChainer

34,236 views • 1 month ago

100 MAC MINIS ON ONE METAL SHELF. IN THE CLOUD, EACH OF THOSE RENTS FOR $120 TO $500 A MONTH. that clip is a homemade rack: wire shelving packed with mac minis, each running macos, wired into one cluster. why macs and not a normal server? two reasons. you can only build, sign, and notarize ios and mac apps on apple hardware. cloud providers know it and charge for it. and apple silicon sips power and runs near-silent, so you can stack a lot of them on a shelf in a room, not a datacenter. the rent they're escaping: a single mac in the cloud runs ~$120 to $500 a month (macstadium up to aws) one engineer documented saving $4,000+ a month by self-hosting mac minis instead of cloud ci runners a used or new mini is a few hundred dollars once, then a few dollars of electricity what a shelf like this actually runs: ios and mac build farms, render jobs, app and device testing automation, and increasingly local ai inference. own the boxes, rent nothing. the uncomfortable part: the cloud was never the only option. it was the convenient one. the people who did the math bought the shelf. the honest caveat: it's real capex up front, real heat and power, and you become the sysadmin. no rented rack means no one to call at 3am. worth it at scale, overkill for one build a week. no rack rental, no per-hour metering, no fleet you don't own. save this before your cloud invoice renews again.
0:25

100 MAC MINIS ON ONE METAL SHELF. IN THE CLOUD, EACH OF THOSE RENTS FOR $120 TO $500 A MONTH. that clip is a homemade rack: wire shelving packed with mac minis, each running macos, wired into one cluster. why macs and not a normal server? two reasons. you can only build, sign, and notarize ios and mac apps on apple hardware. cloud providers know it and charge for it. and apple silicon sips power and runs near-silent, so you can stack a lot of them on a shelf in a room, not a datacenter. the rent they're escaping: a single mac in the cloud runs ~$120 to $500 a month (macstadium up to aws) one engineer documented saving $4,000+ a month by self-hosting mac minis instead of cloud ci runners a used or new mini is a few hundred dollars once, then a few dollars of electricity what a shelf like this actually runs: ios and mac build farms, render jobs, app and device testing automation, and increasingly local ai inference. own the boxes, rent nothing. the uncomfortable part: the cloud was never the only option. it was the convenient one. the people who did the math bought the shelf. the honest caveat: it's real capex up front, real heat and power, and you become the sysadmin. no rented rack means no one to call at 3am. worth it at scale, overkill for one build a week. no rack rental, no per-hour metering, no fleet you don't own. save this before your cloud invoice renews again.

RetroChainer

21,055 views • 2 months ago

BOLT A GPU ONTO THIS $200 FANLESS BOARD AND IT DOES THE TWO THINGS A RASPBERRY PI PHYSICALLY CAN'T: LOCAL AI AND 4K TRANSCODING. that clip is a zimaboard with a graphics card plugged straight into its pcie slot. that slot is the whole point. a pi has gpio and usb, but no real pcie, so it tops out where this one starts. drop a gpu in and the tiny box suddenly does: ollama and local models with actual gpu acceleration, not cpu crawl plex or jellyfin transcoding several 4k streams at once, in hardware anything else that was "you need a real pc for that", on a fanless board the rest of the board backs it up: quad-core intel up to 3.6, dual sata, dual 2.5gbe, runs zimaos, linux, even windows. so one silent box becomes a nas, a media server, and a local ai node at the same time. no tower, no raspberry-pi ceiling, no cloud gpu rented by the hour. the uncomfortable part isn't that it takes a gpu. it's that "a pi can do it" quietly stopped being true the moment the workload needed a real pcie lane. follow RetroChainer for the small boxes that punch way above their size, and bookmark this before you buy a whole tower for one gpu job.
0:21

BOLT A GPU ONTO THIS $200 FANLESS BOARD AND IT DOES THE TWO THINGS A RASPBERRY PI PHYSICALLY CAN'T: LOCAL AI AND 4K TRANSCODING. that clip is a zimaboard with a graphics card plugged straight into its pcie slot. that slot is the whole point. a pi has gpio and usb, but no real pcie, so it tops out where this one starts. drop a gpu in and the tiny box suddenly does: ollama and local models with actual gpu acceleration, not cpu crawl plex or jellyfin transcoding several 4k streams at once, in hardware anything else that was "you need a real pc for that", on a fanless board the rest of the board backs it up: quad-core intel up to 3.6, dual sata, dual 2.5gbe, runs zimaos, linux, even windows. so one silent box becomes a nas, a media server, and a local ai node at the same time. no tower, no raspberry-pi ceiling, no cloud gpu rented by the hour. the uncomfortable part isn't that it takes a gpu. it's that "a pi can do it" quietly stopped being true the moment the workload needed a real pcie lane. follow RetroChainer for the small boxes that punch way above their size, and bookmark this before you buy a whole tower for one gpu job.

RetroChainer

24,813 views • 1 month ago

YOUR HOMELAB IS USELESS IF YOU CAN'T REACH IT FROM ANYWHERE - AND YOU SHOULD NEVER OPEN A PORT TO DO IT. that clip is a homelab in a tiny rack: cheap used mini-pcs running a proxmox cluster with ollama for local ai. but the hardware isn't the hard part. reaching it safely when you're not home is. the wrong way: forward a port on your router. now your services face the whole internet, and every bot on earth starts knocking. the right way, and what he's running: a mesh vpn like twingate, netbird or tailscale. it builds a private encrypted network between your devices and the lab. no open ports, no public ip, nothing exposed. your phone in a cafe talks to your proxmox box at home like they're on the same wifi, and the internet sees nothing. that's the piece that turns a pile of mini-pcs into infrastructure you actually use. no port forwarding, no exposed dashboard, no public attack surface. the uncomfortable part isn't building the lab. it's that most people either can't reach it, or reach it by leaving the front door wide open. follow RetroChainer for the homelab step everyone skips, and bookmark this before you forward a single port.
0:59

YOUR HOMELAB IS USELESS IF YOU CAN'T REACH IT FROM ANYWHERE - AND YOU SHOULD NEVER OPEN A PORT TO DO IT. that clip is a homelab in a tiny rack: cheap used mini-pcs running a proxmox cluster with ollama for local ai. but the hardware isn't the hard part. reaching it safely when you're not home is. the wrong way: forward a port on your router. now your services face the whole internet, and every bot on earth starts knocking. the right way, and what he's running: a mesh vpn like twingate, netbird or tailscale. it builds a private encrypted network between your devices and the lab. no open ports, no public ip, nothing exposed. your phone in a cafe talks to your proxmox box at home like they're on the same wifi, and the internet sees nothing. that's the piece that turns a pile of mini-pcs into infrastructure you actually use. no port forwarding, no exposed dashboard, no public attack surface. the uncomfortable part isn't building the lab. it's that most people either can't reach it, or reach it by leaving the front door wide open. follow RetroChainer for the homelab step everyone skips, and bookmark this before you forward a single port.

RetroChainer

58,500 views • 1 month ago

AMD JUST KILLED THE $200 - A - MONTH AI SUBSCRIPTION - A 65-WATT BOX WITH 128GB OF UNIFIED MEMORY THAT RUNS 70B MODELS LOCALLY. that clip is amd's ryzen ai max+ 395 mini box, held up on stage. the whole pitch is one spec: 128gb of high-speed unified memory. why it matters: cpu, gpu and npu share the same 128gb pool, so a model that used to need a rack of vram just fits. what it actually runs: llama 70b in full precision on the built-in gpu open models up to ~100b parameters, locally, no cloud all of it in a mini pc pulling around 65 watts that's the part that ends the subscription: your prompts, your data, your model, on a box on your desk, not metered by the token. honest line: this runs open models, not gpt-5 or claude opus. for chat, coding help and agents on your own data it's more than enough. for the absolute frontier, the cloud still wins. and it isn't free: the box runs ~$1,500 and up. but that's a few months of a $200 sub, then it's yours forever. no monthly ai bill, no tokens metered, no prompt leaving the room. the uncomfortable part isn't that amd made a fast box. it's that "you need the cloud for ai" was a pricing choice, and unified memory just made it optional. follow RetroChainer for the hardware that turns rent into ownership, and bookmark this before your next ai renewal.
0:41

AMD JUST KILLED THE $200 - A - MONTH AI SUBSCRIPTION - A 65-WATT BOX WITH 128GB OF UNIFIED MEMORY THAT RUNS 70B MODELS LOCALLY. that clip is amd's ryzen ai max+ 395 mini box, held up on stage. the whole pitch is one spec: 128gb of high-speed unified memory. why it matters: cpu, gpu and npu share the same 128gb pool, so a model that used to need a rack of vram just fits. what it actually runs: llama 70b in full precision on the built-in gpu open models up to ~100b parameters, locally, no cloud all of it in a mini pc pulling around 65 watts that's the part that ends the subscription: your prompts, your data, your model, on a box on your desk, not metered by the token. honest line: this runs open models, not gpt-5 or claude opus. for chat, coding help and agents on your own data it's more than enough. for the absolute frontier, the cloud still wins. and it isn't free: the box runs ~$1,500 and up. but that's a few months of a $200 sub, then it's yours forever. no monthly ai bill, no tokens metered, no prompt leaving the room. the uncomfortable part isn't that amd made a fast box. it's that "you need the cloud for ai" was a pricing choice, and unified memory just made it optional. follow RetroChainer for the hardware that turns rent into ownership, and bookmark this before your next ai renewal.

RetroChainer

16,995 views • 1 month ago

A USED $700 RTX 3090 HAS MORE MEMORY AND FAR MORE SPEED THAN THE ~$1,000 A2 GOING INTO THIS SERVER. THE A2 STILL WINS - FOR ONE REASON THAT ISN'T PERFORMANCE. that clip is a dell poweredge r760 - a 2u rack server - getting an nvidia a2 dropped in through a riser. this is the enterprise route to local ai. the rung the desktop ladder skips entirely. the a2, verified: 16gb of memory, single-slot, low-profile, and just 40 to 60 watts it's an inference card, built to sit in a server that has no room or spare power for a real gpu so why not a 3090? a used rtx 3090 gives you 24gb and many times the compute for around $700. the a2 gives 16gb, much slower, for roughly a thousand. on raw local-llm value, the desktop card wins, and it isn't close. the a2's whole reason to exist is the thing you can't see on a spec sheet: it fits. a 2u server has no spare gpu power and no room for a triple-slot furnace. the a2 slips into one low-profile slot on 60 watts and lets an existing server do inference without a rebuild. the honest caveats: the r760 is not a desk machine. loaded, it idles at hundreds of watts, and its fans sound like a hair dryer that never turns off. it belongs in a rack or a closet 16gb is still 16gb. the same 7b-to-32b ceiling as the cheap cards. the enterprise badge doesn't buy you a bigger model what it does buy: ecc memory, redundant power, remote management, hot-swap everything. reliability, not speed so who this is for: someone who already runs a rack and wants to add private inference without touching the power or cooling budget. for anyone starting from a desk, the mac mini or the 3090 wins on every axis that matters. the real point: the "best" local ai box depends entirely on what you already own. on a desk, efficiency wins. in a rack, fit and reliability win. the a2 isn't a bad card - it's a card for a constraint the ladder never mentions. no fastest gpu here, no desk-friendly box, no bigger model than the cheap cards already run. save this before you buy enterprise gear for a desktop job.
0:28

A USED $700 RTX 3090 HAS MORE MEMORY AND FAR MORE SPEED THAN THE ~$1,000 A2 GOING INTO THIS SERVER. THE A2 STILL WINS - FOR ONE REASON THAT ISN'T PERFORMANCE. that clip is a dell poweredge r760 - a 2u rack server - getting an nvidia a2 dropped in through a riser. this is the enterprise route to local ai. the rung the desktop ladder skips entirely. the a2, verified: 16gb of memory, single-slot, low-profile, and just 40 to 60 watts it's an inference card, built to sit in a server that has no room or spare power for a real gpu so why not a 3090? a used rtx 3090 gives you 24gb and many times the compute for around $700. the a2 gives 16gb, much slower, for roughly a thousand. on raw local-llm value, the desktop card wins, and it isn't close. the a2's whole reason to exist is the thing you can't see on a spec sheet: it fits. a 2u server has no spare gpu power and no room for a triple-slot furnace. the a2 slips into one low-profile slot on 60 watts and lets an existing server do inference without a rebuild. the honest caveats: the r760 is not a desk machine. loaded, it idles at hundreds of watts, and its fans sound like a hair dryer that never turns off. it belongs in a rack or a closet 16gb is still 16gb. the same 7b-to-32b ceiling as the cheap cards. the enterprise badge doesn't buy you a bigger model what it does buy: ecc memory, redundant power, remote management, hot-swap everything. reliability, not speed so who this is for: someone who already runs a rack and wants to add private inference without touching the power or cooling budget. for anyone starting from a desk, the mac mini or the 3090 wins on every axis that matters. the real point: the "best" local ai box depends entirely on what you already own. on a desk, efficiency wins. in a rack, fit and reliability win. the a2 isn't a bad card - it's a card for a constraint the ladder never mentions. no fastest gpu here, no desk-friendly box, no bigger model than the cheap cards already run. save this before you buy enterprise gear for a desktop job.

Grimmer

24,287 views • 2 months ago

THE $4,000 DGX SPARK BENCHMARKS AT 342 T/S ON PROMPT PROCESSING - THEN DROPS TO 73 WHEN IT ACTUALLY GENERATES. that clip is a dgx spark running llama-bench on qwen3-coder 30b, side by side with a mac. two numbers decide everything here: pp512, prompt processing = 342 tokens/sec tg128, token generation = 73 tokens/sec that gap is the whole lesson. local ai isn't one speed, it's two. prompt processing is reading your input: your files, your long context. the spark is compute-heavy, so it eats that fast. token generation is writing the answer, and it's bound by memory bandwidth, where the spark is modest and unified-memory macs stay close. so "which box is faster" has no single winner. feeding huge context or running agents that read a lot? prompt processing wins, the spark shines. long chat replies, one token at a time? generation matters more, and a mac holds its own. no single benchmark number, no universal "fastest box", no upgrade that wins every workload. the uncomfortable part isn't that the spark is fast. it's that "tokens per second" was always two numbers, and the hype only ever quotes the flattering one. follow RetroChainer for the benchmark truth nobody screenshots, and bookmark this before you buy on one number.
1:14

THE $4,000 DGX SPARK BENCHMARKS AT 342 T/S ON PROMPT PROCESSING - THEN DROPS TO 73 WHEN IT ACTUALLY GENERATES. that clip is a dgx spark running llama-bench on qwen3-coder 30b, side by side with a mac. two numbers decide everything here: pp512, prompt processing = 342 tokens/sec tg128, token generation = 73 tokens/sec that gap is the whole lesson. local ai isn't one speed, it's two. prompt processing is reading your input: your files, your long context. the spark is compute-heavy, so it eats that fast. token generation is writing the answer, and it's bound by memory bandwidth, where the spark is modest and unified-memory macs stay close. so "which box is faster" has no single winner. feeding huge context or running agents that read a lot? prompt processing wins, the spark shines. long chat replies, one token at a time? generation matters more, and a mac holds its own. no single benchmark number, no universal "fastest box", no upgrade that wins every workload. the uncomfortable part isn't that the spark is fast. it's that "tokens per second" was always two numbers, and the hype only ever quotes the flattering one. follow RetroChainer for the benchmark truth nobody screenshots, and bookmark this before you buy on one number.

RetroChainer

42,451 views • 1 month ago

EVERYONE'S BUYING THE M4 MAC MINI AS A CHEAP DESKTOP. HERE'S WHY IT ENDS UP UNUSED. the pitch is irresistible: a tiny mac that runs cool, quiet, and cheap. then the receipt shows up. the mac mini ships with no screen, no keyboard, no mouse. add a monitor, a decent keyboard and mouse, and more storage, and the "$799 mac" is past $1,000 fast. and macos isn't windows. if your world is gaming, specific windows apps, or the setup you already know, the mini fights you the whole way. that's how so many end up back on a pc, the mini in a drawer. so what is the mac mini actually great at? not being your main desktop. it's the box you never look at. headless in a corner, it's a near-silent always-on server: run local ai models on it, host your automations, keep your files, and reach it from the laptop you already use. it earns its keep by disappearing. the honest turn: the mac mini isn't a cheap desktop. it's a cheap server pretending to be one. buy it for the job it's quietly brilliant at, not the one the ads imply. want a main computer? price the whole setup first. want a silent little box that runs ai and never bothers you? this is the one. no monitor in the box, no keyboard, no "just $599". save this before you buy the sticker price instead of the real one.
0:34

EVERYONE'S BUYING THE M4 MAC MINI AS A CHEAP DESKTOP. HERE'S WHY IT ENDS UP UNUSED. the pitch is irresistible: a tiny mac that runs cool, quiet, and cheap. then the receipt shows up. the mac mini ships with no screen, no keyboard, no mouse. add a monitor, a decent keyboard and mouse, and more storage, and the "$799 mac" is past $1,000 fast. and macos isn't windows. if your world is gaming, specific windows apps, or the setup you already know, the mini fights you the whole way. that's how so many end up back on a pc, the mini in a drawer. so what is the mac mini actually great at? not being your main desktop. it's the box you never look at. headless in a corner, it's a near-silent always-on server: run local ai models on it, host your automations, keep your files, and reach it from the laptop you already use. it earns its keep by disappearing. the honest turn: the mac mini isn't a cheap desktop. it's a cheap server pretending to be one. buy it for the job it's quietly brilliant at, not the one the ads imply. want a main computer? price the whole setup first. want a silent little box that runs ai and never bothers you? this is the one. no monitor in the box, no keyboard, no "just $599". save this before you buy the sticker price instead of the real one.

RetroChainer

14,184 views • 2 months ago

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.
1:25

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.

RetroChainer

13,775 views • 1 month ago

THIS $1,300 CARD HAS THE SAME 32GB OF VRAM AS A $2,000+ RTX 5090 - FOR LOCAL AI, THAT'S THE SPEC THAT DECIDES EVERYTHING. that clip is the gigabyte radeon ai pro r9700 ai top, 32gb of vram, built for local ai. the pitch is simple: the same memory capacity as an rtx 5090, for roughly a third of what a 5090 actually sells for. here's why that matters, and where it doesn't. for ai, vram is the gate. a model either fits in memory or it doesn't. 32gb loads models a 16gb card can't touch, full stop. so for running local llms and image models, this card does the one thing that counts, cheap. honest line: this is not a 5090 for gaming. the 5090 is far faster at raster and ray tracing. they only match on how much vram they carry. if you want frames, buy the 5090. if you want to fit big models locally, you just found the same 32gb for a third of the money. no $2,000+ price tag, no cloud gpu rental, no model too big for 16gb. the uncomfortable part isn't that amd is cheaper. it's that for local ai you were about to overpay for gaming power you'd never use. follow RetroChainer for more on paying for the spec that matters, and bookmark this before your next gpu.
1:52

THIS $1,300 CARD HAS THE SAME 32GB OF VRAM AS A $2,000+ RTX 5090 - FOR LOCAL AI, THAT'S THE SPEC THAT DECIDES EVERYTHING. that clip is the gigabyte radeon ai pro r9700 ai top, 32gb of vram, built for local ai. the pitch is simple: the same memory capacity as an rtx 5090, for roughly a third of what a 5090 actually sells for. here's why that matters, and where it doesn't. for ai, vram is the gate. a model either fits in memory or it doesn't. 32gb loads models a 16gb card can't touch, full stop. so for running local llms and image models, this card does the one thing that counts, cheap. honest line: this is not a 5090 for gaming. the 5090 is far faster at raster and ray tracing. they only match on how much vram they carry. if you want frames, buy the 5090. if you want to fit big models locally, you just found the same 32gb for a third of the money. no $2,000+ price tag, no cloud gpu rental, no model too big for 16gb. the uncomfortable part isn't that amd is cheaper. it's that for local ai you were about to overpay for gaming power you'd never use. follow RetroChainer for more on paying for the spec that matters, and bookmark this before your next gpu.

RetroChainer

38,844 views • 1 month ago

Someone built Kubernetes that runs entirely in your browser. This might be the easiest way to learn Kubernetes. - No Docker. - No Minikube. - No Kind. - No EKS. - No installation. Just open a webpage and start exploring Pods, Deployments, ReplicaSets, Nodes, scheduling, networking, and more. The engineering behind it is incredible. Kubernetes is written in Go, but instead of compiling it to the browser, the developer rewrote major Kubernetes components in TypeScript so they could run natively inside the browser. This is one of the best examples of using AI I've seen. AI helped port thousands of lines of Kubernetes code, while the developer manually reviewed everything and validated it with extensive tests to make sure it behaves like a real cluster. ⚠️ It's not for running production workloads. It's built for learning, teaching, experimenting, and preparing for DevOps interviews. Imagine onboarding new engineers or teaching Kubernetes without asking everyone to spend an hour installing Docker, configuring Minikube, or creating an EKS cluster. I genuinely think projects like this will change how we learn infrastructure. Interactive labs > Static documentation. Blog Post:
0:42

Someone built Kubernetes that runs entirely in your browser. This might be the easiest way to learn Kubernetes. - No Docker. - No Minikube. - No Kind. - No EKS. - No installation. Just open a webpage and start exploring Pods, Deployments, ReplicaSets, Nodes, scheduling, networking, and more. The engineering behind it is incredible. Kubernetes is written in Go, but instead of compiling it to the browser, the developer rewrote major Kubernetes components in TypeScript so they could run natively inside the browser. This is one of the best examples of using AI I've seen. AI helped port thousands of lines of Kubernetes code, while the developer manually reviewed everything and validated it with extensive tests to make sure it behaves like a real cluster. ⚠️ It's not for running production workloads. It's built for learning, teaching, experimenting, and preparing for DevOps interviews. Imagine onboarding new engineers or teaching Kubernetes without asking everyone to spend an hour installing Docker, configuring Minikube, or creating an EKS cluster. I genuinely think projects like this will change how we learn infrastructure. Interactive labs > Static documentation. Blog Post:

Nandkishor

91,578 views • 2 months ago

She makes $1,000s on Etsy from thrift-store junk she never even buys. She doesn't buy the item. She photographs it. A weird vintage bust, a gas mask, something nobody else is selling she snaps it on the shelf and walks out. AI turns the photo into a 3D model. The printer runs overnight. The listing is up by morning. She never learned to 3D model. The AI did that part. The edge isn't the printer. Everyone has a printer. The edge is that thrift stores are full of one-of-one shapes nobody has digitized yet and she's the one photographing them. The whole supply chain: a phone, a $200 printer, and a shelf she doesn't pay for.
0:25

She makes $1,000s on Etsy from thrift-store junk she never even buys. She doesn't buy the item. She photographs it. A weird vintage bust, a gas mask, something nobody else is selling she snaps it on the shelf and walks out. AI turns the photo into a 3D model. The printer runs overnight. The listing is up by morning. She never learned to 3D model. The AI did that part. The edge isn't the printer. Everyone has a printer. The edge is that thrift stores are full of one-of-one shapes nobody has digitized yet and she's the one photographing them. The whole supply chain: a phone, a $200 printer, and a shelf she doesn't pay for.

RetroChainer

422,930 views • 3 months ago

Elon Musk explains the “series of miracles” xAI had to achieve to bring one gigawatt of power online for its supercomputer cluster in Memphis The xAI team coordinated dozens of gas turbines, faced permit challenges in Tennessee, and ultimately moved the power generation just across the border into Mississippi. From there, they had to run high-voltage transmission lines and build an entire power plant on the Mississippi side and it was very difficult to build that But the deeper point is even more important Most people calculate AI power needs by looking only at the GPUs. That is a serious mistake. A real data center also requires substantial power for networking, CPUs, storage, and most critically cooling In Memphis, where summer temperatures are extreme, peak cooling demand can add roughly 40% more power. On top of that, operators must maintain extra capacity so generators can be taken offline for servicing without shutting down the entire system. This redundancy typically adds another 20 to 25 percent When all of these factors are included, Elon stated that approximately 110,000 GB300 GPUs require roughly 330 megawatts of actual power generation This is why building and powering frontier AI data centers is far more difficult and far more capital intensive than it appears from the outside
2:43

Elon Musk explains the “series of miracles” xAI had to achieve to bring one gigawatt of power online for its supercomputer cluster in Memphis The xAI team coordinated dozens of gas turbines, faced permit challenges in Tennessee, and ultimately moved the power generation just across the border into Mississippi. From there, they had to run high-voltage transmission lines and build an entire power plant on the Mississippi side and it was very difficult to build that But the deeper point is even more important Most people calculate AI power needs by looking only at the GPUs. That is a serious mistake. A real data center also requires substantial power for networking, CPUs, storage, and most critically cooling In Memphis, where summer temperatures are extreme, peak cooling demand can add roughly 40% more power. On top of that, operators must maintain extra capacity so generators can be taken offline for servicing without shutting down the entire system. This redundancy typically adds another 20 to 25 percent When all of these factors are included, Elon stated that approximately 110,000 GB300 GPUs require roughly 330 megawatts of actual power generation This is why building and powering frontier AI data centers is far more difficult and far more capital intensive than it appears from the outside

X Freeze

140,377 views • 4 months ago

A 27 YEAR OLD BANGALORE DEV BOUGHT A DECOMMISSIONED BANK SERVER RACK FOR $3,200 AT AUCTION AND NOW PULLS $24,000 A MONTH FINE TUNING LLMs FOR US SAAS COMPANIES raj is 27, bangalore, one bedroom flat with a ceiling fan, won the lot off a state bank IT refresh in march, four 2U storage shelves with 96TB of enterprise SAS drives and a managed switch added two custom towers with RTX 3090s under the desk, runs llama 3.3 70B and fine tunes indic and english variants for 11 US saas clients on hugging face pause at 0:30 on the finger pointing at the yellow drive caddies, that is gear that sold new for $180,000 $24,000 in, $61 in karnataka power, the auction lot paid itself back in 4 days, no claude bill no rate limits, nothing leaves the flat the window is open, follow and bookmark before it closes
1:00

A 27 YEAR OLD BANGALORE DEV BOUGHT A DECOMMISSIONED BANK SERVER RACK FOR $3,200 AT AUCTION AND NOW PULLS $24,000 A MONTH FINE TUNING LLMs FOR US SAAS COMPANIES raj is 27, bangalore, one bedroom flat with a ceiling fan, won the lot off a state bank IT refresh in march, four 2U storage shelves with 96TB of enterprise SAS drives and a managed switch added two custom towers with RTX 3090s under the desk, runs llama 3.3 70B and fine tunes indic and english variants for 11 US saas clients on hugging face pause at 0:30 on the finger pointing at the yellow drive caddies, that is gear that sold new for $180,000 $24,000 in, $61 in karnataka power, the auction lot paid itself back in 4 days, no claude bill no rate limits, nothing leaves the flat the window is open, follow and bookmark before it closes

Flandermaxx

1,191,544 views • 3 months ago

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.
0:41

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.

cvxv666

103,734 views • 2 months ago

THIS FRENCH GUY RUNS OPENCLAW AND HERMES AI AGENTS ON A HOMELAB THAT REPLACED GOOGLE DRIVE AND ICLOUD ENTIRELY ON JUST 10 WATTS The project: host his own local AI agents, OpenClaw and Hermes, ditch cloud storage subscriptions entirely by running his own NAS, and use the whole build to prep for his K8s certification – all running on 4 Raspberry Pis. Today's upgrade: a PoE module. One Ethernet cable now does two jobs – powers the Raspberry Pi AND gives it network access at the same time. No separate power adapters, no cable clutter, no juggling connections during maintenance. Total power draw for all 4 Raspberry Pis combined: max 10 watts. He's not renting cloud storage anymore. He's not paying monthly subscriptions for space he already owns the hardware for. His files, his AI agents, his data – all sitting on hardware in his own home, on a fraction of the power a lightbulb uses. Next up: blocking ads network-wide across his entire home, using one of the automation services running on the same setup. This is what "own your data" actually looks like when someone builds it instead of just talking about it. Bookmark this post. Full build in the video below.
0:45

THIS FRENCH GUY RUNS OPENCLAW AND HERMES AI AGENTS ON A HOMELAB THAT REPLACED GOOGLE DRIVE AND ICLOUD ENTIRELY ON JUST 10 WATTS The project: host his own local AI agents, OpenClaw and Hermes, ditch cloud storage subscriptions entirely by running his own NAS, and use the whole build to prep for his K8s certification – all running on 4 Raspberry Pis. Today's upgrade: a PoE module. One Ethernet cable now does two jobs – powers the Raspberry Pi AND gives it network access at the same time. No separate power adapters, no cable clutter, no juggling connections during maintenance. Total power draw for all 4 Raspberry Pis combined: max 10 watts. He's not renting cloud storage anymore. He's not paying monthly subscriptions for space he already owns the hardware for. His files, his AI agents, his data – all sitting on hardware in his own home, on a fraction of the power a lightbulb uses. Next up: blocking ads network-wide across his entire home, using one of the automation services running on the same setup. This is what "own your data" actually looks like when someone builds it instead of just talking about it. Bookmark this post. Full build in the video below.

SCOTTY BEAM

18,175 views • 2 months ago

made a big breakthrough on tinynodes! this is a huge .blend file with 679 nodes, running 100% in the browser... and it's fully dynamic! at the end of the video, you can see the raw geometry and the node graph that describes how to turn it into this complex wooden structure
0:24

made a big breakthrough on tinynodes! this is a huge .blend file with 679 nodes, running 100% in the browser... and it's fully dynamic! at the end of the video, you can see the raw geometry and the node graph that describes how to turn it into this complex wooden structure

Seth Thompson

36,436 views • 4 months ago

watch the small one on the left. it hears something at 00:05 and does nothing clever with it it just passes it on that is the whole trick. echo isolates a trace in ambient noise. moth follows the noise. kite finds a shorter route to it. vex starts collecting fragments. halo keeps the pattern so nobody has to look for it twice. nobody assigned any of that coherence in the top corner opens the cycle at 18%. by the time the wave crosses the field it is past 75%, and not one instruction was typed while it happened most people building agent teams do this backwards. they write a dispatcher, a queue, a state machine, and then wonder why five bots are slower than one. five bots stay slower than one until they can read each other's job descriptions and hand work sideways with no human standing in the middle three ways this breaks before it works: → give every bot the same description and the orchestrator has nothing to route on. every task comes straight back to you → let two bots own the same folder and they overwrite each other for six hours. you wake up to a clean, empty, perfectly synced nothing → skip the boundary line in one charter and that bot will send something. once is plenty to learn that lesson twenty agents run on one seat here. cheaper than a standup for three humans, and none of them ask what the priority is most setups have one agent and a bottleneck made of a person. this one has twenty, and the interesting part happens while nobody is watching full charters, the routing rule and the one line that stops a bot mid-send are in the piece below
0:30

watch the small one on the left. it hears something at 00:05 and does nothing clever with it it just passes it on that is the whole trick. echo isolates a trace in ambient noise. moth follows the noise. kite finds a shorter route to it. vex starts collecting fragments. halo keeps the pattern so nobody has to look for it twice. nobody assigned any of that coherence in the top corner opens the cycle at 18%. by the time the wave crosses the field it is past 75%, and not one instruction was typed while it happened most people building agent teams do this backwards. they write a dispatcher, a queue, a state machine, and then wonder why five bots are slower than one. five bots stay slower than one until they can read each other's job descriptions and hand work sideways with no human standing in the middle three ways this breaks before it works: → give every bot the same description and the orchestrator has nothing to route on. every task comes straight back to you → let two bots own the same folder and they overwrite each other for six hours. you wake up to a clean, empty, perfectly synced nothing → skip the boundary line in one charter and that bot will send something. once is plenty to learn that lesson twenty agents run on one seat here. cheaper than a standup for three humans, and none of them ask what the priority is most setups have one agent and a bottleneck made of a person. this one has twenty, and the interesting part happens while nobody is watching full charters, the routing rule and the one line that stops a bot mid-send are in the piece below

monokern

12,490 views • 9 days ago

THIS CHINESE DEVELOPER'S OBSIDIAN BRAIN MAPS EVERY CLIENT CONVERSATION - ZERO EMPLOYEES, $40,000/MONTH, CATCHES PROBLEMS BEFORE CLIENTS DO every node on screen is a conversation - green for happy clients, yellow for neutral, red for problems that need attention - the brain sees the emotional state of the entire business in real time this is not a CRM, not a dashboard, not a spreadsheet - it's a living map of every client interaction that fires connections and surfaces patterns no human account manager would ever catch when a cluster starts turning yellow the brain flags it before the client sends the complaint - when a green cluster grows it identifies what's working and replicates it across every other account automatically he replaced a $15,000/month account management team with one Obsidian brain that never sleeps, never misses a message and never needs a performance review no employees, no contractors, no standups, no payroll - just one developer, one brain and one delivery system doing the work of 10 people $40,000/month - solo - from a system that gets smarter every single conversation
0:29

THIS CHINESE DEVELOPER'S OBSIDIAN BRAIN MAPS EVERY CLIENT CONVERSATION - ZERO EMPLOYEES, $40,000/MONTH, CATCHES PROBLEMS BEFORE CLIENTS DO every node on screen is a conversation - green for happy clients, yellow for neutral, red for problems that need attention - the brain sees the emotional state of the entire business in real time this is not a CRM, not a dashboard, not a spreadsheet - it's a living map of every client interaction that fires connections and surfaces patterns no human account manager would ever catch when a cluster starts turning yellow the brain flags it before the client sends the complaint - when a green cluster grows it identifies what's working and replicates it across every other account automatically he replaced a $15,000/month account management team with one Obsidian brain that never sleeps, never misses a message and never needs a performance review no employees, no contractors, no standups, no payroll - just one developer, one brain and one delivery system doing the work of 10 people $40,000/month - solo - from a system that gets smarter every single conversation

Noisy

42,207 views • 3 months ago