We had a blast on this interview, and I hope you enjoy the listen. Feel free to comment, post, and share!

From Twitter I heard from long-time-friend of the Bird House @Odin1eye who featured me in a particularly fun interview on his blog View From Vahalla. This blog features podcast reviews, commentary and rants on Social Media and the world it impacts, and (now) interviews. Odin1eye and I talk about about how Twitter has changed, where it is headed, and what went into the writing of All a Twitter. Here’s a selection from the interview:

I find that the Social Media Experts (a/k/a Evangelists, Mavens, Enthusiasts, Oracles, etc. a/k/a Social Media Douchebags a/k/a SMDs) are becoming less and less tolerated. Some of these self-proclaimed Twitter Messiahs are preaching their gospel to a flock in the hundreds of thousands, but tend to follow back less than a thousand or even less than a hundred.

What’s up with that?

I’m just going to call it like I see it: Everybody wants to be Chris Brogan (@ChrisBrogan)(respectful [ding]) but so few are achieving the balance between pro and personal. Chris isn’t perfect, but he is maintaining the genuine while managing the massive numbers. (One of many reasons I got that trust agent to write the AAT Foreword.) There are others like Jeff Sass (@sass) and CC Chapman (@cc_chapman) who are putting forward that effort to stay honest on Twitter. Between 2008-2009 there were SMDs left and right who nurtured the numbers and then stopped participating in their feeds. Oh sure, they would preach how they used Twitter to “connect” but look at their feeds and it would be RTs, quotes, and questions that linked back to their own site.

This interview was a real pleasure, and I hope you enjoy the read. Feel free to comment, post, and share; and expect more from my blogosphere-podosphere tour this month.

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!

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!

(click image to view Full Size)

…and yet, no real reason given as to what happened with the Retweets this morning.

Anyone else thinking this?

It’s all about communication, Twitter. We just want to know what’s happening…

Changing its interface as one would change underwear, Twitter apparently pulled a back-handed “Give the People What They Want” by removing the new Retweet feature. This feature has been in Beta since the Fall of this year and Twitterakians were kept in the loop as early as idea conception. Sure, there was a slight learning curve and not everyone took to it, but third-party clients adopted it into their user interfaces and many like TweetDeck and Twittelator Pro added the functionality with their own flair. I even covered it in the last Bird House with a video addendum.

But this morning I got a tweet from John Merlin (@zard) from the UK:

Ahahaha! Wondering if @ITStudios will be recording a new vidcast for the lack of retweet

I asked what he meant by that, and he directed me back to my own homepage. (Click for a full view.) Notice anything missing?

And that is how I found out about Twitter removing the new Retweet option.

What angers me is not that Twitter removed the function. As I eluded to earlier, it was received with mixed reviews; but I’m wondering if enough of these so-called “Social Media Gurus, Mavens, and Experts” (which will be covered in a future podcast) rose a big enough stink to pressure Twitter in removing the option. Whatever the reason, that is Twitter’s decision in the end, and any changes they make I will roll with because I’m not paying for Twitter’s service. I appreciate what they do and that I’m getting it for free.

What I don’t appreciate is Twitter making these changes seemingly on a whim without notifying their network. I went to  Twitter Blog, Twitter Status, and Twitter’s Twitter feed. As of 11am EST there is no mention that the new Retweet feature will be removed from Twitter.com’s user interface.

So, if Twitter isn’t talking, what exactly is happening?

This lack of notification is not only inconsiderate to users that liked the new Retweet option, but it is downright rude to developers that have incorporated the new RT options in their programs. Attempt to retweet messages automatically in the new TweetDeck and you receive an error message. The incredibly handy RT icon featured in Twittelator Pro is now disabled. These options that developers spent time (regardless if it took a few minutes or a few hours) integrating into their apps are now rendered useless; and now they must return to their digital drawing boards to remove these options in order to keep their apps streamlined while maintaining stability and reliability.

And if this editorial/rant sounds as if I’m taking this slight from Twitter personally. I am. A bit. You see, the folks at Sams Teach Yourself Twitter in Ten Minutes offered me the opportunity to write for the next printing a brand new chapter featuring many of Twitter’s recent changes. Guess what was one update covered in that new chapter…

Thanks, Twitter. Thanks a lot for the heads up.

I liken this Twitter trip-up (Go ahead, you can call it a “twip-up” if you want to!) to a news story I saw this morning on how United States military surveillance drones — you know, those multimillion dollar robots our tax dollars pay for — were being hacked by Iraqi insurgents with off-the-shelf video software priced at $26. Considering the amount of technology, design, and intelligence that goes into one of these Predator drones, that is just plain embarrassing. So is Twitter — a landmark in modern communication — failing to notify users and independent developers “Yeah, we’re changing our mind on that whole Retweet tool…” While Twitter does have the prerogative to make such a dramatic change, they should at the very least extend a courtesy to the people utilizing their network that such a change will occur. There is no excuse for this kind of disregard. They have two blogs, a new “Notifications” feature on users’ homepages, and of course they have a Twitter account. Would a quick message to the 2,763,628 people following have been so hard? First “password” and now this?

