No, you’re not seeing things. I’m back, and I’m coming out of the Bird House swinging!

It’s been a long break, the first half of it expected and the other half completely unexpected; and I return to talk about foursquare, Please Rob Me, and the current concern sweeping through the Twitterverse. Adding to the debate of how much information is too much information comes FortheHack and their stand against sharing GPS coordinates for neat-o badges and free stuff from various vendors in the real world. Hear my own view of it from the Bird House and pick up a few twips in this episode on how to stay safe while sharing with your fellow Twitterakians.

Guest introduction by Starla Huchton

Featured movie and TV clips:

• Firefly
• The Treasure of the Sierra Madre
  
• Monty Pyhton’s “How Not to Be Seen” sketch
  
• Army of Darkness
  

Featured People and Stories:

• Security Expert Robert Siciliano
• Siciliano’s Twitter posting to CBS segment on “Please Rob Me”
• Siciliano’s tweet concerning “Please Rob Me”
• Exchange between me and Brand Gamblin
• Brightkite

Album Artwork by Paul Fischer of Dancing Cat Studios

Feel free to syndicate this audio, and provide feedback or topics you’d like to hear discussed on Bird House Rules at 703.791.1701, tmorris (at) imaginethatstudios (dot) com, Twitter, or here at the Bird House Rules Blog!

Numerous Twitter users are pointing out that Twitter forced them to change their passwords out of the blue. According to blogger Andrew Girdwood, these users have received an e-mail containing the following message: “Due to concern that your account may have been compromised in a phishing attack that took place off-Twitter, your password was reset,” together with a link for resetting the password.

Although the e-mail itself looks like a phishing attack, it’s genuine; it seems that admins at Twitter have discovered something fishy is going on, and they’re trying to prevent further damage before it happens.

I’ve been reading up on this all morning (with postings from TechCrunch and The Washington Post as examples); and while this situation shouldn’t be taken lightly, I am not scrambling to change my passwords on my accounts. Why?

1. I’m finding out about this scam via Twitter.
2. The people on Twitter are finding out via an “official email” from Twitter.com.
3. On Twitter’s Status and News blogs and on Twitter’s own feed, there is no mention of this phishing scam whatsoever.

Seeing as through email and social networks is how phishers work, this gives me a moment’s pause. And it should do the same for you, too.

Before concerning yourself with changing of passwords and falling prey to a malicious hacker, follow this simple checklist:

• Check your third party clients (TweetDeck, DestroyTwitter, etc.) and see how they are behaving. If they are connecting with Twitter, you are doing just fine.
• Check Twitter Status. This is one of two blogs that keep users in the know about what is happening on Twitter. This particular blog is more technically oriented, but reports outages and hostile actions such as DoS attacks.
• Check Twitter’s Blog. This is news and developments from Twitter’s home base, and usually developers will give commentary here on any hacker attacks, interface redesigns, or serious issues that Twitter is encountering at that time.
• Follow @Twitter’s feed. No, they might not answer a query, but with something as serious as this there may be some updates in their feed that can give you sound advice on how to fix a potential problem.

As of the posting of this column, there has been no solid confirmation from Twitter of this phishing attack. While many are tweeting and retweeting that something is up in the network, it does not necessarily mean that it is actually happening. Always check with Twitter before taking action. It may be a moment’s hesitation, but in that brief second you may be able to avoid unwanted stress and undue inconvenience.

Keep an eye on the Bird House for more as this develops.

UPDATE, 12:58pm EST: With special thanks to Lila Scot, another resource to check is @safety, Twitter’s Trust and Safety account. They did have a post about this at 11:26 am, several hours after Mashable, The Washington Post, et. al. went live with their postings. However, there is still no mention of this being a phishing attack.

UPDATE, 3 February, 11:25am EST: I checked @safety this morning and saw that there was a posting in Twitter Status that mentions the importance of changing your password. While what they describe is a phishing attack, the situation from yesterday appears to be less of an attack and more of a preemptive strike from the Twitter Safety Team headed up by Del Harvey. Whatever the case may be, it appears that all is right in the Twitterverse and our status is at green. You are now free to tweet happily. Make it so.

