Cringely Borrows "A Cup of Bandwidth"

Robert Cringely is always fun to read. He does stuff that we all have done – or wish we had the nerve to do. In his April 14th article, he writes how he has “borrowed” bandwidth from his neighbors (details can be found here). A summary of his efforts is as follows:

  1. He helped his neighbors set up their wireless routers (WRT54G, of course).
  2. He informed them (during installation) that he would keep a “back door” avaialble – just in case they needed support.
  3. He exploited that back door to do some experimentation
  4. The experimentation is nothing exceptional. He put some antennas on his home and he connected to his neighbors routers. He used Vicomsoft’s Internet Gateway as a management tool and Sveasoft as the router software. Note: It’s not clear if he put Sveasoft on the neighbors router originally. If he did, I wonder whether or not he complied with Sveasoft’s licensing terms and conditions! 😉

All Bob’s efforts at authorized bandwidth theft aside, I wonder how many folks truly realize how insecure their wireless home networks truly are. I have written and delivered a number of presentations on the subject. Nevertheless, I am still amazed at how many people have wide-open access to systems that store their financial and personal information.
If you have a wireless network at home, please take extra steps to secure your systems. If you need help, drop me a note or check out the following sites:

  • Microsoft has some good articles that offer hints.
  • PC Mag has a bunch of articles. Here is a good start.
  • Check out Practically Networked guide on the subject.
  • Check out About.com’s guide. I used parts of this guide for a recent KCCMG presentation. It is simple and executable for most computer-literate folks.

-CyclingRoo-

HyperWRT Manual – Now on a Wiki

Avenger has just released his HyperWRT manual – in the form of a Wiki. I’m gonna start adding (or modifying) content – but probably not for a couple of days. In the meantime, I wonder how many folks are using wikis for collaborative electronic manuals. I know it’s the “in” thing to do. But I wonder if a) general/basic customers will use such documentation, b) how document consistency can be strictly enforced, c) whether or not this consistency breaks down with large numbers of contributors, and d) whether there are any special documentation “quality control” steps that should be applied for any “customer-facing” documents. Any insightful comments would be greatly appreciated.
-CyclingRoo-

Even Leaders Need to Take a “Leak”

You know it’s bad when the Three Stooges analogies start to emerge. In the proprietary software world, folks love to point fingers at Larry Ellison, Scott McNealy, and Bill Gates. And if the analogy is supposed to mean that these three men have done some incredibly bone-headed things (amidst all the great things they’ve accomplished) , then the analogy may have merit.

But now the open source community has its own set of humorous “bunblers.” In a recent article, the Register points to Larry, Mungo and Tridge. In this case, we are talking about Larry McVoy (BitKeeper proprietor – and not an open source luminary), Linus Torvalds (Linux uber-geek) and Andrew Tridgell (Samba leader and Bitmover reverse engineer) . Added to this august trio is Bruce Perens (open source maven and former HP exec) who threw a few barbs in Linus’ direction over his recent “Tridge-trashing” comments.

So what’s up with these folks. Well, I won’t spend a lot of time, but here are the highlights:

  • Linus was having trouble coordinating all the changes that were going into the Linux kernel. So he worked a deal with Larry McVoy to move the kernel development from a cvs-based system to BitKeeper (a proprietary system). This decision was not met with unanimous consent. Indeed, it resulted in quite a furor within the community. But Larry worked a deal so that the Linux developers could have a limited license through the use of gateway technologies.
  • Tridge decided to start a pet project to reverse-engineer the Bitmover / BitKeeper “on the wire” protocols. BTW, this is exactly how Samba started – and exactly what Samba accomplished regarding Microsoft’s SMB implementation.
  • Larry took offense at the reverse engineering and decide to pull the license under which kernel development was proceeding.
  • Linus began to raise the issue of how best to conduct kernel development given the BitKeeper license changes prompted by these problems. That question is not yet resolved. But in the meantime, Linus has made some highly inappropriate comments concerning Tridge and his character.

Once Linus began his very public commentary, things got quite heated. Tridge is being conspicuously quiet (probably because of legal concerns over Bitmover). Since Tridge won’t speak, others are stepping up to his defense. As noted earlier, luminaries like Bruce Perens are even starting to speak up.

I will not comment upon the people (or their conduct and comments) in this unfortunate mess. But I will note that this proves that all people can make mistakes – regardless of how luminary these people are.

