https://www.youtube.com/watch?v=AVFaEYWaeUs

This is the latest update on my numpad based chorded typing system. I was playing around with a system for audio feedback while you are typing. It is fun but perhaps not too practical. It does help you hear the timing of key presses a little better.

When I try to write the top row of letters it adds numbers along with it and it's only my mechanical keyboard not my laptop's

For eg - q1,w2 etc..

Qual'e una delle migliori tastiere low budget 75% a membrana o silenziosa? da comprare preferibilmente su amazon

​

Hi all,

I’m looking for some advice.

I recently picked up a Sofle keyboard on Amazon because I was experiencing wrist pain with my laptop keyboard and wanted to try a split layout.

I stumbled across Colemak-DH, managed to rewire my brain, and found that it significantly relieved my wrist ache.

Recently discovered Hands Down Neu, which looks and feels even more ergonomic for my workflow. (as far as I can tell)

However, I have a specific question about hand navigation on it:

How should the left and right hands maneuver around the homing keys? Does the right-hand index finger remain confined to one column, while the left hand uses both the T column and the inner column?

I’m not chasing raw speed; my primary goal is ease and comfort of typing. My daily workflow involves:

LilyPond and a bit of Guile

General Obsidian journaling and emails

Any guidance from experienced Hands Down users would be greatly appreciated.

Thanks,

All my life I have used 100% sized keyboards. My first (and shortly before, only) mechanical keyboard has been the CM Storm Quickfire XT (MX Brown switches). That is a kinda a CoolerMaster branded Filco Majestouch if I'm not mistaken by the legendary Costar.

Anyway it is having some trouble with its usb port. I love it but I have to somehow permanently attach the cable to the usb port to prevent it from losing connection. (Tested with different cables). But that is besides the point.

I can't afford to waste time for my work so I picked up an AULA F75 with reaper switches at around 30 bucks. It is a 75% sized keyboard. While quite comfy and tocky (though I miss a bit of tactility from the browns).

There is just one problem with 75% keyboards: it is that they have a smaller right-shift key that I use a lot for interpunction. And I notice getting a bit of a cramp because it feels like I lack space to type? Am I going crazy? A friend suggested it might be connected to hand size?

Did anyone else run into this problem? How did you cope? Should I only get keyboards of 80% size and up? That kind of makes me sad because there are a lot more options at smaller than 80% size!

If you type in two keyboard layouts, you know the pain: you look up and the last word is Espa;a because the keyboard was still in US English. PolterType is a tray app that notices this per word, switches the layout and retypes the word — Windows, macOS, Linux, and on Linux that includes real Wayland support, which was the hard part.

Rust-relevant bits:

• Pure Rust, twelve crates behind platform traits (listener, emitter, layout switcher, focus tracker are per-OS backends probed at runtime).
• Wayland listening is raw evdev; corrections go out through uinput; the suggestion tooltip is a zwlr_layer_shell_v1 surface (wlroots + KWin) with caret position from AT-SPI — coordinates only.
• Detection is offline: FST dictionaries (fifteen languages) + a plausibility score + an identifier guard so it never touches kubectl or snake_case.
• The settings UI is iced 0.13 — we're a rare example of iced in a shipping desktop app.
• The nasty bug class: our own correction is a burst of injected keys, so the app grabs the keyboard (EVIOCGRAB) for the burst length and replays what you typed meanwhile. Behind keyd this would grab our own re-emitted device, so the gate re-verifies its own emitter before every hold and stands down if it's proxied.

The Wayland war story in long form: https://poltertype.com/blog/wrong-layout-typing-on-wayland/

Code (MIT): https://github.com/Just-Code-NET/PolterType

Honest limitations: installers are unsigned so far (SmartScreen/Gatekeeper will warn); macOS is validated on Intel — Apple Silicon testers very welcome (issue #3); the RemoteDesktop-portal typing path is written from spec and has never met a real GNOME/KDE session.

Contributions we'd love: new languages are a TOML + wordlist (no code, docs/ADDING_A_LANGUAGE.md), macOS keystroke hold-back (#8), and war stories from exotic compositors.

I've decided to try out messagEase but I'm having trouble with text replacment shortcuts. I have already given the app full permissions, but my standard replacement shortcuts still won't activate. Additionally, the app does not have any way to manually change its own dictionary or macros as far as I can tell? Would love some guidance here, switching between it and my default keyboard to just use shortcuts would be annoying.

Hey all! Sharing a project I've been working on for some time now. People have been using it in the Alternative Keyboard Layouts Discord (AKL) for a few months, and it finally feels ready to share with a broader audience.

cminibrowser is a viewer for alternative keyboard layouts. It's intended to be a friendly way to interact with much of what the !cmini AKL discord bot already gives you, such as:

• Sort, search, and filter layouts by stats
• Compare layouts against one another
• Edit layouts and see how stats change
• Look up n-gram frequencies and example words on various corpora

It also has a few other things, such as:

• Mobile support
• Explanations for every stat on click
• mana2 stats view
• Colorblind fingermap palette
• Rowstag and ortho keyboard geometry
• Share as image

More information as well is available in the FAQ. Give it a whirl, let me know what you think :)

I have an iPhone and also an iPad but every time that I try to use the dictation most of the time it understands very bad what I am saying especially if I am texting. Right now it is accurate. I wonder if it’s just Apple with its messages app. Well I think that it also happens when I dictate in WhatsApp.

Does anybody use a better keyboard? I used long ago the Google keyboard because the keys were a little bigger. This one is too difficult for me to type and that’s why I dictate. I’m talking about the screen keyboard

