This is such a bad idea for blocking Internet porn I am nearly speechless

Go take a look at http://www.cp80.org/ and see if you can collect the numerous technical reasons that assigning Internet port numbers for particular content (meaning porn and other things that kids shouldn’t see) is such a bad idea. Silly wabbit, ports are for protocols, and last time I checked, protocols don’t care about content and shouldn’t. Not only is it too much work to completely redesign TCP/IP to address this hairbrained scheme, but it is doomed to fail even if you could.

And too bad port 69 is already taken for something really ironically useful (you get extra points if you know off the top of your head what it is).

Let’s get that .xxx TLD going, not that that is much of a solution, either. Any solution is going to be more parental than technological, anyway.

Favorite comment from Annalee Newitz: The group “sadly isn’t a phalanx of uptight androids who enjoy mysteriously homoerotic relationships with mailbox-shaped companions.” Doesn’t that bring something to mind? What a wasted effort.

Things to read this weekend, 2: The year’s stories in review

Everyone has their top ten lists about this time. My former Tom’s Hardware news hound colleagues, Wolfgang Gruener and Scott M. Fulton, have put together what I think is one of the best collections on the year’s top stories in review.

From the revival of Apple, the mis-steps of Sony BMG, the rise of the Xbox 360, and the fight over HD DVD formats, this piece makes for a compelling review of where we have been over the past year.

Learning how to work the Web from Hef

Yes, I’ll admit that I read Playboy.com only for the articles. And earlier this month I had a chance to get up close and learn from Christie Hefner herself. The CEO of Playboy Enterprises was in town for a conference preaching digital entertainment to a bunch of old-world TV types and Web wannabies. Her speech was on how she has extended the world’s most famous rabbit logo into cyberspace and how she continues to make hay from those centerfolds, I mean, excellent articles.

I came to the keynote a bit skeptical about what Hef’s daughter could tell me about online media. But by the end of the hour I was impressed with her knowledge and common-sense lessons that she and her company have learned from running one of the most popular Web destinations for the past decade. Her words (and a few pictures too, I won’t deny that she is good with the illustrations on her PowerPoint slides) struck a very resonant chord with me.

You can read more about what Christie Hefner had to say here.

Sony BMG Sounds A Sour Note

It is bad enough trying to keep your computer free of viruses, spyware, and those annoying pop-up ads that can download even more nasty stuff to one’s hard drive. Now we have to beware of music CDs and their associated software that comes along with the tunes. It is sending another sour note in the music industry, a sad song indeed.

At least one of Sony’s music CDs comes with special rights management software from a company called First 4 Internet. The software came with the CD from the Van Zants called <i>Get Right with the Man</i> (ironic title completely unintentional).

The software is used to play the music files from the CD and monitor how the music is used by the PC, ostensibly to prevent digital copying and ripping the music. Sadly, the software does more than that, including burrowing deep into your Windows OS and purposely disguising itself and hiding its executable files from plain sight. Worse yet, the software steals performance from your computer in doing its bidding. Even more ironically, the software is Windows-only, meaning that you can still rip the tunes on your Mac without having to worry about having this code enter your system.

The security researcher who uncovered this sad state of affairs, Mark Russinovich, continues to dig deeper this week as Sony backpedals and offers half-baked fixes to the situation. As he mentions on his site, “the EULA does not disclose the software’s use of cloaking or the fact that it comes with no uninstall facility.” Before the story broke, there was no way to remove this code without knowing a great deal about where it was located and how to uncover it. I guess that is part of the design: after all, why would you install a rights management client if you could easily remove it? But people don’t install DRM, big faceless corporations that want to continually grab your wallet do.

Unfortunately, that Catch-22 is at the basis of why digital rights management will ultimately fail, just as every other digital copy protection scheme has failed in the past. While most people don’t care, and just want to play their music, music I might add that they have legitimately purchased, those that do care will spend the extra time like Russinovich and go to great lengths to remove it from their systems. And it isn’t because they want to become digital scofflaws. They just want to get access to their music files without any associated baggage, and play their tunes where and when they want to.

What makes matters worse is how Sony is dealing with the situation, and how they continue to get caught up in their copy protection. There are three big lies here. First is how they are not being upfront in their EULAs  (not that most of us read this documents anyway, but still). Not being upfront on their Web pages dealing with the matter is the second:

“The protection software simply acts to prevent unlimited copying and ripping from discs featuring this protection solution. It is otherwise inactive. The software does not collect any personal information nor is it designed to be intrusive to your computer system.”

Not according to my reading of the situation. Code that takes away a couple of percentage points of CPU performance is not what I would call inactive.

But the final straw is issuing a “uninstall patch” that doesn’t really uninstall the code. The tool that Sony has posted on their Web site last week doesn’t remove anything, but just reveals the files and updates its DRM code with something even more heinous. This won’t do. Sony needs to face the music, as it were, and stop meddling with my machine.

When I buy a CD (and I do buy them from time to time), I don’t want anything extra coming along for the ride. I want access to my music in my car, at work, at home, and on any of the various digital devices that I currently listen to. I want to make backup copies because CDs aren’t indestructible and they do wear out, especially since I leave many of them in my car. I don’t want to be treated like a common criminal, nor do I wish to infect my PC with something that will sap its performance and communicate back to Sony what I am listening to.

