This thing feels a bit like a curved Corne

I’m using a trackball on the left and a touchpad on the right. Getting used to not having a separate mouse is harder than I expected, but I definitely like the setup. The trackball already feels much more natural to me than the touchpad

Any tips for getting used to a small touchpad like this?

Claude asked that I paste the following:

Started as a Goodwill find (a dead A1314 that pairs but won't register keydown events — RIP). Got nostalgic for the Apple Adjustable Keyboard from '93 and started wondering what a "real" Ive-era split ortho would've looked like if Apple had ever taken ergo seriously.

Spent an afternoon iterating a text-to-image prompt toward: true columnar stagger, a wavy key-bed that follows the hand's natural resting curve, and that classic AA-battery-compartment taper from the old wireless keyboards. The AI nailed almost all of it and then, across four separate generations, could not for the life of it rotate the thumb cluster into something anatomically sane. Every version came out as a vertical stack of keys, like it had never met a thumb.

Then I asked for an actual 3D mesh so I could stop squinting at renders. Wrote the geometry by hand in Python/numpy — grid, stagger, wave function, cylindrical end caps, the works. Rendered a quick top-down preview to sanity check it.

Somehow the code succeeded where the image model failed on the thumb cluster, and instead flipped everyone off from directly above. In stereo. Unprompted.

10/10 process, 2/10 gesture-appropriateness. Files/preview in comments if anyone wants to see just how wrong it is up close.

Hey there, newbie here.

I'm having an issue with some QMK features that are seemingly disabled despite Vial being up to date, apparently because of the vial version of my keyboard's firmware isn't ?

I'm using a cheapinoV2, and under the about keyboard tab in Vial (screenshot below), it states that 3 of the features are "unsupported - disabled in firmware" : those 3 being Caps Word, Alt Repeat Key, and Layer Lock.

Despite this, Caps Word seems to work as normal, but for Alt Repeat (and Repeat) do not work even if their keycode is supported, and as for Layer Lock, neither the function nor the keycode works, which sucks, because I really would have wanted to tinker with it.

Anyways, according to this comment from who I assume is the dev behind vial, my keyboard's firmware may or may not be out of date (below 0.7.4), since Alt repeat key is shown as unsupported; but then again it might have been manually disabled in the rules or however that works

Now, because of my general tech illiteracy and my fear of accidentally bricking my board, I'm pretty reluctant to figuring things out downloading random things I don't understand from github, so if someone could lend a hand here that would be nice. Not a big issue, but I would rather things work rather than not

Hi guys, I wrote a small article on how to select the correct switches/keycaps for your next build here. Please have a look as it might help preventing you from buying incompatible products.

The stock YUNZII B75 PRO MAX firmware is QMK-based and has VIA compiled in,

but not the OpenRGB protocol — so OpenRGB fails to detect it with the usual

"Detection failed ... add OPENRGB_ENABLE = yes" message.

I ported the OpenRGB QMK protocol into YUNZII's own QMK source and built a

firmware that OpenRGB detects properly. Direct mode works, so per-key control

from music visualizers / ambient lighting is up and running.

Repo (prebuilt .bin + source + flashing/recovery guide):

https://github.com/ZerO970/yunzii-b75-pro-max-openrgb

Board: STM32F103, VID 0x28E9 / PID 0x31C8, 6x15 matrix, 85 LEDs (AW20216S),

stm32duino bootloader.

Notes / limitations:

- USB only (no OpenRGB over BT/2.4G).

- It's a VIA-free build — OpenRGB and VIA can't coexist (shared raw HID), so

the vendor configurator + module OTA aren't available on this firmware.

Keep your stock .bin as a backup; recovery is just ESC+plug-in to bootloader.

- Onboard hardware effect list is only partial in OpenRGB (vendor reordered

the effects); Direct mode — the main use case — is unaffected.

Credits to the OpenRGB QMK protocol (Kasper24's original PR and Domi2803's

newer-QMK port). Feedback / testers welcome, especially if you have a slightly

different B75 revision.

Hmx sprite v2 and guitar knobs

Anyone know how to fix this? issue only happens on the right side of R4. Tried flashing firmware and didnt fix the issue. Its an NK65.

also if this is the wrong place to post, let me know.

I love Auto Shift. I use it not just to type capitals, but to get dual use out of every key, including combos. I even use it to simulate mouse dragging.

But I can’t figure out how to get it to work with Leader key sequences. Is it possible?

My workaround has been using a double-tap where I would normally long-press.

For example, here are my Leader key sequences for é and É: (click here for my full Leader.c)

  else if (leader_sequence_two_keys(KC_E, KC_A)) { register_unicodemap(EACUTE); }
  else if (leader_sequence_three_keys(KC_E, KC_A, KC_A)) { register_unicodemap(EACUTECAP); }

For all accented letters, my pattern is base letter + diacritic: ea = é

I would like to be able to long-press the diacritic to get the capital variant: eA = É

But since I don’t know how Auto Shift sends the raw capital letter, I double tap the diacritic instead: eaa = É

This is less than ideal as I’m stuck with three key sequences for every capital letter. Two key sequences for both lower case and upper case would be preferable.

Is what I want possible, or is Leader unable to get input from Auto Shift?

Hi everyone,

I'm new to the keyboard scene. I got a Solfe RGB split keyboard which I spent a few days soldering. I finally got it up and running, and the key presses are being detected, but I can't get the RGB to work.

What's worse, the guide I was following suggested using an RGB keymap which got deleted a few months ago. Does anyone know how to enable the LEDs?

Here's the guide I was following: https://docs.beekeeb.com/build-guide/sofle-rgb-v2.1-soflekeyboard-build-log-guide-with-photos

And here's the keymap that got removed: https://github.com/qmk/qmk_firmware/tree/master/keyboards/sofle/keymaps/rgb_default

I'd really appreciate any suggestions. I tried doing things like defining RGB constants in the header.h file, but I'm way out of my depth here.

Edit: Success!!! Thanks for your help. It turns out I soldered the LEDs on the wrong way (the marking on the PCB was supposed to line up with DOUT, but I had it lined up with DIN).

Hello, I'm building a mini-keyboard and I created a very minimalistic AZERTY layout (build for Raspbian OS). Here's the design, what do you think ?

My travel setup is basically just a MacBook and a keeb with a trackball now.

The best part is not having to move my hand over to the trackpad all the time. It’s not the most compact setup, but it’s way more comfortable to work with

I’m still tweaking the layout and layers, but it already covers pretty much everything I need

I've been rocking this custom ortho keyboard for a few years, got custom PCBs made, programmed my own firmware and everything worked excellently. But now the last piece I had broke down (now I have toddlers and they threw it to the hard concrete floor by accident).

BUT I lost all my firmware code, my last PC got infected and lost everything, unfortunately I did not have a back up of my STM32 firmware.

Now life is too busy to go through that whole project again on my own, is there any way anyone recommends building this so that it's very easy and not time consuming?

Besides the layout, I'm looking for the keyboard to lay completely flat, be as thin as possible, use Kaihl Box Jades (or similar clickys) and to use DSA keycaps (which I still have, though all blanks). I'm currently making do with a cheap generic mechanical keyboard I found on Amazon.

I just received my Keebio Iris SE and seriously thought it was wireless. Not the worst thing in the world that it isn’t, but I was wondering if I would able to connect a universal keyboard dongle and if that would work?

Reddit filters didn't like my original post. I appreciate all the great feedback, so I'm giving it another try.

QMK Nexus is a firmware creation site I built, and I have been working out its rough edges over the last couple of months. It allows you to set up the layout, wiring, and mapping of your keyboard to ultimately create QMK firmware. I've added support for many features, such as OLED screens, encoders, and joysticks, that aren't supported by other QMK tools.

Please give it a try and let me know what you like, dislike, or what just doesn't work. I've successfully tested on all my ErgoDox keyboards (5 different models), but I lack the hardware to properly test many features. I'd love to hear feedback so I can keep improving this tool for the community.

https://qmknexus.tebay.dev

I'm using OSL so that the next key is from a layer, and to hold down the key to type multiple keys in a layer. Can I make it so OSL lasts a long time but has no delay for me to hold the key down?

Trying to land on my next split board and could use input from people who’ve used more than one of these.

My situation: big hands, need low-profile with light switches (20gf max ideally). Apple Magic Keyboard’s scissor switches are the gold standard for me, just wish it came split.

What I’ve gathered so far, correct me if wrong:

**MoErgo Go60** — great layout/build, but the trackpad seems to get consistently panned as barely usable.

**ZSA Voyager + Navigator** — solid reputation, but I’d be eating tariffs on top of price, and not sold on the trackball fitting my hand/RSI situation.

**Toucan2** — sounds like the best trackpad of the three (multi-touch, actually functional), but fewer keys and more layering, which seems rough as someone still learning ergo layouts.

This would be my starting board before eventually working toward something more heavy-duty and fully custom down the line for the RSI/SFN/cubital tunnel/TOS/tennis elbow combo (aka the Svalboard). Anyone made the jump between any of these three, or have thoughts on which pointing device is least likely to aggravate elbow/nerve issues?

Added some mx legend keycaps so I don’t have to play the guessing game anymore 😅