<?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: RSS: The Ultimate Opt-In Solution</title>
	<atom:link href="http://www.forevergeek.com/2004/09/rss_the_ultimate_opt_in_solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.forevergeek.com/2004/09/rss_the_ultimate_opt_in_solution/</link>
	<description>Nerds are for Dorks</description>
	<lastBuildDate>Fri, 10 Feb 2012 21:04:07 +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: JC</title>
		<link>http://www.forevergeek.com/2004/09/rss_the_ultimate_opt_in_solution/#comment-2663</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Thu, 30 Sep 2004 23:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=808#comment-2663</guid>
		<description>I have to laugh a bit. Half our customers can&#039;t even comprehend &quot;click here if you have never used this system before&quot; and we had to remove the login box from the page and make them click the appropriate link before they can see the login box they need. Them... RSS?
But for the 2-3% of clueful RSS lovin&#039; people out there,  maybe it&#039;d work. You&#039;d have to teach the RSS reader to do HTTP post, since I don&#039;t think SSL helps much if the username and password are in the URL (could be wrong about that, but it would definitely make people uneasy seeing their passwords there); and of course you&#039;d have to deal with the fact that a goodly number of RSS readers are web-based and the websites they reside on are NOT SSL encrypted...

I can see it being a useful opt-in venue for non-secure things, if by useful you mean &quot;a way to keep them from sending me crap I don&#039;t want&quot; ... after all, the reason marketers hate opt-in so much is that almost no one would ever opt in, given the choice.

It&#039;s an idea though. What I think it&#039;d be FAR more useful for than bank statements, though, is things like CD and other interest rates. I may even bring that one up with my boss, it&#039;d be quite easy to implement.</description>
		<content:encoded><![CDATA[<p>I have to laugh a bit. Half our customers can&#8217;t even comprehend &#8220;click here if you have never used this system before&#8221; and we had to remove the login box from the page and make them click the appropriate link before they can see the login box they need. Them&#8230; RSS?<br />
But for the 2-3% of clueful RSS lovin&#8217; people out there,  maybe it&#8217;d work. You&#8217;d have to teach the RSS reader to do HTTP post, since I don&#8217;t think SSL helps much if the username and password are in the URL (could be wrong about that, but it would definitely make people uneasy seeing their passwords there); and of course you&#8217;d have to deal with the fact that a goodly number of RSS readers are web-based and the websites they reside on are NOT SSL encrypted&#8230;</p>
<p>I can see it being a useful opt-in venue for non-secure things, if by useful you mean &#8220;a way to keep them from sending me crap I don&#8217;t want&#8221; &#8230; after all, the reason marketers hate opt-in so much is that almost no one would ever opt in, given the choice.</p>
<p>It&#8217;s an idea though. What I think it&#8217;d be FAR more useful for than bank statements, though, is things like CD and other interest rates. I may even bring that one up with my boss, it&#8217;d be quite easy to implement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