It is ironic that contemporaneously with Sony’s actions, the TV industry is getting its act together and selling more programming to people who will gladly pay a buck an episode. Disney started this ball rolling, and this week other networks announced they will get on board and make it easier for people to download content. There is a lesson to be learned from the video studios that the music industry could learn. How much piracy would go away if we would could pay 25 cents a song?

It was bad enough when the lawyers of the recording industry went after teenagers and others for participating on peering networks. It was bad enough when people and businesses that I don’t know are trying to grab my bits and deposit their digital crap all over my PC without my knowledge or agreement. Now Sony is coming after my hard drive. As I have said before, Sony, and the rest of the music industry, needs to back down and treat its customers properly, or we will all go away. You could say they need to get right by the Man before the Man goes elsewhere. I know I will think twice the next time I buy a CD. Or at least run it on my Mac.

I Want My Airline Seat!

We live in the era of instant gratification. We have instant messaging, instant soup and coffee, instant relationships and even instant lottery winners. And, of course, there’s no place better to get instant gratification than when you buy something online, and can get it NOW.

But what I like even better than the instant rush about online purchasing is the ability to see my choices from inventory in real-time, or as close to real-time as possible.

Get more information about choosing your own airline seat in my column here.

What happens when you forget your site password

Website passwords are becoming more of a problem, as more of us use a wider number of sites to conduct our daily business transactions. The issue is that the security filters to recover lost passwords are seriously broken, and are biased towards people that frequently return to sites. But think about it. The more often you visit a site, the more likely you are using (hence remembering) the password. The very users that password recovery systems are supposed to help are left in the cold. People’s electronic lives aren’t static, and the password recovery programs can’t keep up as we move about the physical world, change e-mail addresses, and forget which piece of critical data will be used to authenticate our electronic personas.

Consider this situation from one of my correspondents, an experienced computer scientist. She was recently asked to login with her username and password and couldn’t remember either when she went to buy something at eBay.

Find out more here

Finding the Right Co-Location for Your Web Server

The trouble with optimizing your Web server location is that the Internet isn’t easy to pin down. It isn’t like you are trying to open up a store on a downtown street or near a freeway exit. The fact that your public can be located anywhere in the world and on any network is just one small part of the challenge. Other issues include hazy definitions for such terms as backbone, peering point, primary providers, and network access points. It would help if these were commonly understood and used by the majority of people you talk to, but they aren’t.

This article was written back in for a great online pub called 8Wire that is sadly no longer with us. Luckily the HTML lives on here.

cnet: The quick and dirty Intranet

[NOTE: this story was one of the first that I wrote for c|net back in 1996. It is provided as a snapshot of history.]

Here is a quick and easy way to build your Intranet, and it doesn’t require adding IP to every desktop or even having to put up any web servers. 

I used to think that the term “Intranet” applied to those internal web servers popping up all over userland: not visible to the rest of us from the outside Internet, they serve up pages of human resources’ manuals and last quarter’s financials. 

Well, that is part of what Intranets are all about: but there are circumstances when you don’t want or need a web server and you can still have a perfectly good Intranet. You may not have the expertise to deploy a web server right now, or may not want to put IP everywhere. You already have people that are skilled in running NetWare servers, and don’t really want to learn yet another server operating system (like Unix or NT). Finally, if you are tired of hearing how everyone else has their own web server, there is a way to get started without waiting any longer.

You have come to the right place. Here’s how you do it.

Take your existing NetWare file server (come on, admit that you still use ’em). You don’t have to do anything to it for now. But if you want to connect it eventually to the Internet, then you’ll want to consider one of the products mentioned in the box below. You will have to re-write your files in HTML to make your documents on the server web-friendly. 

You can either add an IP stack to your desktops, or else modify the WINSOCK.DLL (if you are running Windows) to talk through IPX. Novell includes this as part of their IntraNetWare solution, or you can make use of the products mentioned in the box. 

Now, run your web browser. Tell users to bring up their web pages using the “open file” command instead of typing in an http: address. Guess what? That’s it — you have your Intranet and no web server in sight.

Indeed, you actually aren’t missing much: your users can still traverse links embedded in your documents, but they are file-based instead of web-based links. You can still load up your pages with images and sounds, provided your links refer to mapped drives on your network (file:///G|\document instead of http://servername/document). 

Okay, so what is the catch? Well, you can’t do a few things: You can’t run CGI programs and perl scripts, and that means that forms will be pretty tough to do. But who cares — most people don’t really want to fill out forms anyway. And you can’t track how people move through your web since you don’t have any log files. But so what — who really has the time to write scripts and analyze these logs anyway? (I am being somewhat cynical here: I actually think logs and forms are very important and key to understanding how you need to evolve your web. But we’ll leave those issues for another day) 

I think this strategy makes perfect sense. It is also somewhat timely, given Novell’s big push this month to package its various pieces of software under the “IntraNetWare” label. The key is beginning to use HTML as your corporate document standard.

That will take some doing: most of your documents, I’ll bet, are in Word or some other word processor, and getting them converted won’t be easy. 

Another suggestion: consider getting a few Macintoshes and using them to add the multimedia experience to your file-based webless Intranet. Why Macs? They have the best tool set for adding images, sound, and video to static text. And since you’ve already got your NetWare file servers, they can see them just fine (as long as you load the Appletalk support properly, which is fairly easy to do.) 

I can see another situation where a non-web Intranet  makes sense: where the center of the Intranet universe is email-based, rather than anything to do with the web and HTML. But that topic is for another day.