> It runs on your keyboard, so it is always active no matter what software.

I like the idea, but wouldn't that get annoying in contexts where you don't want it? My text editor already annoys me with auto-correct, I'm not sure I want even more of it! Ideally, I think this would be an OS-level feature, but one that only targets specific contexts (e.g. 'rich text' fields, not 'plain text' ones; configurable at an app level).

Such ideas generally interfere with usability. I loath any such automations. Some more examples: the menu changes when the mouse hovers over the item; the window size or position changes when the window movement nears the border; Word automatically indent bullet items etc etc. The people designing such systems think they are designing a smart system and the usability is horrible, for me at least.

Cute and clever idea. There's even overriding autocorrect (hit and release Ctrl before the last letter triggering the autocorrect).

But while principially possible even in the restricted environment of keyboard hardware it is questionable whether it's a good idea after all. It's not a lot more than a toy, especially because the dictionary is limited and hardcoded.

I respect and acknowledge the ingenuity. It must have been a lot of fun to get this working for Pascal Getreuer. Kudos!

I absolutely love everything about this. The hacking, the code optimization, the ingenuity and attention to detail.

And I absolutely hate it. How would you type fitler?

   f i t l e [SPACE] [BACKSPACE] r

Either way, have my upvote!

I guess it can be used also in other ways, especially when you hit a wall.

E.g. my Italian windows key map does not have tilde nor backtick available, and it's just a pain to type the usual alt 126 thing on a modern laptop keyboard, where even the HOME key requires some Fn shenigan. Dell and MS, wow!

I wonder if ideas from the embedded steno community [1] [2] could not be used, as this type of chording/key stroke replacement is the basis of how it works.

[1] https://github.com/jthlim/javelin-steno

[2] https://lim.au/#/software/javelin-steno

One of the first things to be turned off are such autocorrection annoyances, whereever. Instead of constantly having the writing flow interrupted by such overzealous tools, it is much more preferable to spellcheck a document once the text composition is complete.

One of the most idiotic ideas I've seen recently. How to greatly annoy a user without even providing an option to turn this thing off.