Why Cordukes.ca exists now.

A notebook for problems worth remembering.

Cordukes.ca collects practical notes about home servers, media playback, storage and networking. Much of the useful material begins with something behaving badly, because perfectly working equipment rarely produces an interesting article.

I am a home user learning this as I go. I am not a network engineer or a professional reviewer. The setup grew over time, often one problem at a time, and the learning path has been long, complicated and occasionally expensive.

It began with a simple household goal: make media convenient to watch. That suggested somewhere to keep files and a way to play them on the devices people already owned. Putting the files on separate storage made the network part of the storage system. Adding more services made it worth thinking about isolation, backups and recovery. Each choice solved a problem while creating a few new relationships.

The goal is not to cover every product release or publish on a schedule. Some articles describe a result from my own setup; others explain a common technical pattern and say plainly when the scenario is illustrative. I will not invent a test just to make a lesson sound more dramatic.

Competent does not mean clairvoyant.

I can learn a system, read documentation and work through a problem without pretending I knew the answer before the problem began. A large part of this project has involved discovering which question I should have asked earlier.

Some fixes came from careful testing. Some arrived after I had already changed three unrelated settings and needed to return to a known baseline. A few involved buying faster equipment and eventually deciding that the previous, slower arrangement was better because it remained connected to the network. The lessons are more useful when the wrong turns remain visible.

This site therefore uses ordinary statements such as “I misunderstood this,” “that test did not prove what I thought it proved” and “I would not buy this again.” Expertise that cannot survive those sentences is mostly decorative.

Specific experience, carefully generalized.

Some articles are records of what I tried and what happened in my own setup. Other articles are explainers: they work through a possible failure or a sensible test without claiming I personally experienced every step. Neither kind is a universal instruction, and both should change when better evidence arrives.

A useful note explains the original goal, the symptoms, the misleading clues, the tests, the result and the limits of that result. “I changed a setting and it worked” leaves out the part another reader actually needs: why that setting was relevant and what else might produce the same symptom.

The writing gives enough context to explain a decision but does not provide private operational details. General descriptions of a NAS, a router and a playback device are enough to follow the reasoning; exact account, network and access settings are not needed.

Technical terms are used when the exact name helps someone find a setting or understand a feature. Otherwise, ordinary language wins. The equipment is already complicated enough without the writing applying for a promotion.

Ownership and research are labelled differently.

If I use something, I say so. If I have only researched it, I say that instead. Reading specifications is useful, but it is not the same as living with a product through updates, failures and the moment it becomes responsible for the household internet.

Problems and caveats remain in the write-up even when they make an expensive purchase look less impressive. The sunk cost has already received the money; it does not also get editorial control.

There are currently no paid placements or affiliate links. If that changes, the commercial relationship will be identified where the recommendation appears. A recommendation must remain useful if the reader never clicks a commercial link.

The site is allowed to learn too.

Technical systems change. Software updates alter behaviour, hardware fails in new ways and a conclusion that matched one set of evidence may need to be narrowed later.

When a meaningful correction is needed, I intend to change the article and note the update rather than quietly preserving a confident mistake for historical ambience. The update log records substantial editorial or structural changes, not every comma moved half an inch to the left.

No comments, accounts or support desk.

The site does not accept public submissions, troubleshooting requests or invitations to debate router brands at length. Readers are welcome to use the notes. Nobody is required to become a customer.

There is no posting quota, engagement strategy or attempt to turn every routine update into an urgent opinion. The site can remain quiet until another problem produces a story worth keeping.

This is also not a complete diagram of the private network. Readers receive the context needed to understand the lesson, not addresses, account details, precise routes or a treasure map labelled “valuable services this way.”