<?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>timwhitlock.info &#187; open letter</title>
	<atom:link href="http://timwhitlock.info/blog/tag/open-letter/feed/" rel="self" type="application/rss+xml" />
	<link>http://timwhitlock.info</link>
	<description>Tim Whitlock&#039;s personal site and blog</description>
	<lastBuildDate>Thu, 15 Dec 2011 13:51:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Open letter #1</title>
		<link>http://timwhitlock.info/blog/2009/08/23/open-letter-1/</link>
		<comments>http://timwhitlock.info/blog/2009/08/23/open-letter-1/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 21:58:30 +0000</pubDate>
		<dc:creator>tim</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[open letter]]></category>
		<category><![CDATA[twitblock]]></category>

		<guid isPermaLink="false">http://web.2point1.com/2009/08/23/open-letter-1/</guid>
		<description><![CDATA[I just received an email that I thought would be of interest to everyone. I have removed people&#8217;s names for reasons of privacy, but I have left the spelling mistakes in for a sense of realism. My open reply to the author follows at the bottom. Hello Tim, I&#8217;m glad to see you have changed [...]]]></description>
			<content:encoded><![CDATA[<p>I just received an email that I thought would be of interest to everyone. I have removed people&#8217;s names for reasons of privacy, but I have left the spelling mistakes in for a sense of realism. My open reply to the author follows at the bottom.<span id="more-135"></span></p>
<blockquote><p>Hello Tim,</p></blockquote>
<blockquote><p>I&#8217;m glad to see you have changed the Twitblock site as it appears it may do the job that you initialy wanted it do &amp; the bleeding seems to have stopped with me at 93 blocks. However &#8211; have you thought of ways of how you can reverse the damage your site did to other legitimate accounts like mine, @&lt;screen_name&gt; (71 blocks) &amp; other larger accounts who were majorly affected by your site with account blocks due to being mislabled as spammers/nuisances? All of those blocks damage reputations.</p>
<p>There is no question that a &#8220;lot of damage&#8221; was done. As I had said &#8211; on Friday night I did not sleep a single second as I had watched that evening my account blocks starting to increase &amp; increase. I have no idea of exactly how many acount blocks I had before your site came into existence but I am pretty sure my numbers were similar to @&lt;screen_name&gt; and &#8220;snowball effect&#8221; blocking due to your site rapidly increased the #s.</p>
<p>Personally I feel that your system should reverse all account blocks that you were responsible for and have people start over again fresh with your current site status. I also think you should apoligize to the many people that Twitblock affected negatively. &lt;name&gt; (@&lt;screen_name&gt;) is one of the sweetest ladies &amp; you saw how she was affected which is similar to my feelings &#8211; I felt awful &amp; it got worse as I saw the #s increase. Most accounts probably have no idea how they were affected by being mislabeled.</p>
<p>Anyway &#8211; I ask you to find a way to correct things. I do not want those account blocks on my Twitter account which damages my reputation &amp; potentially my account with Twitter. I look forward to your response.</p></blockquote>
<h3>My reply</h3>
<p><font color="#ff0000">The reason the blocks appeared to increase is that every time a Twitter user authenticates with TwitBlock we get access to more blocks. i.e. <strong>most of the blocks on these people&#8217;s accounts probably already existed</strong>. The incremental nature of them is largely an illusion. </font></p>
<p><font color="#000000">It is physically impossible for me to ascertain which blocks were performed via TwitBlock as opposed to those performed on Twitter.com or another third party application.</font></p>
<p><font color="#000000">To log into the Twitter API with one of my users&#8217; access keys and unblock a user from their account would be an abuse of TwitBlock&#8217;s privacy policy, not to mention thoroughly immoral.</font></p>
<p>To establish which blocks on your account were performed via TwitBlock, you would have to contact Twitter. I don&#8217;t know whether they record this information or whether they would give it out &#8211; My guess would be &#8220;maybe&#8221; and &#8220;probably not&#8221;.</p>
<p><em>As to what I shall be doing to &#8220;correct things&#8221;:</em></p>
<p>I shall be doing nothing to reverse the alleged and spurious damage for the reasons stated above. I have already spent my weekend altering the application in favour of a very small contingent of people, i.e. the author of this letter plus one or two more, who incidentally were far more polite.</p>
<p>I have also had one aggrieved &#8220;customer&#8221; succeed in getting two of my IP addresses black listed by an SPF provider meaning I cannot send emails to some ISPs from the TwitBlock servers. This act of aggression makes me very unlikely to bow to further pressure and less inclined to apologise to anyone.</p>
<p>I suspect the aggressor is one of the few people who have made contact with me already, and I shall also be exercising my own right to block Twitter users who direct aggression at me, or continually make unreasonable demands.</p>
<p>My focus continues to be making an application that works well for as many people as possible.</p>
]]></content:encoded>
			<wfw:commentRss>http://timwhitlock.info/blog/2009/08/23/open-letter-1/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
	</channel>
</rss>

