InformationWeek: The Business Value of Technology

InformationWeek: The Business Value of Technology
e2 Conference & Expo - Boston 2013
= Member Content
Facebook Twitter Share

E-mail | Print | Permalink | LinkedIn | RSS

SMS Text Messaging Has 20th Birthday Monday


Who invented texting? Who sent the first text and what did it say? Why 160 characters? These and more fun questions are answered on the occasion of the 20th anniversary of the first short message service (SMS) text message.


By Larry Seltzer
InformationWeek
November 30, 2012 12:47 PM

A lot has changed in the last 20 years, but not this technology: text messaging. Monday, Dec. 3, 2012 will be the 20th anniversary of the first SMS message.

Joel Willans on Conversations by Nokia has collected "10 astounding facts about the humble SMS." Here are teasers; read the full article for the fun details.

  1. Get the story of the father of SMS, Matti Makkonen, a Finnish engineer.
  2. Why just 160 characters?
  3. Who sent the first SMS, to whom did he send it, and what did it say? (Hint: It wasn't "1st txt evr.")
  4. How much texting is done today?
  5. How much does the telecom industry earn on texting?
  6. The dangers of texting while driving.
  7. Where did all those stupid abbreviations (BRB, LOL, etc) come from?
  8. All about "sexting."
  9. What is the record for the fastest ever text message?
  10. Did you know texting is the leading cause of tenosynovitis.

Personally, I think texting is inferior to email, but I seem to be in the minority.


Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).




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.
Subscribe to RSS


Advertisement

InformationWeek Reports

report Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.

report Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.

report Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.

report The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.