Light Reading Mobile – Telecom News, Analysis, Events, and Research

5:35 PM --Siri! The Pig and Whistle ... The PIG AND WHISTLE!

This shouted phrase startled me out of fumbling with closing the door on our office building as I left here late one night recently. There were a couple of people nearby yelling into their iPhones for directions to a nearby bar.

Now, West 35th Street in Midtown Manhattan is one of a diminishing number of places on the island where it is definitely wise to be more than a bit cautious with brandishing expensive devices after dark. Particularly when drawing attention to yourself as a tourist by bawling at digital voice assistant for directions.

So, I went over and told them they were off a block for The Pig and Whistle and sent them out into the night.

I wasn't surprised when I saw that Lookout Labs projects that lost and stolen phones could cost users up to $30 billion in 2012. Particularly as devices like the iPhone and the iPad are both so iconic and recognizable to friends and thieves alike.

But I've been pondering how device makers, app developers and users all often seem to act as if we live in a utopian playground where bad things never happen. And what, if anything, we can do about it.

It is clearly not a good idea to yell at -- or pore over -- your device if you're not sure of the area. Use a headset instead (and I'm sure that swapping out those oh-so-recognizable white ear-buds is a good plan, too).

Is it also possible that some of these voice-recognition technologies could help with phone security soon? I mean, if Siri is already collecting so much info about its master's voice, wouldn't one option be to put a lock on the iPhone when the assistant doesn't recognize who is giving it commands?

— Dan Jones, Site Editor, Light Reading Mobile

5:35 PM Can developers, device providers and users do something more to prevent the rising tide of smartphone crime?
March 23, 2012 | Dan Jones |


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

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing 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. Network Computing 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.
 
Related Videos
White Papers SPONSORED CONTENT
Featured
Orthogonal Frequency Division Multiplexing (OFDM)
A modulation scheme where one high-speed signal is split into multiple lower-speed signals