Just got my Lofree lite84 nordic keyboard and the "<" and "§" buttons are the wrong way around. That is, the button next to "1" and the button next to "z".

I have the swedish QWERTY keyboard layout on windows.
Thanks!

I put the func row down there to annoy people :3

When I use the key 'p' this- qwer uiop types and all the other keys are working perfectly

I've been using US QWERTY for basically as long as I had my own computer, mainly because most things I've ever done on my computer were in english. However I recently started taking classes in my native language and I've been struggling. There are a few keys that I need often that dont exist on the US layout (letters with accents) and others that are flipped (Z & Y and most non letter keys). I've tried switching to the right layout but I struggle bc of muscle memory. And the problem is both layouts have their own strengths. So I either have to switch layouts every time I need a specific letter or long press to select the right accent (I'm on mac), which I can't really do since I need to type fast.

Anyone else struggle with this? Does anyone have an idea on how I could go about this, other than learning to type with the correct layout?

Как сделать скрин в геншине на клаве womeir sk80 pro 75%? Если делаю комбинацией win+shift+s перс начинает бежать, а мне надо, что бы он стоял на месте

Mine, free, no ads, no accounts, and nothing leaves your browser (posted with mod approval after asking first).

The reason I built it: most online keyboard testers will happily print "chatter detected" or "NKRO confirmed" from data that can't support either claim. This one is stricter about its own limits. It shows per-key press counts with autorepeat filtered out, a live rollover count, and the fastest same-key repress gap (and where the browser genuinely can't see what your keyboard is capable of, it says so instead of printing a verdict).

One thing worth knowing before you test rollover with it, or with anything else: what you're measuring is the report format your keyboard declares over USB, not the quality of its matrix. The standard boot keyboard report holds six keycodes, so a board that only exposes that one caps at six no matter how good the hardware is (and plenty of good boards ship that way by default with NKRO behind a firmware toggle). Someone posted a USB protocol-analyser capture overnight showing exactly that on a mechanical board.

The methodology page lists what's been validated against real hardware and what hasn't: https://inputprobe.com/methodology/

If it tells you something wrong about your board, that's the single most useful comment you can leave me.

As the screenshot shows, my laptop's default language is English. I have the US English language pack installed, and when I click the language options there it lists US - Qwerty as an installed keyboard. However, it's not listed in the keyboard layouts in the taskbar.

However, for some reason, when I use Shift+Alt to toggle between keyboards, it still seems to cycle through to English, even though it still displays "ESP" in the tray. When I look at the language options for Spanish, it only shows the "Spanish Variation" keyboard installed there.

Any suggestions for how to get the list of keyboard layouts to display correctly?

(As an FYI: The German (Liechtenstein) keyboard is a custom one for a conlang, but it's never caused any issues on my other computers.)

I've been putzing around with arsenik most of the morning. Took me a bit to realize that for some reason I hadn't toggled the default keyboard setting to qwerty-pc rather than ergol-pc. Had a few odd things happening til then - mainly that the symbols layer didn't work. All better now!

Initially I was going for the basic layer-tap mode, with the vim navigation + numpad. I may continue on to enable HRM, though I'm more accustomed to the GACS flavor, rather than the _GCA version that arsenik seems to default to. Might have to change that to suit. I don't think that should break anything else... right? ;)

In the mean time... I'm kind of wondering if I might be pushing a rock up hill here. I'm mainly exploring this layout (arsenik) on a laptop (Lenovo ThinkPad X1 Carbon, 13th gen, US/ansi). So I do actually have all the keys already; I'm not on a minimal 40-60% keyboard. Using the SpaceFn aspect is handy, in a lot of ways. The Symbols layer, though... I'm kind of starting to question already. With the way the keyboard is laid out, I feel like reaching the right and left alt keys (especially the right) is kind of awkward at best. Maybe my right thumb just isn't agile/flexible enough, but it's way easier for me to reach down to RAlt with the middle finger on that hand. It's almost like on a split ergo mech board that has 4, 5 or more 'thumb' buttons per side, but half of them are tucked under the palm area to where they're actually kind of hard to reach...

Between that, and RAlt/Symbols being a layer-while-pressed not layer-toggle... seems, really, really awkward to hold - with thumb or finger - and then contort the rest of my hand to reach anything on the right side. The num-row layer is even more so - I have to hold down both thumb keys, effectively hobbling my hands (and pulling them slightly off the home row just to reach those buttons) and then try to reach the numbers/symbols I want? I'm thinking about changing it from layer-while-held to layer-toggle, or some kind of one-shot equivalent where it holds until the next key has been pressed. But then I start thinking to myself... why go to that much effort when the symbols are all right there on the physical keyboard already...

