I type for fun and 76% is awful. If I dip below 85% I instantly stop. 76% means I have super cold fingers while having butter slathered all over the keyboard!

That's why you should never watch Bear Grylls, Gordon Ramsay, and a Sandi Metz video at the same time.

Possibly best HN comment ever

“CharaChorder’s internal processor arranges the letters on-screen in real time faster than the human eye can perceive.”

So, 76% may also be an artifact due to the way the keyboard interprets inputs rather than something a user would need to correct.

I own a CharaChorder and this is exactly right. Using the CC, you can't get 100% on monkeytype because when I type `helo` it then backspaces that and types `hello` using the CharaChorder's onboard firmware.

The final text is 100% accurate--it's just what was typed by the keyboard wasn't 100% accurate.

What if you're debugging SMTP and you actually meant HELO?

Our keyboard gives users a sense of pride and accomplishment when they type at 200 WPM. User testing has revealed that most of our customers can't spell. We are proud to have made autocomplete an integrated hardware solution on our entire line of products.

As explained downthread it's not misspelling, they're using a chord.

The device allows character entry--you just type h, e, l, o just like you would on a keyboard.

You would know if it was a chord or not--not every word you type will be one.

Outlook, word and I think even google keyboard does the same thing. You have to basically type it again in them and they take it to mean you don't want it autocorrected.

It is the first thing you disable though.

Exactly, I disabled autocorrect early on and never looked back. For convenience I MAY sometimes use the suggested words.

But I prefer a regular keyboard. This doesn't make me a luddite or anything, mobile keyboards are objectively bad compared to regular keyboards.

So is it autocorrecting helo to hello?

Predictive tweaks aren't good in a keyboard, you want everything to be intentional, or you'll lose time and patience correcting things. Spellcheck should be post hoc imho.

>Predictive tweaks aren't good in a keyboard, you want everything to be intentional, or you'll lose time and patience correcting things. Spellcheck should be post hoc imho.

Just depends on what kind of keyboard you're using and why. This is a very specialized keyboard for specialized tasks. I could see lots of different kinds of activities and roles it could be extremely useful for.

For programming, you probably wouldn't want it... though maybe some percentage of programmers who feel their brain moves a lot faster than their fingers might like it. Combined with stuff like Tabnine and Copilot, you hypothetically might eventually be able to "predictive-program" at an incredibly high speed. You'd inevitably have to spend some time revising bad predictions afterwards, but the total amount of time spent developing could decrease by a lot.

I don't even care if this is an ad. If it is, it worked and is the first and only ad I've appreciated. I've never impulse bought anything, but I'm buying this thing right now* after spending 10 seconds looking at it. (I used to spend a lot of time on online typing competition sites, so I'm closer to the target demographic.) My only concern is how much it might affect my normal typing muscle memory.

*As soon as it becomes available. Seems to be sold out, unsurprisingly.

No--the chord for hello is h+e+l+o--if you mean to type helo, you'd use a different chord you have setup for that or type it letter by letter

Ahh, having the option for single entry in combination with word chording makes a difference. I think I'm going to give it a go, this product looks interesting.

I tested that by turning off Apple's autocorrect on my Mac. It turns out I'm a less accurate typist than I thought. Now, I'm happy to let autocorrect put right all "teh" mistakes I make. It's annoying when I want to type something unusual, but that happens less often than I make mistakes, so the balance is in autocorrect's favour.

My goodness, I turned that off under a minute after I discovered that the "feature" existed. Autocorrect is for onscreen keyboards. I am a far more accurate typist than my computer gives me credit for.

It's a nightmare if you're writing in two different languages at the same time, eg. French sentence with English words in it. I often have to disable one or the other and live with most words being red underlined, because autocorrects are just not great at guessing what language I'm using.

BTW, if anyone from Alexa, Apple or Google is reading this, please have someone work on this. It's been 10 years since I've been using it, and neither speech recognition, nor autocorrect have made any kind of progress on the dual language stack.

Google has multiple language mode which works with Google keyboard and Chrome. I type in English and French on the regular at it auto corrects each properly even when mixed (Google keyboard on Android will even complete suggestions properly when mixing languages).

I'm using Google's keyboard on Android in dual language mode, it works pretty decent.

I use the same, it's mostly okay except when I mistype an English word that happens to be a word in French and the keyboard decides to correct the next few words to French.

Also amusing is that autocorrect, even while in English mode, suggests the bear emoji when I type "ours" or the cat when I type "chat".

The 76% was from his competition score. It's a measure of the keyboards actual output, not the error rate of the typist. Any corrections the keyboard makes are already accounted for.

Not if multi-step words are handled by writing the wrong thing first, then deleting and replacing it when the second set of inputs comes in. Which is a very common strategy for implementing chorded keyboards.

I actively worked to remove my oh I typed that wrong reflex. Because I need to ready anything important again and I'll click the squiggles. Everything else dosent mattr enughf for me to kare. Or I use with Google voice dictation and just deal with the craziness.

Dictated not red

I can't tell if this is poorly typed as a joke.

Perfect

I know someone who makes tons of typos in their regular text, they don't seem to use autocorrect, and it's fucking annoying to try and read what they post. It's common typos like jsut instead of just. They just seem too lazy or indifferent to fix their shit.

You bring it up to them?

My main issue is when I type on the phone the text area is so small it scrolls out of view and the autocorrect puts the wrong stuff all the time. So I actually use voice to text a lot which gives you crazy phonetic sentences that end up being like weird poetry or GPT3 sometimes.

Some people said it was hard to read. So I now set the expectation that hey I'm out for a hike, so I'm not going to type. We can either do a phone call, we can do this later, or you can deal with the phonetic oddities. Usually people opt for the oddities.

That being said I notice my own mistakes much less when I'm in a slack type back and forth convo, I'm optimizing for speed not correctness. Whereas here I'm on a desktop on a 4k monitor with a text box the size of a google doc and taking my time.

When it comes to natural language (as opposed to code) I wonder what the optimal error rate is. Autocorrect fixes some issues, so it's not 0 errors.

It also introduces some, so it just might even out.