<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Mashable - The Social Media Guide - Latest Comments in Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.disqus.com/</link><description>Internet and Technology News - Mashable is the world’s largest blog focused exclusively on Web 2.0 and Social Networking news. With more than 5 million monthly pageviews, Mashable is the most prolific blog reviewing new Web sites and services, publishing breaking news on what’s new on the web.</description><atom:link href="https://mashable.disqus.com/twitter8217s_security_meltdown/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 10 Aug 2009 19:31:29 -0000</lastBuildDate><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-14604869</link><description>&lt;p&gt;Very nice "clarification" at the very end. I know some are starting to doubt cloud computing because of Twitter's security breaches, but I'm glad you touched on the more obvious human errors that caused Twitter's meltdown.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Attie</dc:creator><pubDate>Mon, 10 Aug 2009 19:31:29 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-14604795</link><description>&lt;p&gt;Very nice "clarification" at the very end. I know some are starting to doubt &lt;a href="http://www.itstrategists.com/Cloud-Computing.aspx" rel="nofollow noopener" target="_blank" title="More on cloud computing"&gt;cloud computing&lt;/a&gt; because of Twitter's security breaches, but I'm glad you touched on the more obvious human errors that caused Twitter's meltdown.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Attie</dc:creator><pubDate>Mon, 10 Aug 2009 19:29:37 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-13089889</link><description>&lt;p&gt;I think that they were just so wrapped up in their sites success that they totally ignored making sure that all of the security and loopholes were properly taken care of. &lt;a href="http://googlepeoplesearch.net" rel="nofollow noopener" target="_blank" title="http://googlepeoplesearch.net"&gt;Google People Search&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PeopleSearch</dc:creator><pubDate>Tue, 21 Jul 2009 22:13:25 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-13089855</link><description>&lt;p&gt;I think that they were just so wrapped up in their sites success that they totally ignored making sure that all of the security and loopholes were properly taken care of. &lt;a href="http://googlepeoplesearch.net" rel="nofollow noopener" target="_blank" title="http://googlepeoplesearch.net"&gt;Google People Search&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PeopleSearch</dc:creator><pubDate>Tue, 21 Jul 2009 22:12:29 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12804901</link><description>&lt;p&gt;I know YOU :)&lt;br&gt;but do people realize just how cool your site is ?&lt;br&gt;&lt;a href="http://searchles.com" rel="nofollow noopener" target="_blank" title="http://searchles.com"&gt;http://searchles.com&lt;/a&gt; :)&lt;br&gt;I talked with you along time ago can called to ask about DO FOLLOW on your site :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jsinkeywest</dc:creator><pubDate>Fri, 17 Jul 2009 05:05:34 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12743391</link><description>&lt;p&gt;This week Twitter’s own internal systems were hacked, along with the accounts of Twitter users including celebrities:&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.timacheson.com/Blog/2009/jul/twitter_hacked_via_google_apps" rel="nofollow noopener" target="_blank" title="http://www.timacheson.com/Blog/2009/jul/twitter_hacked_via_google_apps"&gt;http://www.timacheson.com/B...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;The point of entry wasn’t a gap in Twitter’s security. The hacker(s) gained access through a Google Apps account. The worry with a Google account is, it’s web-based and therefore only as secure as the rest of the Internet. If yuor Google account is compromised and you use Google Docs in a serious commercial setting, your Twitter account will be the least of your worries.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Acheson</dc:creator><pubDate>Thu, 16 Jul 2009 10:52:01 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12738715</link><description>&lt;p&gt;BS.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">genieyclo</dc:creator><pubDate>Thu, 16 Jul 2009 08:31:46 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12731046</link><description>&lt;p&gt;Sheesh, inflammatory language much? "Burn everything security-related down to the ground"? "Twitter needs to seriously rethink its attitude towards security"? You sound like a patronizing school principal.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bob</dc:creator><pubDate>Thu, 16 Jul 2009 02:21:30 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12723320</link><description>&lt;p&gt;I don't see how anyone can say this post discussing actual events, related to Twitter and some of its now multiple and very public security breaches, infers anything about the safety of Twitter user info. The inferences whether warranted or not, come from the actuality of these very public security breaches. That is not to say that because a Twitter server's password was "password" or that a breach or so described as a "hack" turned out to be social engineering, means Twitter user data is somehow unsafe. Is it possible that somehow the good people at Twitter could demonstrate lax regard for their own data and yet utter concern for user data? Entirely! Still if you use Twitter, a little extra caution should be exercised at the very least. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MykalBoss</dc:creator><pubDate>Wed, 15 Jul 2009 22:51:39 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12723092</link><description>&lt;p&gt;That right there is some amazing insight. Please sign me up for your newsletter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jarrod</dc:creator><pubDate>Wed, 15 Jul 2009 22:40:16 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12720767</link><description>&lt;p&gt;This is no surprise. My specialty is outside what you call "Social Media", and I can tell you that compared to other computing this whole genre has a downright reckless attitude toward privacy and security. It is stunning actually. When business plans actually set out to acquire and leverage private user data, stories like this are predictable.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">@gwoodard</dc:creator><pubDate>Wed, 15 Jul 2009 21:03:57 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12718026</link><description>&lt;p&gt;Yes, they need to make it as secure as possible.  Non spam?  GOOD LUCK.  Not gonna happen.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jim C.</dc:creator><pubDate>Wed, 15 Jul 2009 19:12:41 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12716935</link><description>&lt;p&gt;I think this line is where people get the wrong impression&lt;/p&gt;&lt;p&gt;"This same site (link omitted on purpose) now holds images from various personal accounts of  Twitter co-founder Evan Williams, including PayPal, Amazon, Gmail (Gmail) and MobileMe (MobileMe). "&lt;/p&gt;&lt;p&gt;What is being implied in the article is ambiguous at best and sensationalist at worst.&lt;/p&gt;&lt;p&gt;What you should say is that "user inputted data in the Twitter administration area is subject to compromise", if that uis what you actually mean.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">the King</dc:creator><pubDate>Wed, 15 Jul 2009 18:29:29 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12715201</link><description>&lt;p&gt;Does this even broach the topic of performance issues that severely hinder the site's usage?&lt;/p&gt;&lt;p&gt;Often, there is such a delay between what I type and its display on the screen that I rather choose to discontinue my efforts to "tweet".&lt;/p&gt;&lt;p&gt;If there is some sort of cyber-warfare going on, then isn't it time we push back?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kringle, A Corporation Sole</dc:creator><pubDate>Wed, 15 Jul 2009 17:27:56 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12713962</link><description>&lt;p&gt;Evan is the CEO of Twitter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris</dc:creator><pubDate>Wed, 15 Jul 2009 16:47:38 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12713707</link><description>&lt;p&gt;Oh darn! That's what I do too. Gonna change the one at Twitter NOW.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MC Cendana</dc:creator><pubDate>Wed, 15 Jul 2009 16:41:10 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12712310</link><description>&lt;p&gt;Agree with the footnote that no one should be concerned about their similar (paypal, gmail, amazon) accounts being compromised by this problem... but it does bring up the larger issue about the lack of security on SN sites in general and twitter in particular.  I don't feel any of what's known here will result in any exploits exposing info deeper than what's ON Twitter, but it should be apparent that what IS there is wide open.  Caveat Emptor... however we're not really 'buyers' cuz the service is free, and there may be a good reason for that and also why it's not looking so great for them to go commercial&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larry</dc:creator><pubDate>Wed, 15 Jul 2009 16:01:23 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12712233</link><description>&lt;p&gt;Agree with the footnote that no one should be concerned about their similar (paypal, gmail, amazon) accounts being compromised by this problem... but it does bring up the larger issue about the lack of security on SN sites in general and twitter in particular.  I don't feel any of what's known here will result in any exploits exposing info deeper than what's ON Twitter, but it should be apparent that what IS there is wide open.  Caveat Emptor... however we're not really 'buyers' cuz the service is free, and there may be a good reason for that and also why it's not looking so great for them to go commercial&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larry</dc:creator><pubDate>Wed, 15 Jul 2009 15:59:16 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12711995</link><description>&lt;p&gt;It's a lot better than letting your username/password out, and it also requires two separate hacks if you have Oauth: they need your secret key and pass key for the web app, and then the individual's user specific secret key and pass key (or whatever the terminology is, I forget). If you store those things in two different places it makes it much harder for the hacker to get actionable data. (yes, Twicsy uses Oauth, and yes we store the keys in different places)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dumbfounder</dc:creator><pubDate>Wed, 15 Jul 2009 15:52:45 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12709816</link><description>&lt;p&gt;@Alex: I understand your point of view. However, it's sometimes hard to please everyone. Even casual Mashable readers, or people who follow what's happening in or around Twitter casually are aware that certain celebrity Twitter accounts got hacked or compromised on several occasions. We've also posted about the Twitter admin panel images back in April, which were a good - if not certain - indication that one of Twitter's admin accounts have been compromised. And now the same hacker and the same French blogs that posted those images in April posted many more documents, which are supposedly (but then again, not certainly) coming from Evan Williams' (Twitter co-founder, added clarification in the text) various personal accounts, but have a lot to do with Twitter; in short, they're confidential company documents, some of which potentially very harmful.&lt;/p&gt;&lt;p&gt;So, this article takes this latest security issue, and ties it into the obvious pattern of security problems that have been pestering Twitter in the past couple of months. You and Dan are acting as if this is the only security-related incident that happened to Twitter. It is not.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stan_Schroeder</dc:creator><pubDate>Wed, 15 Jul 2009 14:55:10 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12708448</link><description>&lt;p&gt;So you claim that Twitter is having a "security meltdown" and your only proof is some idiot celebrities who used easy to guess passwords?  Stupid people will always pose a security threat to themselves.  That has nothing to do with the security of the service.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas</dc:creator><pubDate>Wed, 15 Jul 2009 14:23:03 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12706661</link><description>&lt;p&gt;You are talking about Twitter security flaws yet you are stating that "such-and-such" a site has shown images of Evan Williams' PayPal, Amazon, Gmail and MobileMe.  By saying it in such a manner, it makes it sound like they got this information through Twitter.  YOu never made it clear that they might have gotten these through some other manner.  I, at first, thought the same thing.&lt;/p&gt;&lt;p&gt;It's all in the grammar.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Burke</dc:creator><pubDate>Wed, 15 Jul 2009 13:39:54 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12706432</link><description>&lt;p&gt;Not good news for Twitter users...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Evelyn McCormack</dc:creator><pubDate>Wed, 15 Jul 2009 13:34:14 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12705720</link><description>&lt;p&gt;YO THIS IS A POOR STATMENT, "there’s absolutely no reason to believe that being a Twitter user implies a security risk to your other accounts. "  HAVING ANY SECURITY ISSUES WITH ONE ACCOUNT CAN LEAD TO THE TAKE OVER OF ALL ACCOUNTS, TOO MANY PEOPLE USE THE SAME PASSWORD FOR EVERYTHING. If someone's email password is the same as their twitter password, forgettaboutit!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Your Name*</dc:creator><pubDate>Wed, 15 Jul 2009 13:17:15 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s Security Meltdown</title><link>http://mashable.com/2009/07/15/twitter-security-meltdown/#comment-12705388</link><description>&lt;p&gt;These have nothing at all to do with Firefox.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John</dc:creator><pubDate>Wed, 15 Jul 2009 13:07:50 -0000</pubDate></item></channel></rss>