I Don't Want to Build This at Home. I Already Have.
I went into a small computer shop for a Wi-Fi adapter.
Seventeen euros.
Simple mission.
Naturally, I also bought a router.
Not because I had planned to buy a router.
Because I looked at the one on the shelf, looked at the price, thought about the Netgear Nighthawk R7000 I had at home, and went:
Fuck it.
The Nighthawk is about ten years old.
It has a US power adapter.
Which means every time I move the fucking thing around Europe I also get to carry a giant conversion brick like some archaeological artifact from RadioShack.
It had DD-WRT on it.
It served me well.
It is also a dead man walking.
For about forty-four euros, retirement paperwork was filed immediately.
The funny part was trying to explain what I actually wanted from the replacement.
Does It Have VPN?
I asked the guy about VPN support.
Encrypted DNS.
Security.
That kind of thing.
He started looking things up.
I remember thinking:
Buddy, you're not going to find what I'm asking for on the product page.
Because I was not really asking:
Does the box have a checkbox labeled VPN?
Most routers have some kind of VPN story.
Server.
Client.
Passthrough.
Marketing copy.
Whatever.
And asking whether a router "has DNS" is almost meaningless.
Of course it fucking has DNS.
The interesting question is what I can control.
Can I point it where I want?
Can I use encrypted upstreams?
Can I override defaults?
Can I make the router participate in the topology I actually want instead of whatever topology the firmware designer assumed a normal household has?
That was the question.
I am not sure that was the question he heard.
The Clue Was the Sentence
At some point I said something like:
I don't want to build this at home. I already have.
That was the clue.
I was not asking whether encrypted DNS exists.
I know it exists.
I was not asking whether I can run a VPN.
I know I can run a VPN.
I was asking whether this appliance could do enough of the shit I already know how to assemble manually that I would not have to assemble it manually again.
That is a very different shopping question.
It is the difference between:
What features does this router advertise?
and:
How much of my existing network architecture can this little plastic box absorb before I have to start building around it?
Eventually I simplified the protocol.
I looked at the routers.
Looked at the numbers.
Looked at the prices.
And basically said:
This is the most expensive one you have. I'll take that one.
Excellent engineering process.
Very rigorous.
The Supported Path
This reminded me of buying a little Mac mini.
Cheap little machine.
Around eighty euros.
The seller told me what version of macOS it had.
Monterey.
Then explained that was basically the highest supported version.
I told him not to worry about it.
I'll put whatever version of macOS I want on that.
Again, not because support does not matter.
Support matters.
But support is one boundary.
Capability is another.
A seller sees:
Highest supported operating system: Monterey.
I see:
Hardware. Boot process. Patches. Loaders. Drivers. What can actually run?
Same machine.
Different question.
Feature Checkbox Versus Architecture
This happens constantly in technology.
A box says:
- VPN;
- security;
- DNS;
- cloud;
- AI;
- whatever the current magic word is.
Normal buyer asks:
Does it have the feature?
I ask:
What the fuck do you mean by "has"?
VPN server?
VPN client?
WireGuard?
OpenVPN?
Policy routing?
Whole network?
One device?
Can I route only certain traffic?
Does the firmware fight me?
Can I bypass the firmware entirely?
Suddenly the checkbox has turned into twelve questions.
This is why shopping for technical shit gets weird.
The retail vocabulary is optimized for people deciding whether a feature exists.
My vocabulary starts after existence has already been established.
Why I Was in That Shop
As I was leaving, I tried to explain something else.
I said I would rather give him my money than give it to big businesses.
At first he seemed to hear that as criticism of business in general and started explaining something about big companies.
No.
Wrong direction.
I tried again.
I'm here because I'd rather support a small business.
Then it clicked.
"Oh. Yeah. Thank you."
I did not need the thanks.
That was not why I said it.
I was telling him why I was standing in his store.
I could order hardware online.
I could go to a chain.
I could probably spend twenty minutes comparing thirty routers and optimize the purchase within an inch of its life.
I did not want to.
I wanted the adapter.
I saw the router.
The old Nighthawk was already on borrowed time.
The guy had a small shop.
He had something good enough sitting on a shelf for forty-four euros.
Done.
Money transferred.
Small business supported.
Ancient router sentenced to death.
The Technomancer Shopping Protocol
This is apparently how I buy technology now.
Step one:
Enter store for one specific thing.
Step two:
Notice another piece of hardware solving a problem I had mentally classified as "eventually."
Step three:
Ask questions several abstraction layers below the product sheet.
Step four:
Realize the conversation has become incompatible.
Step five:
Buy the best box in the store.
Step six:
Go home and find out what it can actually do.
Because ultimately that is the part I care about.
Not what the sticker says.
Not what operating system the seller says is the highest.
Not whether the box technically "supports VPN."
I want to know where the real boundary is.
And ideally, for once, I would like that boundary to be far enough away that I do not have to build the whole fucking thing myself.
Again.