<?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/"
		>
<channel>
	<title>Comments on: LinkedIn Status &#8211;</title>
	<atom:link href="http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/feed/" rel="self" type="application/rss+xml" />
	<link>http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/</link>
	<description>the blog behind the book</description>
	<lastBuildDate>Fri, 30 Jul 2010 23:44:45 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jon Czerwinski</title>
		<link>http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/comment-page-1/#comment-283</link>
		<dc:creator>Jon Czerwinski</dc:creator>
		<pubDate>Wed, 19 Mar 2008 14:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/#comment-283</guid>
		<description>Ahhh... usability issues raise their ugly head.

I thought to test the length of the status entry.  So I kept typing until the entry field wouldn&#039;t take any more characters - an indication of a limit.  Hit save and get the error message:

&quot;Your status text exceeded the maximum length&quot;

The page source show the entry field to be 150 characters long.  I just tested with 143 characters and still get the error.

This is a example of poor user interface design - the maximum allowable is some value less than the entry field length, yet there&#039;s no indication what that maximum is or how many characters I have left to enter.</description>
		<content:encoded><![CDATA[<p>Ahhh&#8230; usability issues raise their ugly head.</p>
<p>I thought to test the length of the status entry.  So I kept typing until the entry field wouldn&#8217;t take any more characters &#8211; an indication of a limit.  Hit save and get the error message:</p>
<p>&#8220;Your status text exceeded the maximum length&#8221;</p>
<p>The page source show the entry field to be 150 characters long.  I just tested with 143 characters and still get the error.</p>
<p>This is a example of poor user interface design &#8211; the maximum allowable is some value less than the entry field length, yet there&#8217;s no indication what that maximum is or how many characters I have left to enter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Alba</title>
		<link>http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/comment-page-1/#comment-282</link>
		<dc:creator>Jason Alba</dc:creator>
		<pubDate>Wed, 19 Mar 2008 14:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/#comment-282</guid>
		<description>@Jon - that&#039;s pretty funny!  I&#039;m continually amazed (I know, I shouldn&#039;t be) at who is actually reading stuff I&#039;m doing online - whether it&#039;s Facebook, Twitter, my blogs, LinkedIn, etc.  

We are being watched :)</description>
		<content:encoded><![CDATA[<p>@Jon &#8211; that&#8217;s pretty funny!  I&#8217;m continually amazed (I know, I shouldn&#8217;t be) at who is actually reading stuff I&#8217;m doing online &#8211; whether it&#8217;s Facebook, Twitter, my blogs, LinkedIn, etc.  </p>
<p>We are being watched <img src='http://imonlinkedinnowwhat.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Czerwinski</title>
		<link>http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/comment-page-1/#comment-280</link>
		<dc:creator>Jon Czerwinski</dc:creator>
		<pubDate>Wed, 19 Mar 2008 12:18:17 +0000</pubDate>
		<guid isPermaLink="false">http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/#comment-280</guid>
		<description>It&#039;s been interesting so far in just the three days (and two statuses) I&#039;ve had.

I walked into a client yesterday who said she had just been browsing LinkedIn the day before and saw my status &quot;fixing yet another thing he&#039;s never seen before&quot; and was curious about what it was I had encountered...</description>
		<content:encoded><![CDATA[<p>It&#8217;s been interesting so far in just the three days (and two statuses) I&#8217;ve had.</p>
<p>I walked into a client yesterday who said she had just been browsing LinkedIn the day before and saw my status &#8220;fixing yet another thing he&#8217;s never seen before&#8221; and was curious about what it was I had encountered&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Alba</title>
		<link>http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/comment-page-1/#comment-268</link>
		<dc:creator>Jason Alba</dc:creator>
		<pubDate>Mon, 17 Mar 2008 19:09:46 +0000</pubDate>
		<guid isPermaLink="false">http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/#comment-268</guid>
		<description>interesting thing happened to me... I posted that status and a few days later ... IT WAS GONE!  

I don&#039;t know if everyone has a limit on their status, which would suck (imho), or if LI didn&#039;t like my status.</description>
		<content:encoded><![CDATA[<p>interesting thing happened to me&#8230; I posted that status and a few days later &#8230; IT WAS GONE!  </p>
<p>I don&#8217;t know if everyone has a limit on their status, which would suck (imho), or if LI didn&#8217;t like my status.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jen</title>
		<link>http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/comment-page-1/#comment-267</link>
		<dc:creator>Jen</dc:creator>
		<pubDate>Mon, 17 Mar 2008 19:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://imonlinkedinnowwhat.com/2008/03/03/linkedin-status/#comment-267</guid>
		<description>I&#039;m divided on this new feature. You know what they say: one bad apple spoils the whole bunch.

And there is one person in my large network who insists on posting pompous, over-the-top self-promoting messages.

So to avoid this person&#039;s daily status updates, I&#039;ve had to turn this feature off.</description>
		<content:encoded><![CDATA[<p>I&#8217;m divided on this new feature. You know what they say: one bad apple spoils the whole bunch.</p>
<p>And there is one person in my large network who insists on posting pompous, over-the-top self-promoting messages.</p>
<p>So to avoid this person&#8217;s daily status updates, I&#8217;ve had to turn this feature off.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
