In the last post I handed an eighty-year-old man a tablet holding his life’s work — every recorded teaching, transcribed and searchable, in a box he could hold. It was, I thought, a finished gift.

It wasn’t, quite. And the reason taught me something about what “giving” really means.

The tablet was in his hands. But the web address his teachings lived at was registered to me. The account that kept the whole thing reachable from the internet was mine. So in a quiet, hidden way, it was still my server — just sitting in his living room. A gift isn’t really given until it’s owned, and to finish, two hidden things had to change hands.

Why Ownership Wasn’t Optional

Think about what a legacy is for. It has to outlast you. That’s the whole idea.

Now imagine I’d left it half done: his tablet, his teachings — but reachable only through a web address in my name and an account I controlled. What happens the day I forget to renew that domain? Or the day I’m no longer around to manage the account? His legacy goes dark, killed by a missed renewal or a password no one else has. A legacy that depends on me being around forever isn’t really a legacy. It’s a loan.

For this to be his — to survive without me — the setup had to be his too. Not just the device, but the address and the account. Everything in the chain, in his name.

The Two Things We Had to Transfer

There were exactly two hidden pieces still tied to me. Let me explain each in plain terms, because most people have never had to think about them.

1. The domain — his address on the internet. A domain is just a name people type to reach something, like the name on a mailbox. His teachings needed to live at his mailbox, not mine. The good news, and a theme I keep coming back to: a domain costs about $10 a year. That’s the whole price of owning your own permanent corner of the internet.

2. Cloudflare and the tunnel — the secure path to his tablet. Here’s the part that makes this possible from a home at all. A service called Cloudflare Tunnel lets a device tucked away in a living room be reached safely from anywhere, with proper HTTPS, without a static IP address and without opening any ports on the router. (It deserves a full post of its own, and it’s getting one later. Here I’ll just say it’s what connects his little tablet to his domain, safely.)

For both of these to be his, they couldn’t live in my account. They had to be set up under his own.

How We Did It: Side by Side

I didn’t do this remotely and hand him a finished result. I sat down next to him, and we did it together, logged in as him.

We made his own Cloudflare account. We bought his domain right there, and set up the tunnel connecting his tablet to that domain — all under his login, with me guiding and him clicking.

I made one choice on purpose: I didn’t try to explain the tunnel. To an eighty-year-old who’d never thought about DNS or ports, “secure tunnel to your device” is just noise, and understanding the plumbing was never the point. The point was that the account was his, the domain was his, and the path was his. So we set it up together, his name on everything, and left the mechanics for another day. Ownership doesn’t require understanding every pipe. It requires the pipes being in your name.

“What’s a Domain?”

To understand the next moment, you have to understand where he was starting from. He genuinely did not know what a domain was. When I said we needed to buy one, he asked me — plainly, with no embarrassment at all — “What’s a domain?”

So I explained it the simplest way I could think of. “You know how you type www.naver.com to get to Naver?” — Naver being Korea’s biggest web portal, the page half the country opens first thing every morning. “That address — www.naver.com — that’s a domain. We’re going to get one of those for you, just for your teachings.”

“Ah,” he said. “I see.”

That was the whole of his technical briefing. He didn’t need to understand the mechanics. He needed to understand that it was going to be his.

The Moment He Pulled Out His Credit Card

And that’s what makes what happened next land the way it does. I’d expected to quietly pay the $10 myself. It’s nothing, and he’s eighty, and he’d just learned what a domain was thirty seconds earlier. I assumed I’d handle the boring money part.

I was wrong. When we reached the moment to buy the domain, he reached for his wallet, took out his credit card, and bought his own .com — ten dollars, one year — himself.

I can’t fully explain why that small thing moved me as much as it did. An eighty-year-old man, who I’d half expected to be passive about all this, paying for his own corner of the internet with his own hand. It wasn’t about the ten dollars. It was him saying, without saying it: yes. This is mine.

That’s the moment the gift was actually given. Not when I handed him the tablet — when he paid for the domain.

What He Owns Now

So here’s where it stands. His life’s teaching is served at his web address, through his Cloudflare account, from his tablet, in his home. Nothing of mine is anywhere in that chain. If I disappeared tomorrow, it would keep running.

And it stays private and his — password-protected, under his control, holding his own recordings. I didn’t put a man’s teachings out into the world. I gave one man full ownership of his own legacy, down to the last hidden piece.

That, I’ve come to think, is what self-hosting is really about. Not just running your own software, but owning the whole stack — down to the name and the path. For most projects that’s a nice idea. For a legacy meant to outlast its owner, it’s the part that matters.

Where This Goes Next

I thought that was the end of the story. The gift given, the ownership moved, the legacy complete.

Then, at that very handover, he mentioned something — recordings my wife and I didn’t have. Teachings missing from the library. And so the tablet came back to my desk, where it sits right now, for one more round: finding what was missing, adding it, and returning it complete.

That’s the final post in this series — Version 2.0 — and it’s a fitting end, because it’s the whole idea of this blog in miniature: software that’s never quite finished, because we keep using it and improving it.

If you’ve followed this series to here, thank you. Please subscribe for the last chapter.

Key Takeaways

  • A gift built on setup you control isn’t fully given — it’s on loan until ownership moves.
  • A legacy has to outlast its maker, so it can’t depend on your account or your renewals staying alive.
  • Two hidden pieces had to become his: the domain (his address, about $10/year) and the Cloudflare account + tunnel (the secure path to his device).
  • Set it up together, under his login — ownership doesn’t require understanding every pipe, just having them in your name.
  • Self-hosting, at its core, isn’t just running your own software; it’s owning the whole stack, down to the name and the path.