<?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"
	>
<channel>
	<title>Comments on: Major Security Hole at Tumblr</title>
	<atom:link href="http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/</link>
	<description>Startup and Technology News</description>
	<pubDate>Sat, 30 Aug 2008 15:17:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Privacy Disaster At Twitter: Direct Messages Exposed (Update: GroupTweet Is Likely Culprit) &#124; crown.MONKEY</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2220308</link>
		<dc:creator>Privacy Disaster At Twitter: Direct Messages Exposed (Update: GroupTweet Is Likely Culprit) &#124; crown.MONKEY</dc:creator>
		<pubDate>Thu, 24 Apr 2008 09:20:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2220308</guid>
		<description>[...] seeing an increasing trend of privacy issues pop up around new web applications and all this distributed [...]</description>
		<content:encoded><![CDATA[<p>[...] seeing an increasing trend of privacy issues pop up around new web applications and all this distributed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TechCrunch Japanese アーカイブ &#187; Twitterで非公開メッセージ暴露さる（GroupTweetの仕業？）</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2218727</link>
		<dc:creator>TechCrunch Japanese アーカイブ &#187; Twitterで非公開メッセージ暴露さる（GroupTweetの仕業？）</dc:creator>
		<pubDate>Wed, 23 Apr 2008 19:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2218727</guid>
		<description>[...] 新たなウェブアプリやデータ配信がウェブで次々誕生するにつれ、こういったプライバシー問題も最近は増加傾向にある。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 新たなウェブアプリやデータ配信がウェブで次々誕生するにつれ、こういったプライバシー問題も最近は増加傾向にある。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Privacy Disaster At Twitter: Direct Messages Exposed</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2216855</link>
		<dc:creator>Privacy Disaster At Twitter: Direct Messages Exposed</dc:creator>
		<pubDate>Wed, 23 Apr 2008 11:14:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2216855</guid>
		<description>[...] depending on the number of users affected, possibly a more embarrassing security slipup than Tumblr saw last week). Forget downtime, this causes direct and substantial harm to anyone affected. And if it happened [...]</description>
		<content:encoded><![CDATA[<p>[...] depending on the number of users affected, possibly a more embarrassing security slipup than Tumblr saw last week). Forget downtime, this causes direct and substantial harm to anyone affected. And if it happened [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2186653</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Thu, 17 Apr 2008 14:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2186653</guid>
		<description>@Watts and Cameron ;at the time of my post the breach had already been fixed. i suppose when i take a second look i have to agree with the statement we do not need to know about the breach at the moment it happens.  I was  responding more to the protection of free speech and press. Note that i am not a journalist either, so i do not know a lot about standard journalistic practice. Also with further insight into my own statements, i decided i was being contradictory in that i was defending tech crunch in their right to publish without regard to the rights of the readers to repost. This i think is a fantastic system where the journalist is held very much accountable not only to the public, but to each and every readers individual assessment of their journalistic integrity. good job for keeping not only tech crunch in check, but me too.</description>
		<content:encoded><![CDATA[<p>@Watts and Cameron ;at the time of my post the breach had already been fixed. i suppose when i take a second look i have to agree with the statement we do not need to know about the breach at the moment it happens.  I was  responding more to the protection of free speech and press. Note that i am not a journalist either, so i do not know a lot about standard journalistic practice. Also with further insight into my own statements, i decided i was being contradictory in that i was defending tech crunch in their right to publish without regard to the rights of the readers to repost. This i think is a fantastic system where the journalist is held very much accountable not only to the public, but to each and every readers individual assessment of their journalistic integrity. good job for keeping not only tech crunch in check, but me too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ArringtonMuchosSuckas</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2185268</link>
		<dc:creator>ArringtonMuchosSuckas</dc:creator>
		<pubDate>Thu, 17 Apr 2008 04:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2185268</guid>
		<description>You suck for laughing at others fault.</description>
		<content:encoded><![CDATA[<p>You suck for laughing at others fault.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tabish</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2184754</link>
		<dc:creator>Tabish</dc:creator>
		<pubDate>Thu, 17 Apr 2008 00:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2184754</guid>
		<description>Ah, I meant that for Arrington.</description>
		<content:encoded><![CDATA[<p>Ah, I meant that for Arrington.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tabish</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2184751</link>
		<dc:creator>Tabish</dc:creator>
		<pubDate>Thu, 17 Apr 2008 00:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2184751</guid>
		<description>Just because I couldn't resist responding to your juvenile behavior, and partly because it turns me on so much, here's a rub: Tumblr, not iTumblr.</description>
		<content:encoded><![CDATA[<p>Just because I couldn&#8217;t resist responding to your juvenile behavior, and partly because it turns me on so much, here&#8217;s a rub: Tumblr, not iTumblr.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabricio Zuardi</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2183509</link>
		<dc:creator>Fabricio Zuardi</dc:creator>
		<pubDate>Wed, 16 Apr 2008 16:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2183509</guid>
		<description>What kind of asshole posts a security breach on a high traffic website before contacting the site owners... disgusting.</description>
		<content:encoded><![CDATA[<p>What kind of asshole posts a security breach on a high traffic website before contacting the site owners&#8230; disgusting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Watts</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181949</link>
		<dc:creator>Watts</dc:creator>
		<pubDate>Wed, 16 Apr 2008 06:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181949</guid>
		<description>Um, no, "good journalism" does not require the article to go up before Tumblr has a chance to respond. Standard journalistic practice, which is what I believe you're really referring to, involves at least trying to get a statement from all the interested parties. Or have you never noticed the "So-and-so did not respond to our requests for comments" in newspaper articles before?

Good security reporting practices, on the other hand, pretty much DO require giving the affected party a chance to not only respond but repair before widely disseminating a breach. Cameron is absolutely correct in his response above.

This is an issue that others have noted with TechCrunch, although it's absolutely not unique to them: a desire to be the first big-name outlet with "the scoop" means that you're throwing standard journalistic practices out the window whenever they threaten to slow you down. You may publish clarifications and expansions throughout the day, but that's not the same as taking the time to get it as close to right as possible to start with. (Of course, when someone corrects you, you may dismiss them entirely for sending negative energy your way. We all have our own ideas of what "editorial standards" mean.)</description>
		<content:encoded><![CDATA[<p>Um, no, &#8220;good journalism&#8221; does not require the article to go up before Tumblr has a chance to respond. Standard journalistic practice, which is what I believe you&#8217;re really referring to, involves at least trying to get a statement from all the interested parties. Or have you never noticed the &#8220;So-and-so did not respond to our requests for comments&#8221; in newspaper articles before?</p>
<p>Good security reporting practices, on the other hand, pretty much DO require giving the affected party a chance to not only respond but repair before widely disseminating a breach. Cameron is absolutely correct in his response above.</p>
<p>This is an issue that others have noted with TechCrunch, although it&#8217;s absolutely not unique to them: a desire to be the first big-name outlet with &#8220;the scoop&#8221; means that you&#8217;re throwing standard journalistic practices out the window whenever they threaten to slow you down. You may publish clarifications and expansions throughout the day, but that&#8217;s not the same as taking the time to get it as close to right as possible to start with. (Of course, when someone corrects you, you may dismiss them entirely for sending negative energy your way. We all have our own ideas of what &#8220;editorial standards&#8221; mean.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181812</link>
		<dc:creator>Cameron</dc:creator>
		<pubDate>Wed, 16 Apr 2008 05:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181812</guid>
		<description>Mike, so by your logic, if Tumblr is dependable to share security breaches with their users, why did you post this? And even if you say this was a test of their dependable nature, you could have at least called them or made sure they fixed it before posting.

The users don't need to know the absolute second of a security breach. It's not like the users can do anything to stop someone with admin privileges, it's true they needed to know, but you could have emailed Tumblr or contacted them and told them you were going to post at the end of the day.

Jesus. Give them some time.</description>
		<content:encoded><![CDATA[<p>Mike, so by your logic, if Tumblr is dependable to share security breaches with their users, why did you post this? And even if you say this was a test of their dependable nature, you could have at least called them or made sure they fixed it before posting.</p>
<p>The users don&#8217;t need to know the absolute second of a security breach. It&#8217;s not like the users can do anything to stop someone with admin privileges, it&#8217;s true they needed to know, but you could have emailed Tumblr or contacted them and told them you were going to post at the end of the day.</p>
<p>Jesus. Give them some time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181676</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Wed, 16 Apr 2008 04:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181676</guid>
		<description>It's a php app folks.  For the ruby/rails hater above.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a php app folks.  For the ruby/rails hater above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blowmii</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181547</link>
		<dc:creator>blowmii</dc:creator>
		<pubDate>Wed, 16 Apr 2008 03:20:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181547</guid>
		<description>Go F#$k Yourself. 

Show some class. What goes around comes around.</description>
		<content:encoded><![CDATA[<p>Go F#$k Yourself. </p>
<p>Show some class. What goes around comes around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blowski</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181486</link>
		<dc:creator>Blowski</dc:creator>
		<pubDate>Wed, 16 Apr 2008 02:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181486</guid>
		<description>Oh, BTW, I like cock and balls.</description>
		<content:encoded><![CDATA[<p>Oh, BTW, I like cock and balls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blowski</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181447</link>
		<dc:creator>Blowski</dc:creator>
		<pubDate>Wed, 16 Apr 2008 02:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181447</guid>
		<description>Just wanted to say - I post comments on here a fair bit and the Blowski doing a spot of FUD above (#22,#25) is not me. Just for the record.</description>
		<content:encoded><![CDATA[<p>Just wanted to say - I post comments on here a fair bit and the Blowski doing a spot of FUD above (#22,#25) is not me. Just for the record.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181291</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 16 Apr 2008 01:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181291</guid>
		<description>i find it strange there are so many people mad that this mistake was published. GOOD journalism dictates that everyone be notified as soon as something happened, and a good journalist has good sources. If the report was incorrect then we look at the journalist. In this case it was not.  kudos for fixing it so fast, but we have to take into account the fact that if it can be fixed faster than it is reported, we may never know our information was compromised. Luckily we could depend on tumblr to tell everyone, but not every site is so ethically well adjusted.</description>
		<content:encoded><![CDATA[<p>i find it strange there are so many people mad that this mistake was published. GOOD journalism dictates that everyone be notified as soon as something happened, and a good journalist has good sources. If the report was incorrect then we look at the journalist. In this case it was not.  kudos for fixing it so fast, but we have to take into account the fact that if it can be fixed faster than it is reported, we may never know our information was compromised. Luckily we could depend on tumblr to tell everyone, but not every site is so ethically well adjusted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Kelly</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181277</link>
		<dc:creator>Sean Kelly</dc:creator>
		<pubDate>Wed, 16 Apr 2008 01:03:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181277</guid>
		<description>That's great that they got a handle on things. It is problems like this that cause me to be wary of storing personal information on the internet.</description>
		<content:encoded><![CDATA[<p>That&#8217;s great that they got a handle on things. It is problems like this that cause me to be wary of storing personal information on the internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181239</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Wed, 16 Apr 2008 00:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181239</guid>
		<description>We all know what to do when it is discovered TechCrunch has a security hole</description>
		<content:encoded><![CDATA[<p>We all know what to do when it is discovered TechCrunch has a security hole</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nat</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181167</link>
		<dc:creator>Nat</dc:creator>
		<pubDate>Wed, 16 Apr 2008 00:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181167</guid>
		<description>a week ago another website i frequently visit  Killerstartups.com have a problem and you can see the whole index of the website  including the admin logging  and within minutes or so, everything is fixed.


Nat
www.workersinc.com</description>
		<content:encoded><![CDATA[<p>a week ago another website i frequently visit  Killerstartups.com have a problem and you can see the whole index of the website  including the admin logging  and within minutes or so, everything is fixed.</p>
<p>Nat<br />
<a href="http://www.workersinc.com" rel="nofollow">http://www.workersinc.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EH</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181166</link>
		<dc:creator>EH</dc:creator>
		<pubDate>Tue, 15 Apr 2008 23:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181166</guid>
		<description>Love all the "security through obscurity" arguments against publicizing this crack. Must be a lot of aspiring CEOs who are practicing their authoritarian management techniques so they don't ever have to account for their mistakes. 

Sorry all you paper MBAs, but it helps the USERS to know that theres a problem on the site so they can figure out what they want to do. If this means not using your service/site anymore then you should think about talking to your development director or other programming managment about quality control and accepted practices. Making sure an admin is actually an admin is ultra-basic.</description>
		<content:encoded><![CDATA[<p>Love all the &#8220;security through obscurity&#8221; arguments against publicizing this crack. Must be a lot of aspiring CEOs who are practicing their authoritarian management techniques so they don&#8217;t ever have to account for their mistakes. </p>
<p>Sorry all you paper MBAs, but it helps the USERS to know that theres a problem on the site so they can figure out what they want to do. If this means not using your service/site anymore then you should think about talking to your development director or other programming managment about quality control and accepted practices. Making sure an admin is actually an admin is ultra-basic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Head</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181141</link>
		<dc:creator>Richard Head</dc:creator>
		<pubDate>Tue, 15 Apr 2008 23:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181141</guid>
		<description>I see you have no ethical problems reporting a publicizing a security hole before it is fixed. Any decent journalist would fact check a story before running with it, so why not pause before publishing here too?

It really is accepted practice to notify people about security holes and only going public to force the company's hand if they refuse to fix it. Doing anything other than this shows you up as a publicity hungry, ethically naive hack.</description>
		<content:encoded><![CDATA[<p>I see you have no ethical problems reporting a publicizing a security hole before it is fixed. Any decent journalist would fact check a story before running with it, so why not pause before publishing here too?</p>
<p>It really is accepted practice to notify people about security holes and only going public to force the company&#8217;s hand if they refuse to fix it. Doing anything other than this shows you up as a publicity hungry, ethically naive hack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TechCrunch Japanese アーカイブ &#187; Tumblrに重大な脆弱性</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181122</link>
		<dc:creator>TechCrunch Japanese アーカイブ &#187; Tumblrに重大な脆弱性</dc:creator>
		<pubDate>Tue, 15 Apr 2008 23:31:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181122</guid>
		<description>[...] [原文へ] [...]</description>
		<content:encoded><![CDATA[<p>[...] [原文へ] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181099</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Tue, 15 Apr 2008 23:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181099</guid>
		<description>Posting this before Tumblr could adequately respond and deal with the issue is an insult to David and Marco, as well as every legitimate Tumblr user out there, aside from this not even being real news. You guys are no better than the people who ended up mucking around with things during the breach.</description>
		<content:encoded><![CDATA[<p>Posting this before Tumblr could adequately respond and deal with the issue is an insult to David and Marco, as well as every legitimate Tumblr user out there, aside from this not even being real news. You guys are no better than the people who ended up mucking around with things during the breach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonathan</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181085</link>
		<dc:creator>jonathan</dc:creator>
		<pubDate>Tue, 15 Apr 2008 23:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181085</guid>
		<description>why does techcrunch publish this stuff before the hole is fixed.. sending hurds of script kiddies to mess with the exploit is not cool.. and it certainly is not news.. arghh..</description>
		<content:encoded><![CDATA[<p>why does techcrunch publish this stuff before the hole is fixed.. sending hurds of script kiddies to mess with the exploit is not cool.. and it certainly is not news.. arghh..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Afraid of the dark</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181033</link>
		<dc:creator>Afraid of the dark</dc:creator>
		<pubDate>Tue, 15 Apr 2008 22:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181033</guid>
		<description>seriously, why would you post this as soon as you found out about it. I know this is a blog, but have some decency</description>
		<content:encoded><![CDATA[<p>seriously, why would you post this as soon as you found out about it. I know this is a blog, but have some decency</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Allen</title>
		<link>http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181030</link>
		<dc:creator>Ryan Allen</dc:creator>
		<pubDate>Tue, 15 Apr 2008 22:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/04/15/major-security-hole-at-tumblr/#comment-2181030</guid>
		<description>Gee TechCrunch, you guys are awesome. Bet you'll think it's awesome when someone announces an open security hole in your site before it's fixed.

What goes around comes around. I hope you get back what you deserve for this selfish post. 

Are you going to start posting about celebrities on drug rehab stints or is this kind of reporting only temporary?</description>
		<content:encoded><![CDATA[<p>Gee TechCrunch, you guys are awesome. Bet you&#8217;ll think it&#8217;s awesome when someone announces an open security hole in your site before it&#8217;s fixed.</p>
<p>What goes around comes around. I hope you get back what you deserve for this selfish post. </p>
<p>Are you going to start posting about celebrities on drug rehab stints or is this kind of reporting only temporary?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.089 seconds -->