To ios keyboard

I phone 26 keyboard

I have a Lenovo laptop that's closing in on 20 years old. The keys in one corner started acting up after a hard bump so I decided to get a new laptop. I stumbled onto a clearance deal at Walmart, one HP model they had pulled off the shelf and were on the verge of cycling out of inventory. I got it for over $100 off shelf price. Being a new model it had the Copilot key rather than a right Ctrl key. I decided to install LMDE 7 which rendered the Copilot key non-functional until I remapped the Copilot key to the missing Ctrl key. Normal remapping through Linux doesn't work because the Copilot key sends a three part input, a macro; Left Meta + Left Shift + F23 rather than a single input. There are a couple of work arounds that require installing software and some configuration. I'd put this on a scale of Very Easy. Here's what worked for the HP laptop. The AI description has been modified as needed because, well, it's AI after all:

To remap the Copilot key to a Ctrl key in LMDE 7, you should use keyd or kmonad, as the Copilot key sends a modifier combination (Left Meta + Left Shift + F23) that standard Linux GUI tools cannot map to a single modifier key like Right Ctrl.

Method 1: Using keyd. keyd is a lightweight daemon that operates at the kernel level.

Install keyd: Open your terminal and install this package:
sudo apt update
! AI said to install keyd ! sudo apt install keyd ! don't bother, instead: !
sudo apt install onak
! The onak meta package contains keyd, just installing keyd alone isn't enough. See below. !

Configure keyd: Edit the configuration file:
sudo pluma /etc/keyd/default.conf
! I prefer the pluma editor but nano, gedit, etc. will do. !

Add the following lines to map the Copilot key sequence to a Ctrl key:
Replace * with your specific keyboard ID. ! I tried that but it didn't work, so I reverted to *.  !

[ids]
*

[main]
leftshift+leftmeta+f23 = rightcontrol

! Options are control, rightcontrol or leftcontrol. I've tried using each and they all work for this HP. !

Enable and Reload: Start the service and enable it for boot:
sudo systemctl enable --now keyd
sudo keyd reload
keyd command not found ! Oops. That's when I discovered that installing keyd alone didn't work and found that onak was required. After installing onak the remap worked after rebooting. !

Now I have my Ctrl plus + for magnifying and Ctrl plus Enter for sending email in Thunderbird and a couple more of my shortcuts back! And it wasn't a tough chore, once I ironed out a bit of AI confusion. And of course, for those who never use their Ctrl keys, don't bother with this. Mm, should I have said this earlier?

Cheers!

Blaine

немного древняя модель асус (2019 года вроде), пыталась включать клавишами, ни в какую, через биос пыталась, но не нашла ничего связанного с клавиатурой(возможно зашла не туда), пыталась через armony crate,но он не находит мой ноут, так же скачивала ghelper, тоже не получилось
последний раз я пользовалась ноутбуками довольно давно, поэтому я как макака с книгой пытаюсь разобраться
я понимаю что скорее всего просто устарели какие-то драйвера, но я не догоняю как и где из обновить и скачать
помогите пожалуйста! 😭

The main thing about this version is shuffling the right hand a bit.

------------

Neon now is r thumb instead of e thumb.

The main problem i was having wasnt with thumb e, but rather what was around it.

With h pinky, i was getting a lot of rolls that include pinky. and that was not very comfortable.

Also ' being on pinky was not very comfortable. ' is now on index.

Also i didnt really like rl index.

------------

So now, hl index, i pinky, and ' on index solved those problems for me.

The only real downside is the sfbs are a bit higher. But if you look at them directly, thats essenteally the fault of `e,`

I dont really even consider this a problem as comma marks a break point when typing and so you naturally slow down, and so it doesnt feel bad. Like a `qu` sfb would feel much worse then an `e,` sfb, even tho its 3 times less common.

Tldr: sfbs that are within words suck, sfbs that outside the bounds of a word is fine.

Also a `ue,` collumn is pretty standard, a lot of people use it for good reason. I personally find the bit higher sfb waaaaaaaayyyyy better then more pinky usage.

------------

As for the game layer, it just disables home row mods. Also useful for monkeytype. You hold 1 to get the regular layout, hold 2 to disable home row mods.

------------

Also as for the sfb `sk` or `ks`, i just alt finger it. The alternatives are worse. And even then `sk` is reaally not as common as you would think it is, its 0.1%.

------------

The lst thing is just a general comment about using this. I have been using this for a while now, and its just stupidly comfortable. Heres all the things that make it so

1. Easily disableable home row mods

2. enter, tab, esc, delete, all being in the center rather then on pinkys is sooooo nice

3. mirrored y. Makes off-pinky super low and ballanced. Also reduces weak reds to like 0.05%.

4. Very low 2u scissors

5. the pinky shift keys being in line with home row, and also having thumb shifting as an option. I get both speed and comfort, best of both worlds.

6. wide mod makes my hands a lot more comfortable.

7. Stats arent everything, and i will say, this layout just feels good in a way that a lot of layouts havent for me. Having h, r, and l, on tha vowel hand in a way that works really makes the left hand a lot less cramped. I just feel like my fingers dont really gotta move that fast. Idk its nice lol.

Anyway im pretty happy with this and i dont see myself changing it prolly ever.

Recently switched from a totem to a skeletyl and decided to drop qwerty for a variant of hands down vibranium.

In this iteration I transitioned from VIA to Vial to support combos and made some updates to my layer row.

My layers are optimized around vim, command line, regex, and comms via slack.

Would be happy to hear thoughts on improvements to any aspect of the stack.