Why, during the year 2023, does iOS still autocorrect .com to .con?
One of my biggest pet peeves is the iPhone/iOS autocorrect constantly being wrong, and changing correct spelling to something else it "thinks" I'm trying to write.
The biggest offender has to be when I'm typing out web addresses in various apps. It constantly changes ".com" to ".con". It's mildly infuriating that we're on the precipice of going to Mars yet the iPhone doesn't know that web addresses end in .com
Can anyone shed light on why this issue is so hard? (the engineers at Apple are much smarter than me, so there must be a reason)
I'm the only one NOT using autocorrect? I find useful the suggestions that popup above the keyboard but ultimately I decide whether or not to use them. I find autocorrection (on phones) annoying.
Let me just hijack your thread to rant that I KNOW how to differentiate "it's" from "its" and I always use it correctly and Android insists on auto-correcting it to the wrong thing.
My favourite bizarre Apple AI thing is the dictation mode on OSX deciding that instead of an extremely common word like "for" that's pronounced as I've pronounced it in all dialects of English and fits perfectly in the context of the sentence, it's going to grab a surname from my address book that might start with an 'f' but isn't pronounced that way, and insert it into a phrase where a surname makes no sense. Especially when it gets it right first time, pauses and then swaps the name in after I finish the sentence.
Just turn off autocorrect. That's only for kids who can't spell for themselves.
I regularly text in 3 languages. The increase in autocorrect frustration is exponential, not linear.
Stuff like this is why I wish we solved low-hanging fruit AI before we tackled pie in the sky general intelligence.
How come autocorrect, geammarly, Google Assistant/Siri, google translate, etc. are still so bad?
Apple has an incentive to discourage web use to keep people in their app ecosystem, so it’s not inconceivable that small frustrations like that are just one of the ways they do it.
"com" => "con" doesn't do that for me, but I have all sorts of similar infuriatingly bad autocorrects happen. Eg. correcting common English words to made-up English looking words, for example, something like "Regular" to something like "Ruxuler".
I vaguely recall checking into this once and seeing some sort of LLM in iOS 17, so I chalk it up to LLM hallucinations.
These:
- Words are not something I've ever typed. I know, because iOS 17's AutoCorrect is so bad, I avoid typing on iOS as much as I can.
- Words are not under my replacement settings. Nobody is playing a gag on me.
- Don't change after deleting the local autocorrect caches in Settings.
iOS autocorrect is legitimately terrible.
I promise, there are zero circumstances under which I text "nm man u?" and intend to use a short form of "Manchester United"
(And unlike other ducking annoyances, this one cannot be worked around with text replacement shortcuts.)
Can one of those engineers or product managers on $300k+ not fix it or something?
The notorious dot-cons ;)