What This Thing Actually Is
Tip For Mechanical Keyboard Weekly is a recurring newsletter and community roundup that collects practical advice on switches, keycaps, lubing, building, firmware tweaks, and the occasional hotmouse topic. It ships once a week, usually with three to five distinct tips ranging from beginner-level cleaning routines to stuff that only matters if you are already deep into modding. The format has stayed basically the same for years, which means the signal quality is decent but the novelty has worn off. I subscribed about two years ago and mostly read it on Sundays while sorting through a tray of switches I had already lubed anyway. Some weeks it was worth your time. Some weeks it was three pieces of generic advice padded to make up a full issue.
What to expect in Tips For Mechanical Keyboard Weekly
Each issue breaks down into short sections. You will typically find one or two switch or spring picks, a mod suggestion like plate tape or stem polishing, a firmware or QMK note, and occasionally a reader submission that someone else edited down to something readable. The quality swings depending on who wrote the issue that week. The most useful issues are the ones that include actual test data rather than vibes. Switch actuation force curves, stabilizer notes with weight and thickness, foam stack diagrams, and clear before-and-after descriptions of a mod. The weaker issues just rehash the same three lubing videos everyone already watches.
How to actually use it without wasting time
Read the headers first and skip straight to the sections that match your current project. Do not read every word. The pacing is deliberately loose because the writers know you are skimming. If you are trying to choose between Gateron Milk Whites and Taro Jellies, go to that paragraph and nothing else. If you are debugging a rattly spacebar, jump to the stabilizer section. I keep a running folder in my email client tagged by topic. When a new issue drops, I scan the subject line and the first line of each section. Anything that looks potentially useful gets archived. The rest stays unread. This cuts a forty-five-minute read down to about seven minutes for most weeks.
Get the Full Details
When it is worth your subscription time
The newsletter becomes useful when you are stuck on a decision and need a neutral second opinion, or when you want to see what other builders are trying that month. Firmware sections are occasionally the fastest way to find a new setting you did not know existed. The community tips sometimes surface problems that have nothing to do with what the main writer covers. It is not worth reading cover to cover if you already build keyboards regularly. You will learn mostly the same thing each week, just with different examples.
A specific problem I ran into and how I fixed it
Last year they ran an issue recommending a particular foam layout for a planck-style board, and the instructions were missing the order in which you cut and insert the pieces. I followed the diagram as written and ended up with a layer of foam folded under the PCB so badly that the bottom row keys registered inconsistently. The fix was straightforward. I removed the foam entirely, traced the cavity with a pen on a fresh sheet of 3mm open-cell foam, cut the outline, and then inserted the piece sideways from the edge instead of dropping it in from the top. That kept the foam flat and aligned. The misregistration went away immediately. I did not bug the editors about it. Foam fit is one of those things that depends on your specific board and manufacturer tolerances, so the instructions were probably fine for someone else's kit. I just wrote down the workaround and moved on.
Counter-intuitive things most beginners miss
First, more foam is not better. Every extra layer changes how the case resonates and can mute your sound profile in a way that makes the board feel dead. In my experience, a single 3mm layer of PE foam under the PCB plus a thin piece of tape on the plate is usually the sweet spot for most sixty percent boards. Anything beyond that starts to cancel out the highs you actually want to hear. Second, lubing every switch on a new board is rarely necessary unless you are building for competition sound or you personally cannot stand any scratchiness. A selective lube job on the stems that feel rough and a light coat on the housing contact points gets you ninety percent of the benefit with half the labor. I used to full-lube every switch I bought. Now I only lube the ones that tell me they need it. It saves me about an hour per build. Third, switch weight recommendations from a newsletter are not universal. A switch that feels smooth at forty grams on one board may feel mushy on another because plate material, thickness, and MX stem length all change the feel. Test a few samples before committing to a full tray.
Common pitfalls to avoid
Copy-pasting mod stacks from the newsletter without checking whether your board uses a different plate material or thicker PCB will give you inconsistent results. A mod that sounds great on a polycarbonate plate might sound hollow on aluminum. Always note your plate material, PCB type, and switch model before trying anything you read. Another pitfall is buying switches based solely on a single tip. One good issue does not make a switch universally worth buying. Read a few threads, watch a comparison video, and check return policies. Some vendors let you test five switches before you commit to a full box. Use that option.
What the newsletter does poorly
It sometimes leans too hard on budget picks and underplays mid-range options where the real value lives. It also rarely covers newer hot-switch boards properly, so firmware and hot-swap compatibility notes can be stale by the time the issue ships. If you have a recent keyboard like a Keychron Q series with a newer hot-swap socket, assume the advice needs verification against the current manual rather than taking it at face value. There is also a tendency to repeat popular advice without much pushback. If three issues in a row recommend the same lubing technique, it might be worth searching for an alternative view instead of just doing what everyone else is doing.
Getting started with Tips For Mechanical Keyboard Weekly
You can find it by searching for the newsletter name. The subscription page lists recent issues and an archive. I do not have a direct link here because the URL changes periodically and I do not want to send you somewhere that might be broken. Once you are on the page, subscribe with your email and read the first three issues before deciding whether it is worth keeping. If the archive is empty or the signup is down, there is an active community forum linked from the same site where people post the tips manually. Use it as a reference, not a bible. The best builds come from mixing what the newsletter says with your own testing, not from following every recommendation blindly.
