Next thing I know, Mr. X calls me to tell me that he’s hired someone else to develop a new site for him, and he’ll have new hosting as well. Okay. It would have been nice if he had at least asked me for a quote, but that’s fine — he has every right to go with someone else.

I sent him the ftp login info so that he can give it to his new webmaster to grab the files from the existing site, in case those are needed. I also suggested that he open an account with GoDaddy so that we can transfer his domain to his own account, since I have no desire to continue to renew Mr. X’s domain every year and bill him for it. If he’s not hosting with me, and not paying me anything to do updates or other maintenance to his site, handling his domain renewal is just not worth my time. So I walked his secretary through opening a GoDaddy account, and I transferred the domain to him.

Mr. X’s hosting was paid up through the end of the quarter, so I told him that I would keep his hosting active through July 31, but his new webmaster needed to either have his new site up and running on the new host by then, or move the existing site to the new host, in order to avoid any downtime for his site.

The last week of July arrived. Before I shut off his hosting, I decided to see if he’s got the site hosted somewhere else yet. Nope. It’s still pointing to my server. I email Mr. X. I get a reply back from his secretary, who said that he’s out of town and she doesn’t know anything about a new webmaster. She was under the impression that the domain transfer was all that was needed. (Even though I made it very clear in my earlier emails that the domain registration was completely separate from the hosting.)

I explained that she really needed to get Mr. X to get his new webmaster to get either his existing site or his new site up and running on their new host (whoever that might be), and to change their nameservers to point to the new host. I explained that if I just shut off his hosting their site would disappear from the web altogether. I also noted that they could renew their hosting with me so as not to have any downtime if there were any problems with the new webmaster or the new host. She said she would talk to Mr. X about it.

Aug. 1 arrived. I checked, and sure enough, the site was still live on my server. I emailed Mr. X and told him that he either needed to get his site running on his new host immediately or renew his hosting with me, because as soon as I shut off his hosting on my server, his site would disappear.

I received a reply email that said, simply, “This has been taken care of.” When I checked again, the domain nameservers were pointing to GoDaddy’s nameservers. So I shut off the hosting on my server.

Now his site consists of a GoDaddy parking page.

I suspect that Mr. X never did hire another webmaster. I have the feeling that he was expecting his secretary to build him a new site, and that she knows virtually nothing about it. I don’t know why he told me that he had hired someone else, nor do I know why he was so determined to move his hosting somewhere else. He had never complained to me about any problems with either the site or its hosting, and he certainly wasn’t overpaying for the hosting. I believe he may have thought he could save some money, somehow, although the small amount he was paying me for the hosting meant that at most he could only save a little tiny bit on his hosting by going with a cheaper host.

I tell myself that you can’t save people from their own mistakes, and that his site is now his problem, and his problem alone. Nevertheless, I hate to see a site disappear from the web, and kill its standing in the search engines, due to the owner’s stubbornness, lack of knowledge, and unwillingness to listen.

Copyright Incident #1

Not long ago, I made a copyright mistake during the course of a project for a client whose site had previously been created by another website designer. The site’s content was decent, but it badly needed a new design and underlying code structure to make it user-friendly and search-engine-friendly, along with the addition of some new features. So I used the existing content and placed it into the new design. Two of the pages in the previous site contained articles that carried copyright notices. My mistake was in assuming that those two articles were used with permission — that either the client or the previous designer had contacted the copyright owner and obtained permission to use those two articles. I didn’t verify that assumption with my client; I simply used the articles on the new site. It turned out that permission had not been obtained, and before long my client received a cease-and-desist letter from the copyright owner.

Ironically, the old site was so search-engine-hostile that the articles could probably have been used forever on the previous version of the site, and the owner would never have discovered their use, because they never would have been found in any search engine. However, I made the client’s site crawlable by search engines, which made it easy for the copyright owner to track down the unauthorized use of the articles.

Take-Home Lesson: Never assume anything about copyrighted material. I don’t consider it my responsibility as a website developer to police the content my clients provide me. I occasionally use stock photos on client sites where I purchase the license myself, but otherwise content is the client’s responsibility. However, while it may not be my legal responsibility, it certainly represents good practice to help my clients (and, incidentally, myself) to stay out of trouble.

Copyright Incident #2

