<?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"
	>
<channel>
	<title>Comments on: Celebrating Text</title>
	<atom:link href="http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/</link>
	<description>Adaptive Path Blog</description>
	<pubDate>Mon, 08 Sep 2008 00:56:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Daniel Szuc</title>
		<link>http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-52520</link>
		<dc:creator>Daniel Szuc</dc:creator>
		<pubDate>Sun, 04 Mar 2007 01:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-52520</guid>
		<description>"Experts have also noted how different types of technology have developed their own etiquette.

For instance, an e-mail can wait two days to be answered but a text message demands an almost immediate reply." - 

http://news.bbc.co.uk/1/hi/programmes/click_online/6411495.stm</description>
		<content:encoded><![CDATA[<p>&#8220;Experts have also noted how different types of technology have developed their own etiquette.</p>
<p>For instance, an e-mail can wait two days to be answered but a text message demands an almost immediate reply.&#8221; - </p>
<p><a href="http://news.bbc.co.uk/1/hi/programmes/click_online/6411495.stm" rel="nofollow">http://news.bbc.co.uk/1/hi/programmes/click_online/6411495.stm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart</title>
		<link>http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-46182</link>
		<dc:creator>Bart</dc:creator>
		<pubDate>Mon, 12 Feb 2007 15:50:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-46182</guid>
		<description>Here's an interesting story run by CNN on &lt;a href="http://www.cnn.com/2007/TECH/02/09/chat.lingo.ap/index.html" rel="nofollow"&gt;IM text appearing within assignments&lt;/a&gt;.

&lt;blockquote&gt;This "instant messaging-speak" or "IM-speak" emerged more than a decade ago. Used in e-mail and cell phone text messages, most teens are familiar with this tech talk and use it to flirt, plan dates and gossip.

But junior high and high school teachers nationwide say they see a troubling trend: The words have become so commonplace in children's social lives that the techno spellings are finding their way into essays and other writing assignments.&lt;/blockquote&gt;

This reinforces the idea that niche text [a la IM and SMS] is infiltrating our lexicon most significantly.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s an interesting story run by CNN on <a href="http://www.cnn.com/2007/TECH/02/09/chat.lingo.ap/index.html" rel="nofollow">IM text appearing within assignments</a>.</p>
<blockquote><p>This &#8220;instant messaging-speak&#8221; or &#8220;IM-speak&#8221; emerged more than a decade ago. Used in e-mail and cell phone text messages, most teens are familiar with this tech talk and use it to flirt, plan dates and gossip.</p>
<p>But junior high and high school teachers nationwide say they see a troubling trend: The words have become so commonplace in children&#8217;s social lives that the techno spellings are finding their way into essays and other writing assignments.</p></blockquote>
<p>This reinforces the idea that niche text [a la IM and SMS] is infiltrating our lexicon most significantly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leith @ Birth of a Startup</title>
		<link>http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-44010</link>
		<dc:creator>Leith @ Birth of a Startup</dc:creator>
		<pubDate>Wed, 07 Feb 2007 01:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-44010</guid>
		<description>I think we used to care more about abbreviated words for text messaging in its early days when we had a firm character limit per message and the cost for sending text messages was worth considering, and it was a new form of data input that often took a long time to carry out. I find now that its possible to send long text messages easily, and I don't care overly about the cost of text messages, and that I can type long text messages in seconds, means I now am quite verbose in my text messaging, or at least I avoid overuse of acronyms. The only acronyms I still frequently use is 'ur', 'r' and '2moro', but I find with predictive text input, it is often easier to write the full word than to attempt to shorten it. I for one am happy to be an advocate for proper English grammar and spelling, and am happy that the environment is conducive to see it have a come-back!</description>
		<content:encoded><![CDATA[<p>I think we used to care more about abbreviated words for text messaging in its early days when we had a firm character limit per message and the cost for sending text messages was worth considering, and it was a new form of data input that often took a long time to carry out. I find now that its possible to send long text messages easily, and I don&#8217;t care overly about the cost of text messages, and that I can type long text messages in seconds, means I now am quite verbose in my text messaging, or at least I avoid overuse of acronyms. The only acronyms I still frequently use is &#8216;ur&#8217;, &#8216;r&#8217; and &#8216;2moro&#8217;, but I find with predictive text input, it is often easier to write the full word than to attempt to shorten it. I for one am happy to be an advocate for proper English grammar and spelling, and am happy that the environment is conducive to see it have a come-back!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart Solowiej</title>
		<link>http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-43947</link>
		<dc:creator>Bart Solowiej</dc:creator>
		<pubDate>Tue, 06 Feb 2007 22:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/02/06/celebrating-text/#comment-43947</guid>
		<description>I apologize for what will manifest itself as a shameless self promotion by its close.

SMS offers a terse, direct, greatest common denominator approach to extrapolating information from sources within the greater aggregate.  In English, big apps that do BIG things [index the web, catalog film schedules, products, prices, weather, transit timetables].

I wake in the morning and text 'W 20005' to GOOGL and "Dupont" to dc@traincheck.com on my phone. I brush my teeth, wash up, etc etc, while my phone digs up how cold it is outside and when the next three trains arrive at the Dupont Circle Metro station in DC.  I speak to apps using this terse uber geek lingo, each with its own niche format.

The *niche text* subclass reflects the frenetic "I don't-have-time-to-explain" lifestyle more of us are leading in a hyper competitive world. It will be interesting to see how many "standardizations" of SMS niche text arise with the increasing prevalence of text-based mobile communication.

Are we just shortening our lexicon along with the scope of our immediate interests and attention spans?  Would that explain the evolution of "I'll see you later"?

See ya later. -&#62; Later. and See ya. -&#62; C u l8r and l8r -&#62;lates, late, L8s, L8  A myriad of examples exists...

Although I can type the full station name of any station in DC, SF, or Caltrain into traincheck, I as developer and my partner, a designer, made sure we could type in 3 letter codes to get unambiguous result sets in any metro we model (Much like airport codes).  We knew when we did it that this would be awkward for people new to TrainCheck, but not to our content. And people ending up  adopting the short station codes once familiarized with the system.

Niche text is the future of mobile information gathering, allowing us to ask more and get more with less cruft.</description>
		<content:encoded><![CDATA[<p>I apologize for what will manifest itself as a shameless self promotion by its close.</p>
<p>SMS offers a terse, direct, greatest common denominator approach to extrapolating information from sources within the greater aggregate.  In English, big apps that do BIG things [index the web, catalog film schedules, products, prices, weather, transit timetables].</p>
<p>I wake in the morning and text &#8216;W 20005&#8242; to GOOGL and &#8220;Dupont&#8221; to <a href="mailto:dc@traincheck.com">dc@traincheck.com</a> on my phone. I brush my teeth, wash up, etc etc, while my phone digs up how cold it is outside and when the next three trains arrive at the Dupont Circle Metro station in DC.  I speak to apps using this terse uber geek lingo, each with its own niche format.</p>
<p>The *niche text* subclass reflects the frenetic &#8220;I don&#8217;t-have-time-to-explain&#8221; lifestyle more of us are leading in a hyper competitive world. It will be interesting to see how many &#8220;standardizations&#8221; of SMS niche text arise with the increasing prevalence of text-based mobile communication.</p>
<p>Are we just shortening our lexicon along with the scope of our immediate interests and attention spans?  Would that explain the evolution of &#8220;I&#8217;ll see you later&#8221;?</p>
<p>See ya later. -&gt; Later. and See ya. -&gt; C u l8r and l8r -&gt;lates, late, L8s, L8  A myriad of examples exists&#8230;</p>
<p>Although I can type the full station name of any station in DC, SF, or Caltrain into traincheck, I as developer and my partner, a designer, made sure we could type in 3 letter codes to get unambiguous result sets in any metro we model (Much like airport codes).  We knew when we did it that this would be awkward for people new to TrainCheck, but not to our content. And people ending up  adopting the short station codes once familiarized with the system.</p>
<p>Niche text is the future of mobile information gathering, allowing us to ask more and get more with less cruft.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
