<?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: How Wave Could Tackle the Spam Problem</title>
	<atom:link href="http://the.geekorium.com/how-wave-could-tackle-the-spam-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://the.geekorium.com/how-wave-could-tackle-the-spam-problem/</link>
	<description>Home of Rex Havoc, Space Adventurer and other assorted Geekeries.</description>
	<lastBuildDate>Thu, 03 May 2012 00:54:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>	<item>
		<title>By: joshnunn</title>
		<link>http://the.geekorium.com/how-wave-could-tackle-the-spam-problem/#comment-2283</link>
		<dc:creator>joshnunn</dc:creator>
		<pubDate>Thu, 15 Apr 2010 17:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477571#comment-2283</guid>
		<description>I mean that in comparison, email is almost no cost to the spammer, but in either of your examples, it will cost the spammer something - a spammer sending thousands of waves a second will need to keep copies like you say or they will just disappear. If they use free providers (which is I presume what you mean in the first example), the provider will hopefully have strict limits in place that will flag high levels of waving as possible abuse. Unlike email, once their account is suspended, the wave that was sent will be a lot easer to identify as spam by the recipient (now, once an email is sent, it&#039;s gone and suspending a spammer account makes no difference).</description>
		<content:encoded><![CDATA[<p>I mean that in comparison, email is almost no cost to the spammer, but in either of your examples, it will cost the spammer something — a spammer sending thousands of waves a second will need to keep copies like you say or they will just disappear. If they use free providers (which is I presume what you mean in the first example), the provider will hopefully have strict limits in place that will flag high levels of waving as possible abuse. Unlike email, once their account is suspended, the wave that was sent will be a lot easer to identify as spam by the recipient (now, once an email is sent, it’s gone and suspending a spammer account makes no difference).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael</title>
		<link>http://the.geekorium.com/how-wave-could-tackle-the-spam-problem/#comment-2282</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Thu, 15 Apr 2010 17:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477571#comment-2282</guid>
		<description>In point 2 of this article, you mention &quot;Hosting.&quot; What do you mean by this? Do you mean that the wave stays in that person&#039;s &quot;inbox/bin&quot; etc. indefinately, or are you referring to spammers setting up wave servers?&lt;br&gt;&lt;br&gt;If you mean that the wave stays in their account, then it does not solve spam, as the user can just register a new account once they are done.&lt;br&gt;&lt;br&gt;If you mean that spammers will host spam waves on their own servers, then this would stop them spamming completely, as that spam wave would be held on their server, and if they removed it from their server, no-one could access it.</description>
		<content:encoded><![CDATA[<p>In point 2 of this article, you mention “Hosting.” What do you mean by this? Do you mean that the wave stays in that person’s “inbox/bin” etc. indefinately, or are you referring to spammers setting up wave servers?</p>
<p>If you mean that the wave stays in their account, then it does not solve spam, as the user can just register a new account once they are done.</p>
<p>If you mean that spammers will host spam waves on their own servers, then this would stop them spamming completely, as that spam wave would be held on their server, and if they removed it from their server, no-one could access it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Screenbeard</title>
		<link>http://the.geekorium.com/how-wave-could-tackle-the-spam-problem/#comment-2285</link>
		<dc:creator>Screenbeard</dc:creator>
		<pubDate>Thu, 15 Apr 2010 12:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477571#comment-2285</guid>
		<description>I mean that in comparison, email is almost no cost to the spammer, but in either of your examples, it will cost the spammer something - a spammer sending thousands of waves a second will need to keep copies like you say or they will just disappear. If they use free providers (which is I presume what you mean in the first example), the provider will hopefully have strict limits in place that will flag high levels of waving as possible abuse. Unlike email, once their account is suspended, the wave that was sent will be a lot easer to identify as spam by the recipient (now, once an email is sent, it&#039;s gone and suspending a spammer account makes no difference).</description>
		<content:encoded><![CDATA[<p>I mean that in comparison, email is almost no cost to the spammer, but in either of your examples, it will cost the spammer something — a spammer sending thousands of waves a second will need to keep copies like you say or they will just disappear. If they use free providers (which is I presume what you mean in the first example), the provider will hopefully have strict limits in place that will flag high levels of waving as possible abuse. Unlike email, once their account is suspended, the wave that was sent will be a lot easer to identify as spam by the recipient (now, once an email is sent, it’s gone and suspending a spammer account makes no difference).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael</title>
		<link>http://the.geekorium.com/how-wave-could-tackle-the-spam-problem/#comment-2284</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Thu, 15 Apr 2010 12:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://firstwaves.org/?p=229477571#comment-2284</guid>
		<description>In point 2 of this article, you mention &quot;Hosting.&quot; What do you mean by this? Do you mean that the wave stays in that person&#039;s &quot;inbox/bin&quot; etc. indefinately, or are you referring to spammers setting up wave servers?

If you mean that the wave stays in their account, then it does not solve spam, as the user can just register a new account once they are done.

If you mean that spammers will host spam waves on their own servers, then this would stop them spamming completely, as that spam wave would be held on their server, and if they removed it from their server, no-one could access it.</description>
		<content:encoded><![CDATA[<p>In point 2 of this article, you mention “Hosting.” What do you mean by this? Do you mean that the wave stays in that person’s “inbox/bin” etc. indefinately, or are you referring to spammers setting up wave servers?</p>
<p>If you mean that the wave stays in their account, then it does not solve spam, as the user can just register a new account once they are done.</p>
<p>If you mean that spammers will host spam waves on their own servers, then this would stop them spamming completely, as that spam wave would be held on their server, and if they removed it from their server, no-one could access it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