This morning, a lot of things were explained.

Maybe these hackers were partially responsible for yesterday’s intermittent service. Maybe the odd behavior from Twitter was merely a precursor for what PCWorld reported early this morning. Maybe I was the only one thinking about the DoS Attack from this summer, but Twitter was once again under fire. A group referring to themselves as The Iranian Cyber Army redirected for a brief time all Twitter traffic to a landing page of their design. Sumner Lemon of IDG News Service reports:

Visitors instead saw a black screen with an image of a green flag and Arabic writing. The defaced site also included a message that said, “This site has been hacked by Iranian Cyber Army,” and an e-mail address.

Twitter blamed the outage on changes made to the company’s DNS (Domain Name System) records, which match the company’s domain name with the IP addresses of its servers.

Meanwhile, the news from Twitter Status was that as of 11:28pm, last night:

Twitter’s DNS records were temporarily compromised but have now been fixed. We are looking into the underlying cause and will update with more information soon.

So far, nothing new has really surfaced apart from critics who are saying this is just another show of how vulnerable Social Media sites are. I, for one, applaud Twitter’s resilience. They only lost service for an hour (which was probably when I was engrossed in my weekly dose of Mythbusters…) and managed to bounce back. Yesterday had been a somewhat uneven day for Twitter, but they have seen worse. Much worse. I think yesterday’s performance is proof extremely positive that Twitter has learned their lessons from previous growing pains.

So as the dust settles from yesterday, just remember…

…and tweet happy!

When I clicked on the link, I was asked for my Username and Password.  Ummm…no. So I attempted to ping my Twitter contact here and ask if this was, in fact, a real URL. I could not get a DM reply to appear.

And then on the main feed, I saw this from @spam, Twitter’s Spam Hotline:

You might think this is common sense, but it may surprise you how easily people surrender their passwords, particularly from DMs coming from friends and acquaintances.

Be careful!
Someone is out there get phreaky with the phishing.

Just remember these safety twips when you are out in the Twitterverse:

• Never give out your password, even if it’s to someone you know or if they are promising you a bucketload of followers.
• If you do get a DM asking for your password, try to contact the friend on the open feed asking why?
• If someone is, in fact, DMing others with your account, immediately change your password, log out, wait a few ticks, then log in with the new password.
• If you can, change your password for Twitter every 30-60 days.

Twitter is on the case, but make sure you let your fellow Twitterakians know that something  is afoot. Stay safe, everyone, and tweet happy!

Welcome to Birdhouse Rules, the Official Podcast of All a Twitter and Sams Teach Yourself Twitter in Ten Minutes.

I know on Twitter i have been promising to cover TweetDeck and my bad habit of double-posting (which on writing these show notes I just did…) but then when working through my follow requests, I got hard hit by the avatar you see with this post. Yes, if you see that image (and the variations on it) you will have been hit by a spambot that prefixes all their IDs with “STi_”. These useless accounts will fill your feeds with random links that serve no other purpose other than to annoy the crap out of you.

But what really bakes my birdhouse about the various “STi_” accounts is that they are posing as real people.

Welcome to spam on Twitter.

In this episode I cover the ways to tell if you are being spammed on Twitter. The offending tweets are broken down into three categories, and we also take a look at how some spammers are working into your feeds in order to use you and a delivery mechanism. Take a look at these screen captures from Stephanie Lloyd‘s account…

If you click-and-enlarge the left image, you will note that Stephanie’s tweets are coming from her feed are coming from recognizable applications. The right image, though, is a tweet coming from an API. That is just one (of a few) ways to tell that the spam your getting from friends isn’t their fault.

So tuck in and get ready — it’s a Feast of Spam at the Bird House.

Guest introduction by Indiana Jim

“Spam” from Monty Python’s The Final Rip Off

Album Artwork by Paul Fischer of Dancing Cat Studios

