<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Dustpan &#187; TwitSweeper</title>
	<atom:link href="http://TheDustpan.com/tag/twitsweeper/feed/" rel="self" type="application/rss+xml" />
	<link>http://TheDustpan.com</link>
	<description>Discussing Twitter Spam</description>
	<lastBuildDate>Tue, 21 Sep 2010 18:09:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Should Confirmation Page be Paginated? (request for user feedback)</title>
		<link>http://TheDustpan.com/2010/01/should-confirmation-page-be-paginated-request-for-user-feedback/</link>
		<comments>http://TheDustpan.com/2010/01/should-confirmation-page-be-paginated-request-for-user-feedback/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 02:22:23 +0000</pubDate>
		<dc:creator>Doug Braun</dc:creator>
				<category><![CDATA[TwitSweeper Suggestions]]></category>
		<category><![CDATA[request for user feedback]]></category>
		<category><![CDATA[TwitSweeper]]></category>

		<guid isPermaLink="false">http://TheDustpan.com/?p=174</guid>
		<description><![CDATA[Request for User Feedback on Proposed Change to TwitSweeper
BACKGROUND: When TwitSweeper finds spammy or otherwise undesirable followers on a user&#8217;s Twitter account, it queues those followers for confirmation. When the user returns to TwitSweeper, they are presented with a list of the undesirable followers and asked to confirm (or retain) them. These undesirable followers are [...]<p><p><a href="http://TheDustpan.com/2010/01/should-confirmation-page-be-paginated-request-for-user-feedback/">Should Confirmation Page be Paginated? (request for user feedback)</a> is a post from <a href="http://TheDustpan.com">The Dustpan - Discussing Twitter Spam</a></p>
</p>
]]></description>
			<content:encoded><![CDATA[<p><strong>Request for User Feedback on Proposed Change to TwitSweeper</strong></p>
<p><strong>BACKGROUND:</strong> When TwitSweeper finds spammy or otherwise undesirable followers on a user&#8217;s Twitter account, it queues those followers for confirmation. When the user returns to TwitSweeper, they are presented with a list of the undesirable followers and asked to confirm (or retain) them. These undesirable followers are currently displayed in one long list.<span id="more-174"></span></p>
<p><strong>SUGGESTION: </strong>We received a suggestion for enhancement today from a TwitSweeper user asking if this confirmation page could be paginated into smaller <em>chunks</em> so that these undesirable followers could be confirmed in smaller groups (so the page wasn&#8217;t so long if you had hundreds of bad followers to confirm).</p>
<p><strong>YOUR PREFERENCE PLEASE: </strong>Could we please have YOUR feedback or preference on this proposed change by answering the following two questions in a Comment below:</p>
<p>(1) Should the confirmation page be paginated?  Yes (paginate it) / No (leave it as-is as one long page)</p>
<p>(2) If Yes (paginated), how many undesirable followers should be displayed on each page to confirm (before moving on to the next page of followers)? e.g. 25, 50, 75, 100, 200, other:____</p>
<p>We look forward to your thoughts on this change. Comment away please&#8230; <em>(and thanks for helping!)</em></p>
<p><p><a href="http://TheDustpan.com/2010/01/should-confirmation-page-be-paginated-request-for-user-feedback/">Should Confirmation Page be Paginated? (request for user feedback)</a> is a post from <a href="http://TheDustpan.com">The Dustpan - Discussing Twitter Spam</a></p>
</p>
]]></content:encoded>
			<wfw:commentRss>http://TheDustpan.com/2010/01/should-confirmation-page-be-paginated-request-for-user-feedback/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>TwitSweeper goes Public</title>
		<link>http://TheDustpan.com/2010/01/twitsweeper-goes-public/</link>
		<comments>http://TheDustpan.com/2010/01/twitsweeper-goes-public/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 20:14:16 +0000</pubDate>
		<dc:creator>chad</dc:creator>
				<category><![CDATA[TwitSweeper Features]]></category>
		<category><![CDATA[features]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[TwitSweeper]]></category>

		<guid isPermaLink="false">http://TheDustpan.com/?p=161</guid>
		<description><![CDATA[In the past few weeks we have received some great feedback from our private testers. We have implemented new features based on the initial feedback and we are very happy to announce TwitSweeper is now in Public Beta. For some of you that haven&#8217;t tried TwitSweeper yet, here are some of its many features that we think [...]<p><p><a href="http://TheDustpan.com/2010/01/twitsweeper-goes-public/">TwitSweeper goes Public</a> is a post from <a href="http://TheDustpan.com">The Dustpan - Discussing Twitter Spam</a></p>
</p>
]]></description>
			<content:encoded><![CDATA[<p>In the past few weeks we have received some great feedback from our private testers. We have implemented new features based on the initial feedback and we are very happy to announce <a href="http://twitsweeper.com">TwitSweeper</a> is now in Public Beta. <span id="more-161"></span>For some of you that haven&#8217;t tried <a href="http://twitsweeper.com">TwitSweeper</a> yet, here are some of its many features that we think you might enjoy!</p>
<h3>TwitSweeper is an &#8220;always on service.&#8221;</h3>
<p>TwitSweeper scans your account on a regular basis. You may login to your TwitSweeper Dashboard at any time to review your statistics and the date(s) that your Twitter account was last checked. You can register multiple Twitter accounts under one TwitSweeper Dashboard. You can enable TwitSweeper to send an email when activity has taken place on any of your Twitter accounts.</p>
<h3>Automatic or manual block &#8211; it&#8217;s your choice.</h3>
<ul>
<li>Automatically remove spammy followers</li>
<li>Remove spammy followers after a 72-hour notification to you</li>
<li>Notify you to review suspect followers &#8211; Wait for you to confirm</li>
</ul>
<h3>Expand the list of spam phrases.</h3>
<p>TwitSweeper is preloaded with thousands of phrases most often used by spammers. You can add your own phrases for maximum control. Any phrases that you add only affect your account(s).</p>
<h3>All of this for one low annual fee.</h3>
<p>Most services for Twitter are free. TwitSweeper is not one of them. We developed TwitSweeper because we hate being annoyed by spam and spammers. So we built the application on our servers so you don&#8217;t have to worry about downloading any apps to your computer. Our servers do the work and provide you with your personal account stats on an ongoing basis. It&#8217;s as easy as that. It depends on how you value your time and freedom. Our goal: Set it and forget it &#8211; cut down the annoyance factor, save time, make your Twitter experience easier and more enjoyable. It&#8217;s a small <a href="http://twitsweeper.com/pricing.php">price</a> to pay, but with real benefits.</p>
<p>You can try a free trial at <a href="http://TwitSweeper.com">http://TwitSweeper.com</a></p>
<p><p><a href="http://TheDustpan.com/2010/01/twitsweeper-goes-public/">TwitSweeper goes Public</a> is a post from <a href="http://TheDustpan.com">The Dustpan - Discussing Twitter Spam</a></p>
</p>
]]></content:encoded>
			<wfw:commentRss>http://TheDustpan.com/2010/01/twitsweeper-goes-public/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

