<?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; request for user feedback</title>
	<atom:link href="http://TheDustpan.com/tag/request-for-user-feedback/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>
	</channel>
</rss>

