“Die In A Minute”: 125 Times Autocorrect Made A Mess From A Normal Text

For ages, people have tried to find ways around the simple fact that most people, professionals included, will repeatedly make spelling mistakes in anything they write. This is why editors, proofreaders, and entire software companies like Grammarly still exist. Let’s face it, often we are in a hurry when we need to write something and the result can be all the hilarity we can see here. 

The root of many of these issues, as well as better-publicized examples, comes from the simple problem of the spellchecker or autocorrect having an incomplete list of words. One of the most famous examples of this goes all the way back to at least 2007 when multiple people online noticed that many automated spellcheckers only knew the word "cooperation" when it was spelled without the hyphen. 

Older lists of words would only have “co-operation,” so when certain computers saw this word, they believed that it was simply a mistake. And for some reason, the “nearest” word to this mistake was “Cupertino,” the name of a town in California. The result was various, very official documents containing phrases like "South Asian Association for Regional Cupertino" and "presentation on African-German Cupertino".

To this day, this issue is referred to as the “Cupertino effect” which, simply put, is the often hilarious result of a spellchecker not having a word in its dictionary and making an “interesting” substitution. Other famous examples include Routers publishing an article where the "Muttahida Qaumi Movement" became the "Muttonhead Quail Movement." 

However, the “Cupertino effect” pales in comparison to the “Scunthorpe problem.” I’ll give you a moment to figure it out, it’s in the name. Long story short, the entire town of Scunthorpe struggled to create AOL accounts using their town's name because the site's filters kept detecting profanity. 

This issue is quite persistent, as lists of “banned words” are not static and constantly evolve. At the same time, this means more, unrelated words, like Scunthorpe, end up getting incorrectly flagged. The solution tends to be constant human intervention, something that spellcheck was invented to prevent. 

Other famous examples include shiitake mushrooms being misspelled, with a missing “i” and this word being marked as profanity. Fortunately, this particular instance has managed to rectify itself, as more people are familiar with the correct spelling of this Japanese word, as food blogging has taken off. 

Similarly, one Twitter (now X) user from Luxembourg, having just created an account, tweeted (an apt use for the verb) “Finally! A pair of great tits (Parus major) has moved into my birdhouse!” and had their account banned almost instantly. Interestingly, upon review, Twitter support declined to unban the account. 

However, our text messages tend to not fall under such scrutiny, so spellcheck still insists on ducks ducking all over the place, even when not a single bird is present. As always with fails (spellcheck insists on “failure” but we all know it’s something else,) it really depends on where you are sitting. When it happens to you, it’s a tragedy, but hysterical when it happens to someone else. 

More commonly, it’s not so much that we misspell words, but that we over-rely on predictive text. Often it’s great, allowing us to fill in simple emails in moments, to keep some momentum going when writing certain sentences. But if you get used to it, predictive text becomes a crutch, with the writer simply missing the mistakes or misplaced words it gives and leaving it in the text. 

Unfortunately, there is at least one instance where an autocorrect mistake ended up causing someone’s death when it changed “nutter” to “mutter” for one Lancashire man. While it’s unclear why this word would be so triggering, it instigated an argument that caused the recipient to attack the sender, leading to the former being stabbed in the heart.