The Recycling Bin is an enabler for the indecisive
Windows 7 shaped up pretty nicely as expected, much as I’d like to have seen a cleaner interface for it with less screen real estate wastage. The RTM code trundles along quickly on just about anything with no drama, which is how I suspect most potential Windows customers like it. There are many new things in Win 7 though, if you’re a Win2K or XP holdout who has skipped Vista. Windows 95 was a similar big jump from Windows 3.x, and at that time, Microsoft was kind enough to put together training videos featuring none other than Jennifer Aniston and Matthew Perry. What do you mean “who they?” Part 4 is the shortest and least painful to watch. — Matthew Perry and Jennifer Aniston: Windows 95 guide Parts 1 to 4 Part 1 Part 2 Part 3 Part 4
Hit the road, LoJack
One incredibly fascinating aspect of information technology is how just about all of it can be subverted in the hands of its human users. Even the supposedly good stuff: about a year ago, the US Federal Trade Commission (FTC) warned about laptops disappearing at US airports, to the tune of over 10,000 a week. That’s a fair few, so what to do? The FTC advised that you should install low-level tracking programs like Absolute Software’s CompuTrace LoJack that operates from the computers’ BIOSes (that basic piece of code that gets things going). LoJack is able to “phone home” over the internet, and report its location, in case the laptop is reported stolen. Great stuff, you’d think, and apparently, so did the big laptop vendors. Apparently, over 60 percent of laptops have LoJack installed. What if LoJack isn’t secure though, and is in fact a HiJack tool that can be exploited by malevolent people to take over your computer remotely? Oops. In other words, relying on technology without understanding it just plain dangerous still. — Researchers find insecure BIOS 'rootkit' pre-loaded in laptops — Absolute refutes claims of BIOS vulnerability — Laptops lost like hot cakes at US airports
By the power of ComCom
Something remarkable happened this week: a relatively innocuous story was published in the National Business Review about telco regulation. It was a nice scoop by Chris Keall (pictured, chinwagging), but it was the Commerce Commission putting the legal kibosh on it is most noteworthy. More than noteworthy, in fact, because nobody I’ve spoken to can think of a similar precedent where the Commission has silenced the entire media of New Zealand. However, it seems the ComCom can, and will, exercise its ability to use “reasonable force” and its seemingly wide-ranging powers. The decision to censor NBR seems very heavy-handed and illustrates how poorly protected freedom of speech is in New Zealand. The Commission didn’t even have to go and get a court injunction as in most other democratic countries to order the story taken down. This really isn’t acceptable, commercial sensitivities notwithstanding.
As it happens, the censored NBR story has hit Wikileaks already, so it’ll be interesting to see if the ComCom is able to order the suppression of the story now that it has gone overseas. At the heart of the matter is a confidentiality order that says only authorised people must know about the deal between 2 Degrees and Vodafone. Any un-authorised publication of that information is apparently punishable with fines of up to $12,000 a day. I would imagine Vodafone will be fined for breaching the confidentiality order as it has now decided to offer the 2 Degrees deal to other comers as well. — Making sense of ComCom's non-publication order —Information freeze on 2 Degrees deal
Supported featuresCartoon: www.xkcd.com
Robert X Cringely Twitter harpooned, Internet survives (just barely)
The attack on Twitter shows not only how vulnerable the microblog is, but also how dependent we've become on it. That's a dangerous combination. Maybe you didn't notice, but yesterday was International Anti-Tweet Day. Twitter, the microblog most people either love or hate, disappeared from the internet for a few hours yesterday morning, then popped in and out for most of the afternoon. As MediaJobsDaily put it: "Twitter wasn't just down, it was so down that you didn't even see a Fail Whale when you tried to load the page. Down and dirty down. Downer than down. That's how down it was." But this time Twitter didn't go down for the usual reason: being unable to keep up with the volume of tweets. This whale of a fail was due to a deliberate attack that also affected Facebook, Live Journal, and Google. Today security experts are still scratching their heads over why the attacks happened. IT Harvest's Richard Stiennon suggested hackers were steamed that Twitter had stolen the shine from their own preferred methods of micro-interaction, IRC and ICQ. (Richard, I love ya, but ... hacker jealousy? Really?). AVG's Roger Thompson thought white-hat vigilantes launched the attack to point out the dangers of botnets (because there have only been, oh, a few thousand examples of this already). He also thinks the attacker was the same one who's been pelting U.S. and South Korean government sites with malicious packets. (Damn. I knew I shouldn't have tweeted those snarky jokes about Kim Jong-Il. My bad.) Those jokers over at eSarcasm also list 22 other reasons why Twitter may have failed. I think they may need to adjust their meds. Here's the theory that was thrown at the wall and seems to have stuck: According to an account first published in Cnet, Facebook top security dog Mark Kelly says the entire fiasco was a coordinated attack aimed at silencing one person from the Republic of Georgia who goes by the handle "Cyxymu," after the Georgian city with the same vowel-challenged name. Sophos security wonk Graham Cluely gives more heft to this idea, noting that today is the first anniversary of Georgian troops moving into South Ossetia, which triggered a brief and disastrous war with Russia. The New York Times quotes Bill Woodcock of the Packet Clearing House, who says the packet storm originated from IP addresses in Abkhazia, a disputed territory between Russia and Georgia. He attributes the cause to spam, not a botnet. So Cyxymu clearly ticked off the wrong Russians. We got that. But 30 million users taken offline, security teams at Twitter, Facebook, and Live Journal scrambling to fend off the attack, all just to get one guy? That's the really chilling part. The other big story that emerges from this is how dependent many of us have become on social media. It's not just folks who live or die by their favorite celebrity tweets. (FYI, Paris Hilton spent yesterday at the beach, where she collected "many beautiful shells," while Paula Abdul continues to shower in "the undying support and enormous love" of her fans. Now you're all caught up.) Hundreds of startups are entirely dependent on Facebook and Twitter. As Fast Company's Chris Dannen writes: "If you think the combined stuttering of Twitter, Facebook and LiveJournal this morning...were rough for you, well, try dipping into the shoes of the developers who make software based on Facebook and Twitter APIs. Sure, you missed all of Ashton and Demi's tweets for a few hours. But for devs, the two goliath social networking services are their livelihoods. And what's surprising is how Facebook and Twitter left them completely in the dark." Job seekers, Web marketers, reporters, customer support teams, political protestors in oppressed countries — the list of folks who rely on Twitter is long and not entirely frivolous. Like it or not, in a very short time Twitter has become very important. As uber-MILF Brooke Burke told the Wall Street Journal, when she sent her usual morning tweet yesterday and never got a response, she was stunned: "What is going on? Why isn't anybody responding? Why have I not gotten any tweets? It is just not normal." she recalls thinking. "It almost was like having no phone service." Twitter is not Ma Bell ... yet. But one day it could be — so long as the Russians (or the Koreans, the Chinese, and the hackers down the street) don't take it down first. What did you do when Twitter's lights went out? Post your thoughts below or e-mail me: firstname.lastname@example.org.