All of this reminds me of a few scenes from Star Trek: First Contact. In that movie, the Enterprise is thrown back in time. While in the past, they meet the “inventor” of the warp engine. As the crew from Enterprise are working to prepare the very first human warp craft (that will be flown by Zefram Cochrane), many crewmembers start to talk about Cochrane and his accomplishments. There is even the off-hand discussion about “first-year Academny” warp mechanics classes that were inspired by the events that were about to occur. During all of this reminiscence (and downright idol worship), we hear Cochrane utter the following: “You think I want to go to the stars? I don’t even like to fly–I take trains.” And at one point, Cochrane is trying to hide from all the intense adulation. But he is found by Geordi while he is taking a “leak.”

Sometimes, I think we treat the open source leadership like the Enterprise crew treated Zefram Cochrane. We forget that these folks are normal people who sometimes do human things (like take a “leak”). Hopefully, this will all turn out well. But I have always found that the best way to overcome such human frailties is to offer something extraordianry and altogether super-human: forgiveness. A number of community leaders probably need to step back and humbly ask for (as well as offer) forgiveness. Not to the community, but to each other. Too bad that the open source community does everything in public view. This “openness” may make such displays of contition quite difficult. So let’s give these men the time and ability to be real leaders.

-CyclingRoo-

Even Leaders Need to Take a "Leak"

You know it’s bad when the Three Stooges analogies start to emerge. In the proprietary software world, folks love to point fingers at Larry Ellison, Scott McNealy, and Bill Gates. And if the analogy is supposed to mean that these three men have done some incredibly bone-headed things (amidst all the great things they’ve accomplished) , then the analogy may have merit.
But now the open source community has its own set of humorous “bunblers.” In a recent article, the Register points to Larry, Mungo and Tridge. In this case, we are talking about Larry McVoy (BitKeeper proprietor – and not an open source luminary), Linus Torvalds (Linux uber-geek) and Andrew Tridgell (Samba leader and Bitmover reverse engineer) . Added to this august trio is Bruce Perens (open source maven and former HP exec) who threw a few barbs in Linus’ direction over his recent “Tridge-trashing” comments.
So what’s up with these folks. Well, I won’t spend a lot of time, but here are the highlights:

  • Linus was having trouble coordinating all the changes that were going into the Linux kernel. So he worked a deal with Larry McVoy to move the kernel development from a cvs-based system to BitKeeper (a proprietary system). This decision was not met with unanimous consent. Indeed, it resulted in quite a furor within the community. But Larry worked a deal so that the Linux developers could have a limited license through the use of gateway technologies.
  • Tridge decided to start a pet project to reverse-engineer the Bitmover / BitKeeper “on the wire” protocols. BTW, this is exactly how Samba started – and exactly what Samba accomplished regarding Microsoft’s SMB implementation.
  • Larry took offense at the reverse engineering and decide to pull the license under which kernel development was proceeding.
  • Linus began to raise the issue of how best to conduct kernel development given the BitKeeper license changes prompted by these problems. That question is not yet resolved. But in the meantime, Linus has made some highly inappropriate comments concerning Tridge and his character.

Once Linus began his very public commentary, things got quite heated. Tridge is being conspicuously quiet (probably because of legal concerns over Bitmover). Since Tridge won’t speak, others are stepping up to his defense. As noted earlier, luminaries like Bruce Perens are even starting to speak up.
I will not comment upon the people (or their conduct and comments) in this unfortunate mess. But I will note that this proves that all people can make mistakes – regardless of how luminary these people are.
All of this reminds me of a few scenes from Star Trek: First Contact. In that movie, the Enterprise is thrown back in time. While in the past, they meet the “inventor” of the warp engine. As the crew from Enterprise are working to prepare the very first human warp craft (that will be flown by Zefram Cochrane), many crewmembers start to talk about Cochrane and his accomplishments. There is even the off-hand discussion about “first-year Academny” warp mechanics classes that were inspired by the events that were about to occur. During all of this reminiscence (and downright idol worship), we hear Cochrane utter the following: “You think I want to go to the stars? I don’t even like to fly–I take trains.” And at one point, Cochrane is trying to hide from all the intense adulation. But he is found by Geordi while he is taking a “leak.”
Sometimes, I think we treat the open source leadership like the Enterprise crew treated Zefram Cochrane. We forget that these folks are normal people who sometimes do human things (like take a “leak”). Hopefully, this will all turn out well. But I have always found that the best way to overcome such human frailties is to offer something extraordianry and altogether super-human: forgiveness. A number of community leaders probably need to step back and humbly ask for (as well as offer) forgiveness. Not to the community, but to each other. Too bad that the open source community does everything in public view. This “openness” may make such displays of contition quite difficult. So let’s give these men the time and ability to be real leaders.
-CyclingRoo-

