<?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: Plaxo to Throttle Back the Emails</title>
	<atom:link href="http://www.newsome.org/2006/03/plaxo-to-throttle-back-emails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newsome.org/2006/03/plaxo-to-throttle-back-emails/</link>
	<description>Kent Newsome on technology, music and life</description>
	<lastBuildDate>Sun, 05 Feb 2012 23:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Zoli Erdos</title>
		<link>http://www.newsome.org/2006/03/plaxo-to-throttle-back-emails/comment-page-1/#comment-4729</link>
		<dc:creator>Zoli Erdos</dc:creator>
		<pubDate>Thu, 23 Mar 2006 03:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=2843#comment-4729</guid>
		<description>Oops, I guess &quot;preview&quot; is not qute accurate on blogger:-(</description>
		<content:encoded><![CDATA[<p>Oops, I guess &#8220;preview&#8221; is not qute accurate on blogger:-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zoli Erdos</title>
		<link>http://www.newsome.org/2006/03/plaxo-to-throttle-back-emails/comment-page-1/#comment-4730</link>
		<dc:creator>Zoli Erdos</dc:creator>
		<pubDate>Thu, 23 Mar 2006 03:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=2843#comment-4730</guid>
		<description>Plaxo is an increadible useful service – when used properly.  I’ve always said that the &lt;a HREF=&quot;http://www.zoliblog.com/blog/_archives/2005/6/6/975578.html&quot; rel=&quot;nofollow&quot;&gt;“decent” way&lt;/A&gt; is to rely on the auto-updates only (which works between members), and don’t touch the mass-mailer facility.Kent, you’re not quoting the best part of the announcement:  “&lt;EM&gt;This feature will probably always exist in some form, but &lt;STRONG&gt;we are no longer aggressively pushing new users to send out e-mails&lt;/STRONG&gt; and are adding restrictions to prevent existing users from sending out large batches” &lt;/EM&gt;  Isn’t it just lovely, after all the denial they admit to have been “&lt;STRONG&gt;aggressively pushing&lt;/STRONG&gt;” us. Wow!Btw, they still don’t really have a business model, the premium offering is poor.  I tried it, lost 2 workdays recovering my data (this should be another looong post),  then Customer Service ignored my refund request (within the trial period) 3 times, finally an email to the CEO helped.But again, the auto-update feature is priceless (especially if you don’t migrate to new computers too often).</description>
		<content:encoded><![CDATA[<p>Plaxo is an increadible useful service – when used properly.  I’ve always said that the <a HREF="http://www.zoliblog.com/blog/_archives/2005/6/6/975578.html" rel="nofollow">“decent” way</a> is to rely on the auto-updates only (which works between members), and don’t touch the mass-mailer facility.Kent, you’re not quoting the best part of the announcement:  “<em>This feature will probably always exist in some form, but <strong>we are no longer aggressively pushing new users to send out e-mails</strong> and are adding restrictions to prevent existing users from sending out large batches” </em>  Isn’t it just lovely, after all the denial they admit to have been “<strong>aggressively pushing</strong>” us. Wow!Btw, they still don’t really have a business model, the premium offering is poor.  I tried it, lost 2 workdays recovering my data (this should be another looong post),  then Customer Service ignored my refund request (within the trial period) 3 times, finally an email to the CEO helped.But again, the auto-update feature is priceless (especially if you don’t migrate to new computers too often).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

