<?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: Bells and Whistles On Your Blog &#8211; A Good Idea?</title>
	<atom:link href="http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 09:18:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Markku Seguerra</title>
		<link>http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/comment-page-1/#comment-141448</link>
		<dc:creator>Markku Seguerra</dc:creator>
		<pubDate>Tue, 02 Jan 2007 11:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/#comment-141448</guid>
		<description>SPA can really be an annoyance if overdone. Having it available for wordpress.com users is good, because you are providing your users a choice, though I hope they have common sense to know if they really need it or not.</description>
		<content:encoded><![CDATA[<p>SPA can really be an annoyance if overdone. Having it available for wordpress.com users is good, because you are providing your users a choice, though I hope they have common sense to know if they really need it or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Knee</title>
		<link>http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/comment-page-1/#comment-140999</link>
		<dc:creator>Ron Knee</dc:creator>
		<pubDate>Mon, 01 Jan 2007 13:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/#comment-140999</guid>
		<description>I dug up one site last week with one of these &quot;snap&quot; widgets.  Every ruddy little thing I drifted my cursor over brought up a sodding box which obscured what I was reading, even when in desperation I went for the &quot;next blog&quot; button.  Aaaaargh!</description>
		<content:encoded><![CDATA[<p>I dug up one site last week with one of these &#8220;snap&#8221; widgets.  Every ruddy little thing I drifted my cursor over brought up a sodding box which obscured what I was reading, even when in desperation I went for the &#8220;next blog&#8221; button.  Aaaaargh!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle</title>
		<link>http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/comment-page-1/#comment-140462</link>
		<dc:creator>Lorelle</dc:creator>
		<pubDate>Sun, 31 Dec 2006 01:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/#comment-140462</guid>
		<description>I&#039;ve found only one good reason for using Snap Preview from the commenters on my article: If you have a site which features WordPress Themes, web designs, or other graphic and portfolio links, this makes sense. It gives people a preview of the graphic visual at the link&#039;s destination.

However, anyone who says that a visual image of the web page at the link&#039;s site will help them make &quot;an informed decision&quot; on whether or not they should visit the site is a person who makes snap judgments based upon looks not content. A preview of the page will not tell you if the page has the information you want or need. I&#039;ve found great information on ugly pages and ugly information on beautiful pages.

If the Snap Preview had a score card system to judge the quality of the content, then it would be something worth exploring. However, the way social bookmarking and networking works today, too many are experts at gaming such score cards. So how could I trust that information, either.

Another issue being overlooked a bit here is that Snap Preview is forced upon you. To not &quot;see&quot; it anywhere, you have to visit their site and opt-out. That&#039;s a nice option, but why should we bother. If the sites warned us they were using this, and gave us an option to see it or not, then that might work, but still, there are better ways to waste bandwidth, don&#039;t you think? ;-)

I believe something better will come of the Snap Preview technology as it is a great gimmick, but covering our content isn&#039;t the right use of this novel tool.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found only one good reason for using Snap Preview from the commenters on my article: If you have a site which features WordPress Themes, web designs, or other graphic and portfolio links, this makes sense. It gives people a preview of the graphic visual at the link&#8217;s destination.</p>
<p>However, anyone who says that a visual image of the web page at the link&#8217;s site will help them make &#8220;an informed decision&#8221; on whether or not they should visit the site is a person who makes snap judgments based upon looks not content. A preview of the page will not tell you if the page has the information you want or need. I&#8217;ve found great information on ugly pages and ugly information on beautiful pages.</p>
<p>If the Snap Preview had a score card system to judge the quality of the content, then it would be something worth exploring. However, the way social bookmarking and networking works today, too many are experts at gaming such score cards. So how could I trust that information, either.</p>
<p>Another issue being overlooked a bit here is that Snap Preview is forced upon you. To not &#8220;see&#8221; it anywhere, you have to visit their site and opt-out. That&#8217;s a nice option, but why should we bother. If the sites warned us they were using this, and gave us an option to see it or not, then that might work, but still, there are better ways to waste bandwidth, don&#8217;t you think? ;-)</p>
<p>I believe something better will come of the Snap Preview technology as it is a great gimmick, but covering our content isn&#8217;t the right use of this novel tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: franky</title>
		<link>http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/comment-page-1/#comment-140408</link>
		<dc:creator>franky</dc:creator>
		<pubDate>Sat, 30 Dec 2006 19:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2006/12/30/bells-and-whistles-on-your-blog-a-good-idea/#comment-140408</guid>
		<description>I have used Snap for some days on my blog, but then I removed it again. If you adhere to validity and accessibility, you will specify the attribute &lt;strong&gt;title=&lt;/strong&gt;, which if correctly used should inform the reader enough to decide if she/he wants to visit that site.</description>
		<content:encoded><![CDATA[<p>I have used Snap for some days on my blog, but then I removed it again. If you adhere to validity and accessibility, you will specify the attribute <strong>title=</strong>, which if correctly used should inform the reader enough to decide if she/he wants to visit that site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

