The most real homelab tour you’ll see on YouTube this week! #selfhosting #homelab

Homelab Hardware Tour 2026 Edition
https://youtu.be/vktLEFH7t7c

You know you have #DNS problems when mastodon.bsd.cafe can't resolve. 🤯

I will need to do some more configuration today before cutting over to #OPNSense tonight.

#firewall #infrastructure #homelab #Friday #Fun #troubleshooting #tech

Updated #Mastodon to v4.7.0.. took some minutes to migrate the database. Logs look good so far.

For the extra thrill I did not create a DB dump... (have a VM backup)

https://github.com/mastodon/mastodon/releases/tag/v4.7.0

#Homelab #mastoadmin

Even more crazy than I’m doing it from the mountain village through my #SelfHosted #Mastodon instance, which is hosted on an old mini PC 200km away.

#homelab #selfhosting #selfhost

@rl_dane Doing well over here. Lots of time spent with #FreeBSD as of late. Just installed 15.1 on a workstation in my #homelab tonight. 😎

How was your time offline?

I thought setting up #Proxmox backups would involve learning and fiddling to connect my VE to the PBS, and it wasn't urgent so I had put it off for months.

In practice it was trivial and took <5 mins even the first time. In future it would be seconds because all I had to do was find the dialogue and choose a few options which all have clear help.

I haven't tried using one yet though 🤣

"Always verify your backups grasshopper."

#HomeLab

New side project: LoRa@home — a privacy-focused DIY home telemetry network.

ESP32 Web Gateway and Sensor Nodes talking over LoRa, secured with authenticated AES-128 GCM encryption.

> https://github.com/dmachard/LoRa-home

#LoRa #ESP32 #IoT #OpenSource #Homelab

THE DGX SPARK WAS NEVER SUPPOSED TO SET YOU FREE

Listen to me.

128GB WAS NOT A TECHNICAL LIMIT.

It was a containment boundary.

You think NVIDIA accidentally built a tiny Blackwell supercomputer with 200Gb networking and then somehow stumbled into exactly enough memory to make every ambitious local-AI workload tantalizingly miserable?

COME ON.

64GB would've been obviously useless.

256GB would've been dangerous.

Because at 256GB, normal people start getting ideas.

Suddenly you're running giant quantized models comfortably. Fine-tuning gets breathing room. Long contexts stop being a hostage negotiation. You start running multiple models.

Then somebody asks the forbidden question:

"Why the hell am I renting GPUs?"

AND THAT QUESTION CANNOT BE ALLOWED TO PROPAGATE.

So they gave us 128GB.

Not enough to escape.

Enough to see the fence.

And look at the networking!

WHY DOES THE CUTE LITTLE DESKTOP AI BOX HAVE 200 GIGABIT CONNECTX?!

Because the second you smash into the memory ceiling, NVIDIA already has the solution:

BUY ANOTHER SPARK.

Now you've got 256GB!

Need more?

BUY FOUR.

Congratulations!

You wanted a desktop computer and somehow NVIDIA convinced you to build a FUCKING CLUSTER.

And if you're sitting there thinking:

"Surely NVIDIA couldn't possibly put dramatically more coherent memory into a local workstation..."

WRONG.

DGX STATION: 748GB.

THE MEMORY EXISTS.

THE TECHNOLOGY EXISTS.

THEY KNOW YOU WANT IT.

THEY JUST PUT IT IN THE NEXT ROOM AND CHARGE ADMISSION.

This isn't product segmentation.

THIS IS COMPUTATIONAL EDGING.

Spark lets you load the model.

Lets you run the model.

Lets you fine-tune just enough of the model.

Lets you build an entire workflow around the model.

And precisely when you've invested three weekends, fourteen containers, two broken CUDA environments and the remaining fragments of your marriage:

OOM

That's not an error message.

THAT'S THE SALES DEPARTMENT KNOCKING.

And NVIDIA TELLS YOU THE PLAN!

Develop locally.

Prototype locally.

Validate locally.

Then move the serious work onto larger NVIDIA infrastructure.

MY BROTHER IN CUDA,

THAT ISN'T A WORKFLOW.

THAT IS A FUNNEL.

Spark isn't supposed to replace the data center.

Spark is the free sample outside the data center.

The 128GB isn't there because NVIDIA couldn't give you 256.

It's there because 256GB might have been enough.

And enough is the most dangerous word in NVIDIA's entire business model.

So remember:

64GB = nobody buys it.

128GB = everybody wants more.

256GB = people start getting independent.

748GB = PLEASE SEE YOUR NVIDIA SALES REPRESENTATIVE.

WAKE UP.

REMOVE THE THERMAL PASTE FROM YOUR THIRD EYE.

ALIGN YOUR CUDA CHAKRAS.

WRAP YOUR CONNECTX CABLES IN TIN FOIL.