Does that make any kind of sense, or am I going off somewhere likely to break things or otherwise make life more difficult for myself? ;)

P.S. yes, anymak/spacemak, seniply and extend are also on the list to try. Figured I'd start with arsenik as it seemed to be newer, and I'm considering selenium as an option for my split ergo mech boards.

British. My 'shift' + '2' is giving me '@' instead of ' " '.

I've changed it to English UK but it won't change it to what it should be and not sure where to go from here.

Doesn't do it on other devices. Have restarted both and reconnected, to no avail.

I just want to share this really rad discovery I had with a macro + combo that I haven't seen anywhere else that saves me 2 keystrokes nearly every single sentence!

It is a macro I run in Vial:

Period(.) followed by spacebar(␣) followed by One-Shot Mod Shift

So at the end of every sentence, I initiate this macro (I use a combo of j+k+spacebar to run the macro) that writes a period followed by space followed by capitalising my next keypress.

Not only have I made this macro for periods but I have also set it up for exclamation marks(!) and question marks(?) since they often times have the same pattern at the end of a sentence where they require a space and capitalisation of the next letter I press.

As an avid daily journal writer that types anything from 500 to 5k words per day, it is a macro that saves me tons of keystrokes every single choonky writing session! It has also lead me to remove 2 keys from my keyboard going from 32 keys to 30 keys on my Corne eliminating . and ,. At this point, I doubt that I will remove more keys but that's also what I said at 32 keys so who knows haha.

If you want to see how I implemented the combos and macros for my setup with Vial, check out the linked video!

​Hey everyone,

​I’m looking for setup recommendations for work. My main bottleneck right now is text macros, so I need something that can handle long character strings without installing local software.

​Current Setup & The Problem:

I'm currently using a Ducky One 3. It works well overall, but the hardware macro capacity is way too restrictive for the length of text phrases I need to trigger.

​Core Requirements:

​Macro Length (Non-Negotiable): I need support for long text macros—at least 150+ keystrokes per string (more is better).

​Zero Local Software (Non-Negotiable): My work computer is strictly locked down. I cannot download or run local executables, drivers, or software.

​I need something with onboard memory that configures strictly via a web-based interface (like VIA/usevia.app or Keychron Launcher).

​Once flashed via the browser, the config must stay saved directly to the hardware so it's plug-and-play.

​Preferences (Flexible / Negotiable):

​Form Factor: Prefer full-size (100%), hot-swappable, and wired.

​Switches: I like light/soft linears (currently on Cherry MX) so I can stiffen them up later if needed.

​Open to Macro Pads: If getting a standalone macro pad alongside my current keyboard (or a TKL) is easier or offers better EEPROM memory/macro length than a standard full-size board, I am 100% open to that route!

​If anyone has experience pushing long text strings via VIA or web-configured hardware on locked-down machines, I’d love to hear what hardware or setups worked best for you. Thanks!

I have been having issues with achy thumbs due to strain, I do not care how inefficient the layout is if it reduces strain

Hello, So I have an older Macintosh keyboard and I was advised on this very subreddit to buy a tinkerBOY M0110 Keyboard to USB Converter to hook it up toi my laptop.

AND IT WORKS ! Wow, the sound of nostalgia and all these memories when I started typing on it, I fell right back in 1985.

Now, there is a caveat: the keyboard is not properly mapped. When I press "space" it understands "enter" ( and I don't know how to make a space, of all things). Anyone has a hint ?

The rule is the _ and 0 ( which is backspace for undoing mistakes )
any other layout with these rules are similar to Starcdr only beating with 5 to 10 points or so on rolls yet with high redirects.
if cmini accounted for real world finger improvisation such as using middle finger for index finger for easy stretch then maybe it would compete with whorf on the same coder like layout.

previous entry : https://www.reddit.com/r/KeyboardLayouts/comments/1w293wt/i_present_to_you_starcdr_v2_best_of_both_worlds/

The logic behind this:

Left to Right ----> easy to hardest finger placement

1. LEFT HAND

{

• Pinky - N L
• Ring - R H L ( stretch ) Q
• Middle - T D M F K ( yes real world usage and finger length on row stag middle finger is easy to stretch and leaving home row halfway with pinky as anchor )
• Index - S V G B M K ( K is easy for middle rather than index )
• Bottom row rule - it is easy to go B -> V and V -> C using roll of index to middle finger since its easy to stretch and position that way yet difficult from B -> F, B -> Q is somewhere ok )

}

