<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: iPhone autocorrection error analysis</title>
	<atom:link href="https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/</link>
	<description>cognition, language, social systems; statistics, visualization, computation</description>
	<lastBuildDate>Tue, 25 Nov 2025 13:11:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: הזבל של הרווארד או של אפל?</title>
		<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/#comment-68144</link>
		<dc:creator>הזבל של הרווארד או של אפל?</dc:creator>
		<pubDate>Thu, 16 Jun 2011 08:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://brenocon.com/blog/?p=960#comment-68144</guid>
		<description><![CDATA[[...] מעלה על המוקד מנתח בקצרה את בודק האיות של אפל. זה מזכיר לי שלפני כשנה אפל [...]]]></description>
		<content:encoded><![CDATA[<p>[...] מעלה על המוקד מנתח בקצרה את בודק האיות של אפל. זה מזכיר לי שלפני כשנה אפל [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brendano</title>
		<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/#comment-64614</link>
		<dc:creator>brendano</dc:creator>
		<pubDate>Mon, 23 May 2011 03:32:48 +0000</pubDate>
		<guid isPermaLink="false">http://brenocon.com/blog/?p=960#comment-64614</guid>
		<description><![CDATA[gaussian model sounds totally awesome!!  seriously though, i bet if you train a p(char&#124;intent) model you&#039;ll end up getting a transition model that reconstructs the topology of the keyboard -- e.g. take the first two principal components and it might look like a qwerty keyboard. maybe.

ok screw big fancy LMs, the problem is just to look at a small amount of left context]]></description>
		<content:encoded><![CDATA[<p>gaussian model sounds totally awesome!!  seriously though, i bet if you train a p(char|intent) model you&#8217;ll end up getting a transition model that reconstructs the topology of the keyboard &#8212; e.g. take the first two principal components and it might look like a qwerty keyboard. maybe.</p>
<p>ok screw big fancy LMs, the problem is just to look at a small amount of left context</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yoav Goldberg</title>
		<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/#comment-64495</link>
		<dc:creator>Yoav Goldberg</dc:creator>
		<pubDate>Sat, 21 May 2011 21:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://brenocon.com/blog/?p=960#comment-64495</guid>
		<description><![CDATA[I don&#039;t think they actually need a huge LM.  I bet a 4gram letter-level LM could really go a long way.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t think they actually need a huge LM.  I bet a 4gram letter-level LM could really go a long way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aria Haghighi</title>
		<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/#comment-64465</link>
		<dc:creator>Aria Haghighi</dc:creator>
		<pubDate>Sat, 21 May 2011 13:32:52 +0000</pubDate>
		<guid isPermaLink="false">http://brenocon.com/blog/?p=960#comment-64465</guid>
		<description><![CDATA[I thought the iPhone did do a unigram  LM  character-by-character and this was modeled along with the coordinates of the touch on the keyboard as an observation modeled as  gaussian centered on the letter you &#039;intend&#039; to touch. 

The real problem with the iPhone keyboard are (1) It&#039;s not personalized at all. The unigram model is clearly some generic one. (2) As far as I can gather it&#039;s not looking at the past word at all, so you get no-grammatical predictions a lot. I think you want to condition on the last word regardless of what else you do.]]></description>
		<content:encoded><![CDATA[<p>I thought the iPhone did do a unigram  LM  character-by-character and this was modeled along with the coordinates of the touch on the keyboard as an observation modeled as  gaussian centered on the letter you &#8216;intend&#8217; to touch. </p>
<p>The real problem with the iPhone keyboard are (1) It&#8217;s not personalized at all. The unigram model is clearly some generic one. (2) As far as I can gather it&#8217;s not looking at the past word at all, so you get no-grammatical predictions a lot. I think you want to condition on the last word regardless of what else you do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brendano</title>
		<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/#comment-64460</link>
		<dc:creator>brendano</dc:creator>
		<pubDate>Sat, 21 May 2011 12:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://brenocon.com/blog/?p=960#comment-64460</guid>
		<description><![CDATA[Yeah, I bet Apple totally could do this.]]></description>
		<content:encoded><![CDATA[<p>Yeah, I bet Apple totally could do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrew m</title>
		<link>https://brenocon.com/blog/2011/05/iphone-autocorrection-error-analysis/#comment-64429</link>
		<dc:creator>andrew m</dc:creator>
		<pubDate>Sat, 21 May 2011 06:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://brenocon.com/blog/?p=960#comment-64429</guid>
		<description><![CDATA[from a technical standpoint, is there any reason why iphone autocorrect shouldn&#039;t be as good as google autocorrect?
on the most recent stack exchange podcast they talked about this -- apparently a good deal of the google autocorrect was built from people typing one thing, realizing they mis-typed, editing, then searching again.  google then interprets that as a correction event and records the change.  slick.

couldn&#039;t apple just do this times a billion?]]></description>
		<content:encoded><![CDATA[<p>from a technical standpoint, is there any reason why iphone autocorrect shouldn&#8217;t be as good as google autocorrect?<br />
on the most recent stack exchange podcast they talked about this &#8212; apparently a good deal of the google autocorrect was built from people typing one thing, realizing they mis-typed, editing, then searching again.  google then interprets that as a correction event and records the change.  slick.</p>
<p>couldn&#8217;t apple just do this times a billion?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.016 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2026-04-09 09:50:18 -->