Whiskey. Tango. Foxtrot.

Just when you thought I was done with TweetDeck v0.32.1…

TEE MORRIS’ TWEETDECK EPISODE
THE VIDEO PODCAST!

The audio is still the same, but now I have MOVING PICTURES to go with it! this is NOT going to be a regular feature at the Bird House, but when the mood strikes me, when the time allows, and when it is something that REALLY NEEDS the visuals, I will offer this kind of video addendum. I hope you all enjoy it!

Imagine That! Studios now presents to you the highlights of TweetDeck v0.32.1…in colour!

Featured movie and TV clips:

• Pirates of the Caribbean: Curse of the Black Pearl
  
• Iron Man
  
• Monty Python’s “Spanish Inquisition” sketch
  
• Firefly

Featured Resources on Twitter:

• “What’s New on v0.32″ from TweetDeck’s Support Forum
• Camtasia for the Mac
• LinkedIn
• Facebook
• YouTube.com

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!

Finally….after several attempts…after daring the Fates…after waiting for just the right time…and weathering an unseasonal snowfall in Washington, D.C.

TEE MORRIS’ TWEETDECK EPISODE!

This has been a long time coming, and I have decided to pull out all the stops and not only post a longer-than-usual BHR, but in the feed tomorrow and posting on YouTube as well will be an accompanying video companion to this podcast, filmed and edited on both Camtasia and the Final Cut Suite, bit-cheeezzz!

A labor of love and a lot to take in, here comes the highlights of TweetDeck v0.32.1!

Guest introduction by Coach Ian Scott

Featured movie and TV clips:

• Six Million Dollar Man
• Pirates of the Caribbean: Curse of the Black Pearl
  
• Iron Man
  
• Monty Python’s “Spanish Inquisition” sketch
  
• Firefly

Featured Resources on Twitter:

• “What’s New on v0.32″ from TweetDeck’s Support Forum
• Camtasia for the Mac
• LinkedIn
• Facebook
• YouTube.com

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!

It all started this morning when, from Twitter Status, this nugget of good news arrived, explaining the odd, intermittent service:

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

For those of you (like me) who didn’t know what a Denial-of-Service or DoS Attack was at the beginning of the day, you probably know what it is now. The U.S. Computer Emergency Readiness Team (CERT) defines a DoS Attack as the following:

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.

This attack didn’t stop with Twitter, though, as Wired Magazine gave confirmation that Facebook was 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.

And now from several news sources, Epoch Times cited in this column, the popular blogging site LiveJournal is also being hammered and hammered hard…

Popular blog site LiveJournal also confirmed that it had been hit by a DoS attack. The company said that an attack had occurred at approximately 6 a.m. Pacific time.

The denial-of-service attacks are the latest in a round of such attacks. In July of this year, several websites run by the U.S. government, the New York Stock Exchange and websites in South Korea were taken down by similar attacks. While North Korea was suspected to be involved in those attacks, analysts have indicated in interviews with The Epoch Times that it was most likely the Chinese Communist Party helping North Koreans with the technology to launch the attacks.

In no way am I suggesting that the sky is falling, but I will give a bit of thought to what David Grizzly Smith asked me after my original posting on this morning’s assault on Twitter:

Given the whole thing with #iranelection, think the State Department will investigate the DDoS?

I’m hoping that someone up on Capitol Hill is paying attention. No, I don’t think this is Social Media’s 9-11, but something is most definitely afoot. This isn’t just a fluke happening. To hit Twitter, Facebook, and LiveJournal is impressive in a particularly scary way. It will be some time before the dust clears until we discover the responsible party behind these attacks, but right now we must all remain patient and (above all) calm. The creators and developers of these Social Media outlets are all working to keep their services online. I also have faith that other administrators to other popular sites are preparing for similar attacks. We, as the consumers, must keep our own heads about us and not flip out.

Today’s a weird, weird day…but consider this: Tomorrow’s Friday.

UPDATE

From the Twitter Status blog:

Thursday, 4:14 p.m. Site latency has continued to improve, however some web requests continue to fail. This means that some people may be unable to post or follow from the website.

From the blog comments, Aline sends in word from the New York Times that Google was also hit in the DoS onslaught. The article goes on to comment:

But Bill Woodcock, research director of the Packet Clearing House, a nonprofit technical organization that tracks Internet traffic, said the attack was an extension of the conflict between Russia and Georgia.

It was not clear who initiated the attack, Mr. Woodcock said, but it was likely that “one side put up propaganda, the other side figured this out and is attacking them.” He said he found evidence that the attacks had originated from the Abkhazia region, a territory on the Black Sea disputed between Russia and Georgia.

Twitter is still a tag sluggish (although TweetDeck is running like a champ), but they are online and running. Remember, if your account starts acting squirrely, swing by Twitter Status and see what is going on back aboard the Mothership.

This was my first official interview for the title, and a terrific kickoff in promoting this latest title concerning Social Media. If you would like to have me on your podcast or would care to host a guest blog column with me, feel free to contact me here! Thanks for listening.