Not long after the cease-and-desist incident, a different client sent me a collection of photos to be used on his site that I was developing. The images were all embedded in a Word document, and I used a program called FileJuicer to extract the images. FileJuicer’s a great little program; it works on Word files, PDFs, and many other file formats, and extracts into separate files all the images and other embedded elements from the file. When using FileJuicer, I usually don’t pay attention to any files except the images that FileJuicer extracts — but in one of those weird coincidences, I happened to open the URLS.html file that FileJuicer created. This file was a clickable list of links where all these photos came from.

It turned out the photos were lifted from a variety of websites, and I was pretty sure my client had not obtained permission for their use, particularly since one of the sources was a competitor of my client.

I contacted my client and let him know, as diplomatically as I could, that he was not legally permitted to use those photos on his site unless he had permission. I offered suggestions for alternative approaches, including contacting the copyright owners for permission to use the images, taking his own photographs, and paying for a license for photos from one or more of the royalty-free stock photo sources. Fortunately, my client saw the wisdom of this, and agreed to use photos from other sources.

Take-Home Lesson: Clients will generally be reasonable about this kind of thing, when you’re trying to keep them out of trouble. If I had ignored what I discovered from the URLS.html file that FileJuicer created, my client would probably have been hit with a number of cease-and-desist notices from a variety of different entities.

He may even had received one of the dreaded Getty Images demand notices. Getty Images has been in the habit for some years now of sending threatening and intimidating settlement demand letters to people who are allegedly using a Getty Images image without a proper license. Getty often demands exorbitant sums — they often demand in the neighborhood of $1,500 to $2,000 for a photo that can be licensed for $40 or $50. There’s no telling how many people roll over and pay these exorbitant and ridiculous sums in the face of the threatening letter from Getty, reasoning that an individual or small business owner is better off paying whatever Getty asks, if it will make Getty go away, thus avoiding the hassle and expense of a lawsuit.

It’s entirely possible that the photos my client sent me originated from Getty. The sites he got the photos from may have paid Getty for a license, or may have lifted the photos from somewhere else that had paid the Getty license fee. Either way, my client could well have received one of those hostile Getty demand letters if I had proceeded to post the photos he sent me.

Here are a few guidelines on copyright and using material that you didn’t create yourself:

Copyright Guidelines

Copyright Fact #1: Virtually anything you might find on the Internet is copyrighted. If it’s legally capable of being copyrighted, it’s copyrighted, unless the author or creator has explicitly placed it in the public domain. (And note that “it’s on the Internet” does not mean it’s in the public domain. It’s still copyrighted.) In the United States, anything created in the past 75 years is subject to copyright, and everything created since 1989 is automatically copyrighted at the moment of creation — no need for a copyright notice, and no need to register the work with the U.S. copyright office. Simply by virtue of creating it, the creator owns the copyright. (There are exceptions that hinge on “works made for hire,” under which a work created by an employee in the course of his employment is owned by his employer. I won’t address “work for hire” just now, except to note that it exists.) Generally, you must assume that if a work exists, it is copyrighted.

Copyright Fact #2: You may not use copyrighted material without the express permission of the copyright holder. There are exceptions here, too, such as fair use for commentary or criticism, but in general, one must assume that one cannot copy and use material owned by others without their permission.

Copyright Fact #3: Even if you’re not making money from the copyrighted material, or if you’re not using it for commercial purposes, you will still be committing copyright infringement if you use it without permission.

There are lots and lots of nuances, considerations, exceptions, and ramifications when using copyrighted material. Bear in mind, IANAL — I Am Not A Lawyer. Anyone wishing to use any copyrighted material in a way that they think is permissible under copyright law should consult a competent IP attorney for appropriate legal advice. My bottom line message is:

Never use material that you did not either create yourself or obtain permission from the copyright owner to use. That approach will keep you out of trouble.

• Brad Templeton’s “10 Big Myths about copyright explained” is a nice summary of some common copyright myths.
• If you like to get it “straight from the horse’s mouth,” the U.S. Copyright Office has very comprehensive information on copyright law, along with an online form for registering your copyrighted works.

I checked the DNS settings on the server. I did traceroutes from my computer. I went to websites in other parts of the country and did traceroutes. I pinged. I double-checked and triple-checked the nameservers. Everything was exactly right, and I was tearing my hair out trying to figure out why the client couldn’t reach his own site.

Finally, it struck me: The client was searching for the site, using the search box on Yahoo and Comcast.

Once I told him that his site not indexed yet (because it’s brand new), and that he needed to enter the URL directly into the browser’s address bar — voila! Problem solved.

This is one to file away to deal with future “can’t reach my site” issues.

Note to website designers and developers: If you ever have clients who can’t reach their site, check to see if they’re searching for it.