<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Farewell to the &#8216;@&#8217; &#8211; We Welcome the Meta Revolution</title>
	<atom:link href="http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/feed/" rel="self" type="application/rss+xml" />
	<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/</link>
	<description>My View of the Real-Time Web - Tech and Rants From Jesse Stay, The "Social" Geek</description>
	<lastBuildDate>Tue, 09 Mar 2010 02:59:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jessestay</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-14861</link>
		<dc:creator>jessestay</dc:creator>
		<pubDate>Tue, 31 Mar 2009 06:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-14861</guid>
		<description>I view SMS as just another UI.  With a proper meta backend, Twitter could&lt;br&gt;simply interpret the SMS text, parse out the @&#039;s and the #&#039;s and insert them&lt;br&gt;into the appropriate meta tag. This way focus could remain on the content,&lt;br&gt;and 140 characters wouldn&#039;t be affected by the person in the Tweet or what&lt;br&gt;the Tweet is being tagged with.</description>
		<content:encoded><![CDATA[<p>I view SMS as just another UI.  With a proper meta backend, Twitter could<br />simply interpret the SMS text, parse out the @&#39;s and the #&#39;s and insert them<br />into the appropriate meta tag. This way focus could remain on the content,<br />and 140 characters wouldn&#39;t be affected by the person in the Tweet or what<br />the Tweet is being tagged with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mclaughj</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-14862</link>
		<dc:creator>mclaughj</dc:creator>
		<pubDate>Tue, 31 Mar 2009 06:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-14862</guid>
		<description>I have been with you on not including meta information in the 140 character limit since the very beginning and I think the points you make in this post are valid and very applicable. &lt;br&gt;&lt;br&gt;If I could &#039;spend&#039; my entire 140 characters on a comment I had on a blog post, and then include the &quot;reading:http://url.com&quot; meta tag for example, I think it would be much more powerful.&lt;br&gt;&lt;br&gt;But, as you mentioned on Twitter, it&#039;s not likely that Twitter will implement anything like this soon.</description>
		<content:encoded><![CDATA[<p>I have been with you on not including meta information in the 140 character limit since the very beginning and I think the points you make in this post are valid and very applicable. </p>
<p>If I could &#39;spend&#39; my entire 140 characters on a comment I had on a blog post, and then include the &#8220;reading:http://url.com&#8221; meta tag for example, I think it would be much more powerful.</p>
<p>But, as you mentioned on Twitter, it&#39;s not likely that Twitter will implement anything like this soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessestay</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-11226</link>
		<dc:creator>jessestay</dc:creator>
		<pubDate>Tue, 31 Mar 2009 02:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-11226</guid>
		<description>I view SMS as just another UI.  With a proper meta backend, Twitter could&lt;br&gt;simply interpret the SMS text, parse out the @&#039;s and the #&#039;s and insert them&lt;br&gt;into the appropriate meta tag. This way focus could remain on the content,&lt;br&gt;and 140 characters wouldn&#039;t be affected by the person in the Tweet or what&lt;br&gt;the Tweet is being tagged with.</description>
		<content:encoded><![CDATA[<p>I view SMS as just another UI.  With a proper meta backend, Twitter could<br />simply interpret the SMS text, parse out the @&#39;s and the #&#39;s and insert them<br />into the appropriate meta tag. This way focus could remain on the content,<br />and 140 characters wouldn&#39;t be affected by the person in the Tweet or what<br />the Tweet is being tagged with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mclaughj</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-11225</link>
		<dc:creator>mclaughj</dc:creator>
		<pubDate>Tue, 31 Mar 2009 02:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-11225</guid>
		<description>I have been with you on not including meta information in the 140 character limit since the very beginning and I think the points you make in this post are valid and very applicable. &lt;br&gt;&lt;br&gt;If I could &#039;spend&#039; my entire 140 characters on a comment I had on a blog post, and then include the &quot;reading:http://url.com&quot; meta tag for example, I think it would be much more powerful.&lt;br&gt;&lt;br&gt;But, as you mentioned on Twitter, it&#039;s not likely that Twitter will implement anything like this soon.</description>
		<content:encoded><![CDATA[<p>I have been with you on not including meta information in the 140 character limit since the very beginning and I think the points you make in this post are valid and very applicable. </p>
<p>If I could &#39;spend&#39; my entire 140 characters on a comment I had on a blog post, and then include the &#8220;reading:http://url.com&#8221; meta tag for example, I think it would be much more powerful.</p>
<p>But, as you mentioned on Twitter, it&#39;s not likely that Twitter will implement anything like this soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bookmarks about Opinion</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-10900</link>
		<dc:creator>Bookmarks about Opinion</dc:creator>
		<pubDate>Sat, 03 Jan 2009 21:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-10900</guid>
		<description>[...] - bookmarked by 4 members originally found by bibliorat on 2008-12-08  Jesse Stay: Hash.png  http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/ - [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; bookmarked by 4 members originally found by bibliorat on 2008-12-08  Jesse Stay: Hash.png  <a href="http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/" rel="nofollow" >http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/</a> &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Paul Weber</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-10311</link>
		<dc:creator>Stephen Paul Weber</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-10311</guid>
		<description>I don&#039;t think this in broken - but by design.  If you want to be sure someone gets a message (and you don&#039;t know their reading habits) txt/dm them or something.  @ is good for unambiguous mentions of names, and easy replying (which can be invisibly turned into data, but typing the @ is still a nice UI)</description>
		<content:encoded><![CDATA[<p>I don&#39;t think this in broken &#8211; but by design.  If you want to be sure someone gets a message (and you don&#39;t know their reading habits) txt/dm them or something.  @ is good for unambiguous mentions of names, and easy replying (which can be invisibly turned into data, but typing the @ is still a nice UI)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessestay</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-10082</link>
		<dc:creator>jessestay</dc:creator>
		<pubDate>Tue, 19 Aug 2008 14:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-10082</guid>
		<description>I recognize that, and I know SMS is a protocol - it&#039;s a great protocol  &lt;br&gt;in fact that has some great uses.  However, at the end of every SMS  &lt;br&gt;request (on the server) is a client that can parse SMS requests.  Just  &lt;br&gt;as I mention it could easily parse out all @addresses and #hashtags,  &lt;br&gt;and leave the body of the message so only pure content is left and the  &lt;br&gt;remainder is sent as meta information back to the microblog service.   &lt;br&gt;SMS should be treated like any other client, just as XMPP would be  &lt;br&gt;treated as well.</description>
		<content:encoded><![CDATA[<p>I recognize that, and I know SMS is a protocol &#8211; it&#39;s a great protocol  &lt;br&gt;in fact that has some great uses.  However, at the end of every SMS  &lt;br&gt;request (on the server) is a client that can parse SMS requests.  Just  &lt;br&gt;as I mention it could easily parse out all @addresses and #hashtags,  &lt;br&gt;and leave the body of the message so only pure content is left and the  &lt;br&gt;remainder is sent as meta information back to the microblog service.   &lt;br&gt;SMS should be treated like any other client, just as XMPP would be  &lt;br&gt;treated as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessestay</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-10083</link>
		<dc:creator>jessestay</dc:creator>
		<pubDate>Tue, 19 Aug 2008 14:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-10083</guid>
		<description>I recognize that, and I know SMS is a protocol - it&#039;s a great protocol  &lt;br&gt;in fact that has some great uses.  However, at the end of every SMS  &lt;br&gt;request (on the server) is a client that can parse SMS requests.  Just  &lt;br&gt;as I mention it could easily parse out all @addresses and #hashtags,  &lt;br&gt;and leave the body of the message so only pure content is left and the  &lt;br&gt;remainder is sent as meta information back to the microblog service.   &lt;br&gt;SMS should be treated like any other client, just as XMPP would be  &lt;br&gt;treated as well.</description>
		<content:encoded><![CDATA[<p>I recognize that, and I know SMS is a protocol &#8211; it&#39;s a great protocol  &lt;br&gt;in fact that has some great uses.  However, at the end of every SMS  &lt;br&gt;request (on the server) is a client that can parse SMS requests.  Just  &lt;br&gt;as I mention it could easily parse out all @addresses and #hashtags,  &lt;br&gt;and leave the body of the message so only pure content is left and the  &lt;br&gt;remainder is sent as meta information back to the microblog service.   &lt;br&gt;SMS should be treated like any other client, just as XMPP would be  &lt;br&gt;treated as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marjolein Katsma</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-10081</link>
		<dc:creator>Marjolein Katsma</dc:creator>
		<pubDate>Tue, 19 Aug 2008 08:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-10081</guid>
		<description>SMS is a protocol - there&#039;s no such thing as an &quot;SMS client&quot; that could do something like &quot;parsing&quot;. all there is is a field to enter a message in and a way to send it on its way.&lt;br&gt;&lt;br&gt;All semantics needs to be inside that message - and remain there. And the same applies to any context where a message can be posted that is not a &quot;microblogging client&quot;.</description>
		<content:encoded><![CDATA[<p>SMS is a protocol &#8211; there&#39;s no such thing as an &quot;SMS client&quot; that could do something like &quot;parsing&quot;. all there is is a field to enter a message in and a way to send it on its way.&lt;br&gt;&lt;br&gt;All semantics needs to be inside that message &#8211; and remain there. And the same applies to any context where a message can be posted that is not a &quot;microblogging client&quot;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jessestay</title>
		<link>http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/comment-page-1/#comment-10085</link>
		<dc:creator>jessestay</dc:creator>
		<pubDate>Tue, 19 Aug 2008 08:36:08 +0000</pubDate>
		<guid isPermaLink="false">http://staynalive.com/articles/2008/08/18/farewell-to-the-we-welcome-the-meta-revolution/#comment-10085</guid>
		<description>You and I will simply have to agree to disagree on this one.  I&#039;ve  &lt;br&gt;stated my points.</description>
		<content:encoded><![CDATA[<p>You and I will simply have to agree to disagree on this one.  I&#39;ve  &lt;br&gt;stated my points.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
