<?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: Interesting question</title>
	<atom:link href="http://bradfordbenn.com/2009/09/interesting-question/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradfordbenn.com/2009/09/interesting-question/</link>
	<description>My thoughts and other things to share</description>
	<lastBuildDate>Wed, 18 Aug 2010 03:00:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dr Nick</title>
		<link>http://bradfordbenn.com/2009/09/interesting-question/comment-page-1/#comment-3683</link>
		<dc:creator>Dr Nick</dc:creator>
		<pubDate>Wed, 28 Oct 2009 04:44:04 +0000</pubDate>
		<guid isPermaLink="false">http://bradfordbenn.com/blog/?p=376#comment-3683</guid>
		<description>I say to keep &#039;em protected. I tried to publicize mine at one point recently, and I got SPAMMMMMMMMMED. People search the public timeline for hash threads and then reply to your posts with (what they think) are related threads. It&#039;s not worth it.

[nick]</description>
		<content:encoded><![CDATA[<p>I say to keep &#8216;em protected. I tried to publicize mine at one point recently, and I got SPAMMMMMMMMMED. People search the public timeline for hash threads and then reply to your posts with (what they think) are related threads. It&#8217;s not worth it.</p>
<p>[nick]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://bradfordbenn.com/2009/09/interesting-question/comment-page-1/#comment-3304</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Thu, 01 Oct 2009 18:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://bradfordbenn.com/blog/?p=376#comment-3304</guid>
		<description>One&#039;s desire of sense for privacy doesn&#039;t always need to be rational.

Sometimes people just like the sense of security that protecting one&#039;s Tweets would give, even though unprotecting those Tweets probably wouldn&#039;t really change your reader base or your risks.</description>
		<content:encoded><![CDATA[<p>One&#8217;s desire of sense for privacy doesn&#8217;t always need to be rational.</p>
<p>Sometimes people just like the sense of security that protecting one&#8217;s Tweets would give, even though unprotecting those Tweets probably wouldn&#8217;t really change your reader base or your risks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kneupper</title>
		<link>http://bradfordbenn.com/2009/09/interesting-question/comment-page-1/#comment-3287</link>
		<dc:creator>David Kneupper</dc:creator>
		<pubDate>Wed, 30 Sep 2009 04:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://bradfordbenn.com/blog/?p=376#comment-3287</guid>
		<description>Protecting tweets is a personal choice, and if you&#039;re comfortable with the sense of security, etc. it provides, don&#039;t sweat it.  

I&#039;m not a fan of protecting tweets, as the openness it provides has led me to follow people I never would have discovered otherwise.  You get bot followers of course, and they tend to come in waves. Once a week or so I go through my followers and weed out the bots and undesirables.  It&#039;s a 3-4 minute task, and a small price to pay for some great follow discoveries. 

My daughter and her 16-yr old friends protect their tweets of course, but for less vulnerable users the precise value of tweet protection is unclear. FWIW, most users (including myself) generally avoid trying to follow protected users.  I like to review people&#039;s tweets before I choose to follow them, and protection prevents that process. Protection creates one-way access in a two-way social medium, and thus will always have limited appeal.

My best suggestion is to unprotect for a while and see if it works for you.  If it doesn&#039;t, go back.  No worries. It may open some unexpected doors and alter your Twitter experience in a positive way.  Or the porn, real estate and marketing bots may creep you out.

Good luck, and let us know how it works out!</description>
		<content:encoded><![CDATA[<p>Protecting tweets is a personal choice, and if you&#8217;re comfortable with the sense of security, etc. it provides, don&#8217;t sweat it.  </p>
<p>I&#8217;m not a fan of protecting tweets, as the openness it provides has led me to follow people I never would have discovered otherwise.  You get bot followers of course, and they tend to come in waves. Once a week or so I go through my followers and weed out the bots and undesirables.  It&#8217;s a 3-4 minute task, and a small price to pay for some great follow discoveries. </p>
<p>My daughter and her 16-yr old friends protect their tweets of course, but for less vulnerable users the precise value of tweet protection is unclear. FWIW, most users (including myself) generally avoid trying to follow protected users.  I like to review people&#8217;s tweets before I choose to follow them, and protection prevents that process. Protection creates one-way access in a two-way social medium, and thus will always have limited appeal.</p>
<p>My best suggestion is to unprotect for a while and see if it works for you.  If it doesn&#8217;t, go back.  No worries. It may open some unexpected doors and alter your Twitter experience in a positive way.  Or the porn, real estate and marketing bots may creep you out.</p>
<p>Good luck, and let us know how it works out!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