FF 1.0.3 – Where the Hits Just Keep On Coming

As reported yesterday afternoon:

The Mozilla Foundation today released updates to two of its main products, the Mozilla Suite and Firefox. This marks the third round of security fixes for Firefox, along with the seventh minor update to the 1.7 version of the Mozilla Suite. Security issues fixed in these new versions are listed on the Known Vulnerabilities page with detailed descriptions of each issue.

So I’ve updated – and added another few downloads to the counters. Man, I wonder what the real stats are for unique downloads. Oh well. We’ll see more details as web sites report unique visits by Firefox users. In the meantime, you can get you copy here.
The security fixes are as follows:
MFSA 2005-33 Javascript “lambda” replace exposes memory contents
MFSA 2005-34 javascript: PLUGINSPAGE code execution
MFSA 2005-35 Showing blocked javascript: popup uses wrong privilege context
MFSA 2005-36 Cross-site scripting through global scope pollution
MFSA 2005-37 Code execution through javascript: favicons
MFSA 2005-38 Search plugin cross-site scripting
MFSA 2005-39 Arbitrary code execution from Firefox sidebar panel II
MFSA 2005-40 Missing Install object instance checks
MFSA 2005-41 Privilege escalation via DOM property overrides
I don’t yet have the scoop on whether these bits include Asa’s “Popups Must Die” ad block improvements. I’ll double check and report later.
-CyclingRoo-
===Update===
The relevant string did not exist in about:config after install. So I added the following: privacy.popups.disable_from_plugins with a string value of 2 (it accepts 0,1,2, or 3). Things are blocked quite nicely now.

5.3 Million iPods Sold in 1Q05

Apple dropped its sales bomb – and it’s a big noisemaker. According to published results, Apple sold 5.3 million iPods during 1Q05 (second quarter of the Apple fiscal year). But the thud came in the form of the revenue drops associated with the increased sales. Overall, iPod revenue per unit dropped by 16%.
Why the difference? Well, Apple didn’t provide enough information to make the reasons clear. Indeed, Apple made it a point _not_ to report where the revenue came from. So increased iPod sales and decreased revenue probably was a result of a major (and possibly unexpected) shift in iPod purchasing habits. By that, I suspect that iPod Shuffle sales were far higher than expected. That is good. But the sales were not (exclusively) incremental unit sales. Rather, iPod Shuffle purchases may very well have displaced iPod mini, iPod, and iPod Photo sales – thus damaging revenue projections. And the fact that Apple did not report the results per product in the iPod family lends credibility to that assertion.
If my speculation is correct, then Apple may be faced with the good news before the bad news. The good news is the unit sales increases. But if the sales were for the Shuffle, then the bad news is that they shifted their market towards the more commoditized end. This is good and bad. If true, expect the other flash player manufacturers to step up the competition. In this end of the market, Apple does not have a feature or price advantage – only a brand advantage.
So I expect other suppliers to ramp up competition. And I expect Apple to shoot back with something new. I expect the knee-jerk response to be some form of firmware update to provide more distinctiveness (and brand allegiance) to the Apple iTunes family. But I am having difficulty guessing what that might be. Given the current design, there is very little that can be done on the player side. But I wonder if there might be something to be done with iTunes or at the ITMS channel. Again, this is just speculation. But expect to see something (e.g., a new rev?) soon and expect folks like Samsung to ramp up the price pressure on flash-based players.
For more information on the subject, check out Jupiter Research’s entry on their Microsoft Monitor site. Jupiter expects a very serious push by the PlayforSure crowd. I just love it when competition makes things faster, better and cheaper!
-CyclingRoo-
-Update-
Apple stock took a pounding despite the amazing sales results. Maybe other folks are curious about the 16% revenue decline as well.

The Second Coming of Microsoft Smart Tags