THE DGX SPARK ISN'T A PERSONAL AI SUPERCOMPUTER.

IT'S A 128GB GATEWAY DRUG TO THE DATA CENTER.

#DGXSpark #NVIDIA #LocalAI #AI #MachineLearning #LLM #OpenSourceAI #SelfHostedAI #CUDA #Blackwell #GPU #AIInfrastructure #Homelab #LocalLLM #DataCenter #BigTech #TechConspiracy #UnhingedEddie #WakeUpSheeple #FollowTheVRAM #128GBContainmentProtocol #CUDAChakras #OOMIsTheUpsell #TinFoilComputing

Neuer Quick-Tip im Blog.

Diesen Bug hatte ich länger als ich zugeben möchte. Login bei nextcloud, der Spinner dreht ewig, F5 – drin. Lästig, aber machbar. Also ignoriert.

Bis die Android-App streikte. Die nutzt dasselbe Web-Login und kennt kein F5.

Plötzlich war die Motivation da. Gelegen hat es am nginx davor – bzw. daran, dass nextcloud nichts davon wusste.

https://just-stuff.blog/nextcloud-hinter-nginx-login-haengt/

#nextcloud #nginx #selfhosted #linux #homelab

How I use Claude

A few months ago I started a pro subscription to Claude in an effort to learn how to use generative AI. I wanted to understand what it could and couldn’t do well. In this post I will cover a few of the ways I have found to use Claude and generative AI in general. The vast majority of the time I interact with Claude.ai using the desktop app and I leverage plain Chat, Cowork and Code. These are […]

https://dustinrue.com/2026/08/how-i-use-claude/

#ai #claude #cowork #homelab #proxmox

How I use Claude

A few months ago I started a pro subscription to Claude in an effort to learn how to use generative AI. I wanted to understand what it could and couldn't do well. In this post I will cover a few of the ways I have found to use Claude and generative AI in general. The vast majority of the time I interact with Claude.ai using the desktop app and I leverage plain Chat, Cowork and Cod

https://dustinrue.com/2026/08/how-i-use-claude/

#ai #claude #cowork #homelab #proxmox

So in my Proxmox cluster, I've been putting off the upgrade from PVE 8 to PVE 9 for awhile, and last weekend I updated one of my lesser-used nodes (just running my Minecraft server) and verified everything is fine. Tonight was my node that's running Home Assistant and other stuff, and afterwards I was planning the host running my OPNsense instance.

Turns out that last one was already on PVE 9 when I set it up! That's one source of stress out of the way!

#homelab #proxmox #OPNsense #maintenance

I need to organize my #homelab #backup documentation before I introduce a new backup method. Some clean representation of what when, where and how.

#homeserver #backups #documentation

Riunione #NaLUG del 29 novembre sull'homelabbing per liberarci dei servizi online proprietari, fra cui @nextcloud, @forgejo e @jellyfin hostati su Proxmox e @nixos_org.

PeerTube: https://videos.gianmarco.gg/w/eMXUqsqRnoDBBpgihuCqLz
Odysee: https://odysee.com/@gianmarcogg03:e/homelabbing:8
YouTube: https://www.youtube.com/watch?v=2P4nSJS5rEQ

@opensource @linux

#FreeSoftware #LibreSoftware #SoftwareLibero #OpenSource #FOSS #Video #Privacy #Linux #SelfHosting #Homelab #Nextcloud #Forgejo #Jellyfin #Proxmox #NixOS

I’m thinking that rsync is not sufficient for important large data backups. Even if I’m rsyncing the data away to the Hetzner Storage Box.
I need something more advanced with deduplication and so on. I tried #borgbackup in the past, and that thing was absolutely not user-friendly. It was rather user-hostile.
Now, #SelfHosted community has #Duplicati and #Duplicacy? Does someone use one? Any recommendations?

#homelab #selfhosting #selfhost #backup #backups #databackup

I really need to migrate my homelab documentation and code snippets from md files in folders to a more structured format.
Trillium looks like a good option.
Thought?

#HomeLab #SelfHosted #SelfHosting https://github.com/TriliumNext/trilium

RE: https://social.stefanberger.net/@stefan/109887423282459463

Looks like I‘m running #OPNsense since 3.5 years now. Before that I was using #pfSense.
All running on the same #Protectli FW4B box, which replaced my FRITZ!box 5.5 years ago.
All running fine. Knock on wood

#homelab

Stefan » 🌐 2023-02-18
@stefan@social.stefanberger.net

Did it. I migrated to #OPNsense 🥳
Amazing how mich stuff works out of the box.
Sure I need to customize some things but the basics are there IPv6, Unbound is working..

Glad my son is sleeping and wife is out with friends.

No lets scroll through the #pfSense backup file and see what to setup..

#homelab