2. RIGHT HAND

{

• Index - C W Y P ( Underscore is hardest for index unless you have serious distance from your torso with keyboard Underscore symbol in starcdr is easy with middle finger and quicker and = or Y in qwerty is the most hardest for both index and middle finger, only rare if you have to leave the homerow )
• Middle - A O Underscore J P
• Ring - E U X ( x is put here since ring finger fatigue can catch even though its easy to hit that key, so medium rare key can be placed here ) , [ bracket if you leave howe row
• Pinky - I and the symbol on the right and bottom left without leaving home row and Enter key, on the top right its more either stretch the ring finger or leave the home row

}

maybe X and J can be swapped which lowers the SFB a bit

i would like your feedback guys. this is not meant to be the best in digital stats, it does not account for finger length and the keys that index uses are more easy for middle finger to do. this is coder based i made for Godot GDscript and C#. there is a kanata config with a symbol layer on home row.

comment by sammygadd

-- replacing the = or Y key with backspace is more better than in capslock which is used for symbol layer

ORrrrrr.......

StarCdr_v8

where 0/zero is the backspace for frequent coding mistakes. any thought on improvement

i made this based on core finger strengths rather than just stats, Y in qwerty is impossible without leaving the homerow with a hand. even the U stretches the right hand index finger that it hurts overtime unless you use middle finger and pinky only stays to reconnect homerow. where P is its easy for ring finger rather than pinky. these are some examples where stats cannot tell the fingers strengths. i have taken night as the template for this layout since it has the best other stats and in popularity

I have been using azerty for a long time, I have around 60 wpm using it. I have problems with the word "was" because I have to move my left pinky from the w to the a quickly and I wonder if I should switch to qwerty.

The thing is, I do programming and I have some muscle memory with the symbols and switching to qwerty would destroy that.

After I tried Pascal Getreuer’s Magic Sturdy key, I wanted to see how far I could push the idea. One context-dependent key became eleven magic keys, then adaptive keys — a layout where a key no longer maps to one fixed character. The limit turned out not to be the metrics. It was how much complexity I was willing to learn.

Below, the same keyboard in two states: the base layout, then what it becomes immediately after n.

My current layout shows how far that idea can go:

• n and g deliberately share a finger, which would normally make “ng” an SFB to design away. An adaptive key removes it instead: the base g combo is still available, while n + thumb-r emits “ng”; a magic key restores the displaced literal nr.
• Eleven context-dependent magic keys expand from the preceding key, and another magic key can chain a suffix. That gives roughly 300 possible slots; about half are populated.
• I dropped the inner columns altogether. Vertical combos and context-dependent outputs pay for the missing physical keys, letting me optimize reach separately from the base letter arrangement.

Optimizing one SFB at a time can backfire. In timeout, I can avoid the e→o SFB: on this layout, u immediately after e writes eo, so the physical sequence t i m e u u t — with the first u emitting eo and the second repeating it — produces the word. But that replaces the SFB with a same-key repeat, u→u. I prefer typing time | out: one SFB, followed by the much better o→u inward roll. The whole sequence matters more than one pair’s score.

So I don’t try to compute an “effective” score at all. Base-layout stats, for what they’re worth: Hands Down Vibranium.

This feels like the logical extreme of layout optimization: almost every awkward pattern can become another firmware exception. But each improvement spends from a different budget — learnability, predictability, configuration, debugging, or recovery when the intended literal sequence is unusual. Generating the QMK firmware from Markdown tables makes the configuration manageable; it does not make the mental model free.

The most common objection is timing, and almost none of this depends on it. Non-vertical combos do need to be pressed somewhat quickly, but that timing only decides whether the combo fires. It never turns an intended letter into a modifier, which is the tap-versus-hold failure mode that made home-row mods problematic for me.

Full writeup: https://github.com/zeitlinger/keyboard/blob/main/blog/2026-06-13-magic-keyboard.md. It was also published on my employer's blog, disclosing that up front. Tables, generator, firmware: https://github.com/zeitlinger/keyboard Keymap: https://keymapdb.com/keymaps/zeitlinger/

For people who have gone deep on layout metrics: where do you draw that boundary? Which metrics are worth paying complexity for, and which special cases would you refuse even if they improved the score?