Man, gboard does that on android so much that I wound up installing and using heliboard. It kinda sucks but at least it doesn't "fix" your message after you type everything
This helps, but it's not nearly enough, thanks to the terrible (and continually declining) quality of predictive tap zone enlargement for keyboard keys.
This is actually a necessary feature for a touchscreen keyboard to feel usable, and it's been in iOS since day one. The problem is that it has gotten not only much worse over time at predicting which tap zones to enlarge, but it also feels more aggressive. For example, tapping the shift button on the iOS keyboard enlarges the Enter/Return key's touch area so much that I am unable to immediately tap the microphone icon to turn off dictation. If I've tapped shift, I need to then wait a second for the predictively-enlarged tap zone to shrink before I can turn off dictation.
I disagree that it's necessary and I wish I could disable it. They even have it enabled on iPads, which are a tad larger than the original iPhone, and which can be used with the official stylus.
"Necessary" was probably too strong a word. I'm definitely no expert so I can only offer anecdotes, but for the first ~decade of iOS, the keyboard felt amazing to use. I felt super fast and typing mistakes were rare. Now I feel like I'm constantly fighting the keyboard to type the letters I actually want to type.
Agree at this point that I would disable it (in its current state) if I could, but when it worked correctly it was a huge boon to typing.
Ok so it's not just me. I never had predictive text enabled but stopped being able to type easily when I switched from iPhone 5 to 12 mini. Thought I needed to get used to the new phone, but it's been years.
I wonder if it's an optimization for the monstrously large phones they make today, and on a reasonably sized phone such as my 12 mini it doesn't adapt well.
It's not random, setting the query string to a new value on every fetch is a cache busting technique - it's trying to prevent the browser from caching the page, presumably to increase bandwidth usage.
It's trying to prevent the server from caching the search. Thousands of different searches will cause high CPU load and the WordPress might decide to suspend the blog.
"However exactly you divide up the AI landscape, it is important to distinguish what I call AI-as-engineering from what I call AI-as-cognitive-science. AI-as-engineering isn’t particularly concerned with mimicking the precise way in which the human mind-brain does distinctively human things. The strategy of engineering machines that do things that are in some sense intelligent, even if they do what they do in their own way, is a perfectly fine way to pursue artificial intelligence. AI-as-cognitive science, on the other hand, takes as its primary goal that of understanding and perhaps reverse engineering the human mind.
[...]
One reason for my own skepticism is the fact that in recent years the AI landscape has come to be progressively more dominated by AI of the newfangled 'deep learning' variety [...] But if it’s really AI-as-cognitive science that you are interested in, it’s important not to lose sight of the fact that it may take a bit more than our cool new deep learning hammer to build a humanlike mind.
[...]
If I am right that there are many mysteries about the human mind that currently dominant approaches to AI are ill-equipped to help us solve, then to the extent that such approaches continue to dominate AI into the future, we are very unlikely to be inundated anytime soon with a race of thinking robots—at least not if we mean by “thinking” that peculiar thing that we humans do, done in precisely the way that we humans do it."
Yes, the concept is called "shut up and multiply". I estimate the content-blocking counter-measure has saved hundreds of man-years.
On the days I feel particularly nasty like Ellison's character The Ticktockman, I wish that the programmers and the product managers who are responsible for the enshittification get this time subtracted from their life.
The title here suggests they're watching you shop and entering items into a list as you go (which would be ridiculous). It seems to actually just be low-paid workers spot checking to ensure the "algorithm" got it right?
reply