Mark Twain was right. History does rhyme. And my variant on Samuel Clemens quote is that history not only rhymes – it now riffs (or maybe it’s a cover song)! This time, I’m hearing the notes of the smart tag song once again.
For those with short memories, I’ll play a few notes. In early 2001, Microsoft announced its Hailstorm initiative as well as its Smart Tags features for Windows XP (and Office XP). I won’t go into too many details – especially since I’m not an expert on the subject. But the heart of these technologies was a coupling of web services (via XML and SOAP) and smart-tagging. The industry (i.e., the open source community and many web developers) screamed “foul.” Specifically, folks felt that it was absolutely criminal for Microsoft to “edit” content by adding tags that weren’t provided by the content author. BTW, I was one of those screaming about the “arrogance” of Microsoft acting as a content editor.
Today, we are now talking about tags once again. All of us are thrilled by Flickr, Del.icio.us and other tag-centric content modification approaches. And lots of us are thrilled by the Greasemonkey extension for Mozilla Firefox – even the staid Jon Udell.
So what’s my point? Everything old is new again. Greasemonkey is doing exactly what we screamed at Microsoft for doing. Well, sort of. Greasemonkey is different because it places content control in the customers’ hands – not a corporation’s hands. The customer must implement the scripts that would modify the content. In this regard, the ethics are quite different than the Microsoft Smart Tags proposition. But the technologies are quite similar.
And if the big content providers release their own versions of Firefox (as both Yahoo and Google are rumored to be doing), then we must watch these folks quite carefully. It would take very little work to include Greasemonkey and a bunch of scripts into a browser. And such amplified browsers would be capable of doing exactly what we screamed at Microsoft for talking about.
So the issue of content modification and ethics needs to remain a concern for the open source community – lest we engage in the same things that we scorned others for. Simon Willison has the makings of a good start on the subject. Let’s keep the discussion going!
-CyclingRoo-

Nanotech Used for Product Coatings

Just when you thought the materials industry was starting to slow down, you run across another really cool innovation. Ecology Coatings (Akron, Ohio) has announced that DuPont will be licensing its nanotechnology coating system. I love the way Ecology Coatings refers to its products. They produce curable liquids that are 100% solids! Sounds like a marketing term, right? Right. But here are the features: fast-drying (3 seconds vs. twenty minutes), no evaporation and/or fumes, no need for solvents and/or carriers. In addition, UV curing consumes about 75% less energy than heat-based drying schemes. In short, this stuff is far more environmentally friendly than traditional industrial coatings.
The potential applications are numerous. DuPont is envisioning the product for use in automobile finishes. Other companies are considering licensing the coating as a screen to apply to other materials. For example, Nano-Tex (a competitor) uses their coatings to prevent socks from absorbing foot odor. Other applications include rain-repellant (or bullet resistant) cloth.
This stuff is pretty cool. And it’s important to note that DuPont is the company that brought us Teflon coating. They know about how to market coatings for an incredible diversity of applications. Indeed, DuPont has been a pioneer for nanotechnology on the future battlefield. I wonder just how much it will cost!
-CyclingRoo-

Success In Carbondale

