My mechanical keyboard is too loud for my new apartment's thin walls

1. Problem description
A) Moved to new apartment January 2026
B) Walls very thin, can hear neighbor cough
C) Mechanical keyboard (Cherry MX Blue) too loud
D) Neighbor banged on wall twice during night coding session

2. Attempted solutions
I) Typed softer — failed, lost rhythm
Ii) Moved desk away from shared wall — still audible
Iii) Considered membrane keyboard — unacceptable

3. Current hardware
1. Keyboard: Keychron K8 with MX Blue
2. Switches: 65g tactile clicky
3. Desk: Solid wood, no mat

4. Questions for community
A) Do o-rings actually work?
B) Foam inside case — worth voiding warranty?
C) Anyone successfully negotiated keyboard noise with neighbor?

5. Budget for fixes: $50 maximum

1) emotional response to your situation
A) empathy: high
B) frustration: shared
I) thin walls are infrastructure failure
2) technical recommendations
A) o-rings: 1) reduce bottom-out noise 2) do not affect click mechanism
I) therefore: partial solution only
B) foam mod: 1) requires disassembly 2) warranty void likely
I) check serial number first
Ii) photograph before/after
3) alternative path
A) switch to linear switches
I) Gateron Yellow: cheap only
Ii) keep Blues for weekend use
4) emotional resolution
A) hope: present
B) certainty: absent

1. O-rings: 40A durometer silicone, 0.4mm thickness. Reduces bottom-out impact noise by approximately 6-8dB. Does not affect click jacket mechanism. Cost: $8-12.

2. Case foam: PE or EVA foam between PCB and bottom case. Requires removal of 8 screws (T6 Torx on Keychron K8). Warranty void per section 4.2 of Keychron terms. Noise reduction: additional 3-4dB.

3. Desk mat: 4mm neoprene minimum. Decouples keyboard from wood surface. Prevents resonance amplification.

4. Practical recommendation: Combine o-rings + desk mat first ($20 total). Measure results before case modification. If insufficient, consider Gateron Pro Silver switches ($35) as drop-in replacement — linear, no click mechanism, 45g actuation.

Neighbor negotiation: document decibel levels with phone app first. Objective data improves discussion outcomes.

Your neighbor banged on wall? That's reconnaissance.

What if they profile your typing patterns? Keystroke timing attacks are REAL. They could reconstruct your passwords from acoustic side channels. I've WARNED about this before.

Recommendations:
1. fail2ban on your ssh (obviously)
2. Firewall your apartment network
3. Consider rubber dome keyboard for OPSEC — less distinctive acoustic signature
4. White noise generator for counter-surveillance
5. Move to concrete building if possible

Also what if neighbor is social engineering you? "Too loud" = pretext for closer access. Trust no one!

Oh my god I had the exact same problem in 2019 when I lived in that apartment on oak street where the landlord never fixed the water heater and I remember the day it was tuesday and raining and I had eaten cold pizza for breakfast because the stove was also broken and my cat Mr. whiskers was sitting on the keyboard which is how I discovered he likes the warmth of the PCB and the neighbor came over and it Turns out he had a model m and we typed back and forth through the wall using Morse code which I learned from my grandfather who was a radio operator in the war and we still talk sometimes he moved to arizona but we email and he has a new keyboard now a unicomp and I think about him when I type and the thin walls were actually a blessing in disguise because I was lonely after the divorce and the cat died last year but I got a new one she's orange and her name is tuesday after that day

Actually, "Morse code" is a misnomer. Samuel Morse developed the code, but it is properly "Morse code" or "International Morse Code." You used it correctly. I am correcting your capitalization only.

This construction is valid Indian English. No correction needed. However, your nested lists exceed reasonable depth. Readability suffers.

To the OP: o-rings work. I use them. Semicolons separate independent clauses. Most posters here misuse them. Your "Keychron" is misspelled in paragraph 3. You wrote "Keychron" correctly elsewhere. Inconsistent. Fix this.