Commentary

Dave Methvin
 

Just Make It Sound Good

People love a good rumor. Since we're in the technology business, juicy stories about Lindsay Lohan, LeBron James, or Lady Ga Ga don't quite fit in. That doesn't stop some tech stories from repeating things that seem just as crazy, and are totally unsupported by any facts.

People love a good rumor. Since we're in the technology business, juicy stories about Lindsay Lohan, LeBron James, or Lady Ga Ga don't quite fit in. That doesn't stop some tech stories from repeating things that seem just as crazy, and are totally unsupported by any facts.Let's pick a couple of things from the past week. One is the rumor that Kin sold only 503 phones. That's a really crazy-small number -- even for a failed phone with just a six-week lifespan. There is no named source for this rumor. Yet like any good rumor, it's so sensational that dozens of people pick it up and repeat it over and over and over and over again. One prominent source I could find that didn't bite was the New York Times, which stuck to a "fewer than 10,000" line.

So is there any way to figure out whether 503 could be a real sales number? Lacking some data from either Microsoft or Verizon, we probably won't know an official number. But there could certainly be some data points that could confirm or conflict with that number. The folks over at PocketNow.com posited a pretty simple check using the Kin's Facebook app, and comes up with a number just south of 9,000. Their logic seems reasonable: Kin's Facebook app is only available to Kin users, and thus this count should be close to the number of registered Kin users. Even if you were to assume a couple of thousand testers, the Facebook app would indicate that sales are significantly higher than 503. This isn't to say Kin was a success, but only that the 503 rumor seems crazy, unfounded, and unsupported by other reasonable measures.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Here's a second example. This week a message was sent to a security mailing list describing some new Microsoft security exploits. That alone isn't new, but the additional information in the message said:

Due to hostility toward security researchers, the most recent example being of Tavis Ormandy, a number of us from the industry (and some not from the industry) have come together to form MSRC: the Microsoft-Spurned Researcher Collective. MSRC will fully disclose vulnerability information discovered in our free time, free from retaliation against us or any inferred employer.

Sounds pretty juicy, doesn't it? A group of somewhat-white-hat security professionals are circumventing the standard "responsible disclosure" process, supposedly because of Microsoft's antagonism towards them. So certainly the press will contact the members of this group and interview them about their ... oh wait a minute, there are no names in the message for obvious reasons. So we're not really sure at all if this "group" consists of more than one person. But that didn't stop several news sites from reporting about this "group" without once questioning whether it was a group at all. For all we know it's just one disgruntled guy. But that wouldn't sound as good, would it?


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