It’s been three days since my last post. So I’ve been a very naughty boy. I have not had a chance to blog since Friday. Dana and I spent all weekend in Carbondale, Ill. But we were at a Motel 6 w/o any connectivity. Worse still, I couldn’t find free WiFi access anywhere. I am sure that if I cruised through Carbondale with NetStumbler going, I would have found something. But there just wasn’t any time.
So why was I in Carbondale? My daughter Dana was involved in an AAU basketball tournament. The winner of the tournament got an automatic berth to the AAU Nationals (to be held in Orlando this summer). So Dana and I headed out from Kansas City on Friday afternoon. She drove for 6.5 hours and we made it into Carbondale while there was still fading daylight.
The campus at Southern Illinois is great. The gyms were nice with a few minor challenges (like ventilation and clocks). The competition was pretty fierce. We were in the 16U brackets. There were five teams in the bracket. So Saturday was pool play. Our girls played an Illinois team (the Titans), a central Missouri team (the Lady Jazz), and an Indiana team (the Elite). We went 2-1 on Saturday. The Titans put up a good challenge, but fell flat in the second half. The Lady Jazz rallied from a first-half deficit to squeak out a narrow win. And the Elite fought hard until the very end. So Saturday was a good chance to focus on teamwork and trust. The more games these girls play together, the better they are becoming!
When Dana and I got up on Sunday, we were greeted with the news that our final pool play game had been cancelled. We were set to play the Kansas Belles at 10:00. But since the result was only going to determine which of the two would have home court advantage at 1:00, both teams decided to bypass the final pool play game.
So we met the Belles in our bracket semi-final. The Belles were also 2-1 from the previous day. Their only loss had come at the hands of the Lady Jazz. So our 1:00 match-up was very telling. At the same time, there were some personal reasons for this game. About half of our team had been on the Belles at one time or another. So we faced off against friends. But that’s the great thing about amateur athletics. It is supposed be friendly competition – and it was. But when the tip-off whistle blew, both teams came out wanting the win.
Dana had a great start but still struggled at the free throw line. She was hitting around 50% from the charity stripe – and she wasn’t happy. But her interior play was strong. And she put the Belles strong post player (Jadhon Kerr) into early foul trouble. Boy, that was tough. We love Jadhon and her parents. But Dana knew she would need to drive on Jadhon. Eventually, Dana fouled her out. But after the game, Jadhon and Dana hugged. And Jadhon’s mom (also named Dana) promised to pray for our game against the Lady Jazz. I love friendly competition – especially between good families!
So the 3:00 championship game was between Team Excel and the Lady Jazz. We had lost to the Jazz just one day earlier. So this was going to be a tough game. And the venue managers didn’t help. They delayed the game until 4:00. In fairness, this was a good decision. It gave both teams a chance to cool off and revitalize. But it put us another hour later. Win or lose, the trip home was going to be very late.
So Dana took the extra time to work on her free throws. And Todd (her coach) was great. He recognized that the trouble was mental and not mechanical. So he told Dana that she wouldn’t be allowed to go through her typical free-throw ritual (three bounces, a head bob and the shot). She would have to step to the line and shoot without thinking. Dana agreed. So the extra few minutes was good for Dana.
Both teams started well. But since this was the championship game, there were some nerves. After all, the winner of this game would earn a berth to the AAU National tournmament. Once the teams got past the jitters, the game got very serious. Dana was relentless in driving to the net. I wasn’t tracking points (since I’m the designated cheerleader – and I can’t see anything anyway). But she went to the charity line three times in the first half and came away with six points. So Dana finished the first half with some unspecified number of points and 100% free throw shooting. At half-time, we were ahead by six points.
At the beginning of the second half, the Jazz keyed on Dana. They double-teamed her. So she went to work on the inside-outside game. They would collapse on her and she would dish it off for an easy score by her teammates. Everyone got in on the act. Shaylyn, Amanda and Taber were dropping in points from the outisde while Marissa and Ashley kept things exciting inside. Even our newcomers (Hadleigh and Kelley) made a big difference. They were able to find (or make) the openings whenever they turned up. It was great to see this “total team effort” from such a young squad! And when our outside shooters got really hot, the Jazz team shifted their defense. So Dana found herself open on the block and really kicked in some points. In the end, we won by almost twenty points. The Jazz were strong, but our girls were even stronger on this day.
So the drive home was great. Everyone was smiling and hugging each other when we left the gym. And winning always makes a six hour drive more bearable. Dana still needed to drink a couple of Amp drinks (caffeine + sugar). But she drove home as well as she drove to the net.
So it’s now “off to nationals” in July. In the meantime, there are a few more tourneys where we can hone our skills and breed confidence in every player. All in all, this was a great weekend for a team that has only played together for three weeks!
-CyclingRoo-

CastBlaster & PodShow

It is amazing to experience technology changes as they are occuring. Over the past six months, podcasting has started to take off. According to Pew Research, there are over six million podcast listeners on the Net. And there are a bunch of folks that are jazzed about the kinds of social and commercial changes that this medium will spawn.

And these millions of listeners are using lots of different pieces of software. On the Windows platforms, you have iPodder and Doppler as the principal podcatching clients. On the Mac, there are plenty of other tools including iPodderX. And these tools are very good.

But Adam Curry wasn’t happy with just good podcatching software. So he and his development team have been working on podcasting production software. On yesterday’s Daily Source Code, Adam demoed his new production software which he is dubbing “CastBlaster.” From the sounds (and sights) of the software, it looks really good. I am getting excited to try the software – whenever the beta is released.

Of course, I have no idea whether the “studio” software will be proprietary or open source. I would guess that it would be open source. After all, I am sure that he will be using existing open source software as a basis. But I do think that Adam wants to monetize this – but through the “services” angle. In December, he registered the domains for the PodShow. And recent DSC podcasts have hinted at the launch. There is a functioning web site (with little to no content) and lots of hints. I don’t know where this is going, but I suspect that Adam wants to start a “network” of podcasters. On that network, he can charge “rent” (storage space) and collect his “cut” of advertising revenue. In a way, he is building an “MTV” network all over again. But this time, the talent will be far more decentralized – and geeky.

Rick Turoczy talked about this on his “hypocritical” blog. At the same time, Christopher Carti talked about this on his Social Customer Manifesto blog. Both seem to predict big things for the venture. If buzz could kill, this would be homicidal!

-CyclingRoo-