Current Construction Projects:

  1. Finish Drywall/sand/paint and install trim to office Door
  2. Kids tree-house base/floor
  3. Main bedroom bath exhaust fan install
  4. Kitchen Range exhaust fan/vent install
  5. Build out fire walls for server room
  6. Finish Fiber pull to server rack and Terminate *new since now I remember I still need to do this too

Current hardware projects:

  1. Kids custom 3d printed TLK keyboards
  2. Micro cluster rack mount design
  3. Micro cluster storage solution
  4. De-com old server, ship to Xydros
  5. Move racks to server room
  6. Rebuild rack layout
  7. Add UPS to wireless/nvr/camera equipment

Software Projects:

  1. OPNsense/PFsense update
  2. Pihole for DNS
  3. Degoogle storage
  4. Degoogle photos
  5. Degoogle calendar
  6. 3-2-1 bakup solution
  • infinitevalenceOPEnglish
    1·
    1 year ago

    I only build my own now because OEM software is garbage next to QMK/VIA. I used to have a GSKILL Ripjaws Mech board but all the macro keys would only work if the software was running. On top of that it the software would only work when directed connected to the keeb.

    Since I use Linux and a physical KVM there was no way for me to take advantage of the extra keys, and I could not control the lighting :(

    The final straw was when one of my switches got gummed up and i could not just pull it out and swap it without totally deconstructing the board and desoldering the switch.

    So From that point on I will only buy/build boards that support QMK, and are hotswap. If the board is not hotswap by default like the HINEY boards above then I will solder in milmax sockets which convert them into hotswap.

    Now that most of my boards are QMK (the cheap Redragon 60 is the only one that is not) I can build all my macro’s into keycodes that work regardless of the operating system, and will pass a KVM with HID emulation.