<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
     >
  <channel>
    <title>Sirius Stuff</title>
    <link>http://www.siriusventures.com/</link>
    <description>A static blog engine/compiler</description>
    <pubDate>Thu, 28 Apr 2011 23:43:35 GMT</pubDate>
    <generator>Blogofile</generator>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Twitter phishers are after your password</title>
      <link>http://www.siriusventures.com/twitter-phishers-are-after-your-password/</link>
      <pubDate>Thu, 29 Oct 2009 10:10:10 PDT</pubDate>
      <category><![CDATA[Web]]></category>
      <category><![CDATA[User Interface]]></category>
      <category><![CDATA[Twitter]]></category>
      <guid>http://www.siriusventures.com/twitter-phishers-are-after-your-password/</guid>
      <description>Twitter phishers are after your password</description>
      <content:encoded><![CDATA[
				<p id="p1">I was burned by this one!  Graham Cluley writes a nice article on his blog called <a href="http://www.sophos.com/blogs/gc/g/2009/10/28/twitter-phishers-password/">Twitter phishers are after your password </a></p>
<p id="p2">What was really appalling to me was getting burned by this screen:<br/>
<img id="image119" src="/site_img/tw-phishing-550.jpg" alt="Fake twitter login screen"/><br/>
Twitter, like Facebook, lets you use other sites by handling authorization.   I’d been having serious problems with Twitter not accepting my password (as were thousands of others, apparently) and it just got fixed last week.  So even though I was logged in and active on twitter.com, I wasn’t surprised to be prompted to login.  And I didn’t look closely enough at the URL.</p>
<p id="p3">Of course I wasn’t surprised to see this:<br/>
<img id="image120" src="/site_img/tw-over-capacity-550.jpg" alt="Fail whale - you've seen this"/><br/>
Takeaways?   Twitter has becoming more and more reliable.   They are fixing bugs.   And we all need to watch where we’re going - sometimes we think we’re someplace we’re not.  </p>
<p id="p4"><em>images courtesy of <a href="http://www.sophos.com">Sophos</a> I copied them so they won’t take their bandwidth or disappear if they change their links.</em> </p>
]]></content:encoded>
    </item>
  </channel>
</rss>

