<?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: Interface Elements for Providing Feeds and Having People Subscribe to Them</title>
	<atom:link href="http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/</link>
	<description>A Blog about Social Web Design</description>
	<pubDate>Sat, 30 Aug 2008 05:36:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Josh</title>
		<link>http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-1257</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 28 Jul 2005 13:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-1257</guid>
		<description>Good to know, Marilyn. Sign up is definitely another alternative. I wonder, can we come up with some sort of test for this stuff? Has anyone tested various alternatives and seen which have what effects?</description>
		<content:encoded><![CDATA[<p>Good to know, Marilyn. Sign up is definitely another alternative. I wonder, can we come up with some sort of test for this stuff? Has anyone tested various alternatives and seen which have what effects?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marilyn Langfeld</title>
		<link>http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-1256</link>
		<dc:creator>Marilyn Langfeld</dc:creator>
		<pubDate>Thu, 28 Jul 2005 11:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-1256</guid>
		<description>Hi Joshua,

After I read this post I decided to add a similar 'SUBSCRIBE' button to a site I'm redesigning, in lieu of RSS or XML. The client loved it, but her internal clients preferred 'SIGN UP' so that's what we're trying. They felt that SUBSCRIBE might incorrectly indicate there would be a subscription fee.

The site launches at the association's national convention in mid September, and we'll be watching users navigate it there. I'll get back to you with any feedback I get at that point.</description>
		<content:encoded><![CDATA[<p>Hi Joshua,</p>
<p>After I read this post I decided to add a similar &#8216;SUBSCRIBE&#8217; button to a site I&#8217;m redesigning, in lieu of RSS or XML. The client loved it, but her internal clients preferred &#8216;SIGN UP&#8217; so that&#8217;s what we&#8217;re trying. They felt that SUBSCRIBE might incorrectly indicate there would be a subscription fee.</p>
<p>The site launches at the association&#8217;s national convention in mid September, and we&#8217;ll be watching users navigate it there. I&#8217;ll get back to you with any feedback I get at that point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Miller</title>
		<link>http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-914</link>
		<dc:creator>Paul Miller</dc:creator>
		<pubDate>Fri, 08 Jul 2005 10:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-914</guid>
		<description>I agree wholeheartedly that a technology-neutral button such as your 'subscribe' is the way forward.  First, though, we need to crack the technology so that clicking the button really will - reliably - do just that, rather than return meaningless XML to the browser, throw up an error, or whatever. NetNewsWire running on Tiger copes pretty well now when a Safari user clicks on one of these things. That is not true with other software and operating systems.

And if we're seeking a term that makes sense to people, subscribe is definitely better than syndicate, but may put some people off clicking as (to my mind at least) it carries connotations of *payment* in from the physical world; you subscribe to a magazine. You PAY A SUBSCRIPTION to get the content.</description>
		<content:encoded><![CDATA[<p>I agree wholeheartedly that a technology-neutral button such as your &#8217;subscribe&#8217; is the way forward.  First, though, we need to crack the technology so that clicking the button really will - reliably - do just that, rather than return meaningless XML to the browser, throw up an error, or whatever. NetNewsWire running on Tiger copes pretty well now when a Safari user clicks on one of these things. That is not true with other software and operating systems.</p>
<p>And if we&#8217;re seeking a term that makes sense to people, subscribe is definitely better than syndicate, but may put some people off clicking as (to my mind at least) it carries connotations of *payment* in from the physical world; you subscribe to a magazine. You PAY A SUBSCRIPTION to get the content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kevin</title>
		<link>http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-909</link>
		<dc:creator>kevin</dc:creator>
		<pubDate>Thu, 07 Jul 2005 17:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-909</guid>
		<description>This works great, and I think is preferred in very specific instances. That said, there are times when it's necessary to let people know what &lt;em&gt;kind&lt;/em&gt; of content a link points to in (that it points to a feed and not a web page per se). Perhaps in the context of an application that indexes a number of different feeds ina a view that also contains links to hypertext docs. 

It seems like one-click icons for various online readers are also a necessary evil but I'm all for slapping those in an xsl-ified view of the feed.</description>
		<content:encoded><![CDATA[<p>This works great, and I think is preferred in very specific instances. That said, there are times when it&#8217;s necessary to let people know what <em>kind</em> of content a link points to in (that it points to a feed and not a web page per se). Perhaps in the context of an application that indexes a number of different feeds ina a view that also contains links to hypertext docs. </p>
<p>It seems like one-click icons for various online readers are also a necessary evil but I&#8217;m all for slapping those in an xsl-ified view of the feed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Wills</title>
		<link>http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-907</link>
		<dc:creator>Chris Wills</dc:creator>
		<pubDate>Thu, 07 Jul 2005 14:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/interface-elements-for-providing-feeds-and-having-people-subscribe-to-them/#comment-907</guid>
		<description>A subscribe button is the way to go. It has the most meaning to the greatest number of people. I've been using "RSS Feed" in a text format but will be changing this to a "subscribe" graphic soon. I've also found it useful to provide additional information to inexperienced RSS users to explain what RSS is about. I've done this on my site by using a small question mark graphic.</description>
		<content:encoded><![CDATA[<p>A subscribe button is the way to go. It has the most meaning to the greatest number of people. I&#8217;ve been using &#8220;RSS Feed&#8221; in a text format but will be changing this to a &#8220;subscribe&#8221; graphic soon. I&#8217;ve also found it useful to provide additional information to inexperienced RSS users to explain what RSS is about. I&#8217;ve done this on my site by using a small question mark graphic.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<div  style="display:none; width=0px; height=0px" >
</div>