Commentary

Google Can't Tell The Difference Between 'iPhone' And 'Sex'

This is a stitch. British users of Google's new voice-powered search application are finding that the software isn't quite ready for prime-time. The issue? It can't understand the British accent. The outcome? Searches for "iPhone" are returning results for "sex" instead. Um, oops.

This is a stitch. British users of Google's new voice-powered search application are finding that the software isn't quite ready for prime-time. The issue? It can't understand the British accent. The outcome? Searches for "iPhone" are returning results for "sex" instead. Um, oops.The U.K.'s Daily Telegraph reported the issue yesterday. According to readers of the Telegraph, the new Google search application isn't understanding their voice searches. Users of the application are finding that if they fake an American accent, they get better results.

Edward Parsons, an iPhone user in the U.K., said of the search app, "It actually works pretty well, but I have to disguise my (North London) accent with a terrible folksy Texan tourist voice to get results. I can see this is going to be the source of much amusement and confusion."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That's hysterical. I'd really like to hear a person from England fake a Texas accent. What I want to know is, how well does faking an accent from Brooklyn work?

Some of the mistaken results turned up after a search for "iPhone" include "sex", "kitchen sink", and "Einstein" reports the Telegraph. The Telegraph also reported that a user from Scotland was taken to a porn site after performing a search for "iPhone".

Sounds like the software that Google is using to translate speech into text isn't very worldly.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links