Feel free to syndicate this audio, and provide feedback or topics you’d like to hear discussed on Bird House Rules at 703.791.1701, tmorris (at) imaginethatstudios (dot) com, Twitter, or here at the Bird House Rules Blog!

Welcome to Birdhouse Rules, the Official Podcast of All a Twitter and Sams Teach Yourself Twitter in Ten Minutes.

I promised that the show was going to post on a fortnightly schedule; but in light of recent events, I decided to shuffle the schedule around and make the first episode something timely. I wanted to talk about what happened on Twitter (and elsewhere) all day Thursday, August 6, 2009.

Just in case you missed it, you can hop over to the link I provide here in the show notes, but safe to say, it was a really busy day. It has taken Twitter a few days to recover. From the looks of things and according to the Status blog, there are still a few pieces needing to be picked up but Twitter — on a whole — is running smoothly.

This show was imspired not only by the events of last week but also by a comment left behind by our Guest Voice. Take a look at the blog, have a listen to this episode, and take a moment to send a “thank you” note to Twitter.com. They really managed to hold things together, and we should all be appreciative of their hard work for this free service they provide.

Guest introduction by Fred Castaneda

“All is Well” drop-in’s from National Lampoon’s Animal House.

Album Artwork by Paul Fischer of Dancing Cat Studios

Feel free to syndicate this audio, and provide feedback or topics you’d like to hear discussed on Bird House Rules at 703.791.1701, tmorris (at) imaginethatstudios (dot) com, Twitter, or here at the Bird House Rules Blog!

From Twitter Status comes this nuggest of good news:

We are defending against a denial-of-service attack, and will update status again shortly.

Okay, that doesn’t sound good.

What exactly is a Denial-of-Service or DoS Attack? Heck — I’d never heard of it and I’m a geek, passionate about his Social Media. So, I turned to Google and started the research. In a nutshell, it’s bad. REALLY bad. From the files of U.S. Computer Emergency Readiness Team (CERT) comes a definition of what a DoS Attack is all about:

In a denial-of-service (DoS) attack, an attacker attempts to prevent legitimate users from accessing information or services. By targeting your computer and its network connection, or the computers and network of the sites you are trying to use, an attacker may be able to prevent you from accessing email, web sites, online accounts (banking, etc.), or other services that rely on the affected computer.

The most common and obvious type of DoS attack occurs when an attacker “floods” a network with information. When you type a URL for a particular web site into your browser, you are sending a request to that site’s computer server to view the page. The server can only process a certain number of requests at once, so if an attacker overloads the server with requests, it can’t process your request. This is a “denial of service” because you can’t access that site.

So yeah. This is bad.

Right now, according to Twitter, they are back online and picking up the pieces of this malicious assault on their servers; so if you feel like coming on to the network and complaining about them, think twice. As I mentioned last night (and probably will, again, in an upcoming interview), Twitter has been growing like Kutzu on steroids, and trying to come up with adequate security is an ongoing challenge. I applaud them for keeping us all in the loop and for handling this as well as they have, but sadly this is a reminder of how their security should become an issue of highest priority.

I’ll have more information here as the day progresses, but remember you can keep tabs on Twitter’s Status by clicking here. See you all on the tweet side.

UPDATE at 3:14pm EST

Doesn’t look like Twitter is the only one getting slammed by hackers. From Wired Magazine comes confirmation that Facebook is also under a DoS attack:

Facebook has confirmed to Wired.com that — like Twitter — it was the victim of a denial-of-service attack Thursday morning.

“Earlier this morning, Facebook encountered network issues related to an apparent distributed denial-of-service attack, that resulted in degraded service for some users,” responded Facebook spokeswoman Kathleen Loughlin via e-mail.

Facebook seems to be weathering the storm, but Fan Pages have been reported offline and their response time on other pages slow. Twitter has been on and off, and some folks in my networks have been voicing their ire abut their inconsistency. Remember that while, yes, Twitter is awesome, it is also dealing with people today that are not-so-awesome and are making life in 140-characters-or-less close-to-near impossible. Be patient with Twitter. It’s not going anywhere, but it is getting hammered by hackers today.