Archive for June, 2008

Selling on Sedo.com: What Happens If the Buyer Does Not Pay?

Tuesday, June 24th, 2008

A few weeks ago, I auctioned off a domain name on Sedo.com. It fetched a little over a thousand bucks so I was happy to sell. One day after the auction ended, I promptly received an email message from Sedo, which informed me that they had already invoiced the buyer and were expecting the payment for the domain to arrive soon. Since the entire process was dependent on when the buyer sent payment, Sedo didn’t specify a date when the transaction would be completed.

A couple of weeks passed and I didn’t hear any update from Sedo. Then I started thinking, “What happens if the buyer doesn’t pay?”. I’ve had encounters with time wasters on some of the domaining forums, but there are no formal or legally binding contracts for domain transactions on those forums, so there’s really not much that you can do. You get to scratch your head and mutter curses to an unresponsive screen — that’s the closest thing to compensation that you could get. But this was Sedo, possibly the biggest domain auction house on the Internet!

I decided to contact Sedo — surely a thousand bucks is worth more than one email message. I didn’t get any reply though. They usually reply within a day or two, but not this time. I checked the Sedo contract again, but it didn’t say anything about what happens if the buyer does not pay — whether Sedo will twist his arm and make him cough up the money that he promised to pay when he placed his bid. Nothing. The only clause that was remotely related was this:

Payment must be remmited (sic) to Sedo with five (5) business days from the creation of the payment request.

It didn’t say what happens if the buyer doesn’t pay within five business days. Maybe Sedo doesn’t want to think about that part.

Anyway, I needed confirmation if I was still legally bound to sell considering that the buyer had obviously defaulted on his payment. Since I wasn’t getting any reply from Sedo, I decided to contact a Sedo employee who lurks on one of the domaining forums that I frequent. I got a reply within an hour. He wrote:

The buyer has five days to confirm payment has been sent and then the seller can choose to cancel.

That was my way out of the contract. I wasn’t happy that my domain didn’t sell as I thought it did, but I was glad to have found closure on this issue. A few hours after I got the answer from the Sedo guy on the forum, I finally received an official reply from Sedo:

Unfortunately we have had no choice but to cancel the transfer for this domain name. Despite repeated emails and contact attempts the buyer has failed to make payment for this domain.

The contract in place for this transaction is legally binding. Should you wish to pursue legal action, the buyer's applicable contact details have been made available for your viewing. You will now find them on the contract for this transaction within your Sedo account.

I’d wasted enough time on this buyer, so I didn’t even think about whether I should pursue legal action. It was a lesson learned: A domain isn’t sold until you actually receive the payment, regardless of where you sell it.

One week after this all happened, I received an email message from a guy who made an offer on the same domain a few months back. He was asked if I had decided on the selling price for the domain. I said yes and asked for 150% of the winning bid on Sedo, plus Escrow.com fee. He agreed. So I was able to sell the domain for more and all is well.

Font Problems After Installing Windows XP SP3

Tuesday, June 10th, 2008

The other day, I received a Windows Update notification that Service Pack 3 (SP3) was available for download. It was mid-afternoon and the sweet, powerful aroma of coffee brewing in the pantry wafted to my cubicle — beckoning, tempting me like… Anyway, I decided to take a break and install SP3. After two-and-a-half cups of coffee (about 30 minutes in time unit), the installation process was completed and my computer allowed me to work again.

I went straight back to what I was doing before — updating a not-so-usable user guide using Adobe FrameMaker. When I tried to update the cross-references in the user guide, I got an error message that the book could not be updated because Arial Black was missing. (Yes, we’re using Arial Black in our template. At least it’s not Comic Sans.) Arial Black is part of the default font pack that is installed with Windows, so I was pretty sure I had it on my computer. Wanting to be sure, I checked C:\WINDOWS\Fonts and verified that the Arial Black font file (ariblk.ttf) was indeed there.

It could only be SP3 that caused this, I thought, so I did some digging. True enough, a few other people were encountering the same issue and were posting on the Microsoft forums. Apparently, SP3 installs new versions of some of the font files, including Arial Black, Impact, and Tahoma. The new version of the Arial Black font file has some problems, which is why I and some other people were getting error messages on the various applications that we were using. Some people reported that Arial Black looked “weird” in Microsoft Word, while others who were working with Web pages said that Arial Black bold appeared as italicized.

Regardless of the symptoms, there is only one quick fix — replace the problem font file. Get a copy of the old Arial Black font file and replace the one that is currently in C:\WINDOWS\Fonts. Here are the steps:

  1. Open Windows Explorer.
  2. Go to C:\WINDOWS\$NtServicePackUninstall$.
  3. Look for ariblk.ttf (with the timestamp 8/4/2004 6:00 PM).
  4. Copy it, and then paste it in C:\WINDOWS\Fonts. This will replace the new Arial Black font file (with timestamp 1/2/2007 8:00 PM).

That’s it. Problem solved. Arial Black should now appear as it should — ugly.

The old Arial Black font file has the timestamp 8/4/2004 6:00 PM.

How to Create a Go Daddy Account

Tuesday, June 3rd, 2008

Just because I buy and sell domains as a hobby, people ask me all sorts of questions about domains. One of the more frequent questions that I get is “How do I create a GoDaddy.com account?”.

It’s getting boring to explain the steps again and again. And telling them to go to www.justfuckinggoogleit.com for instructions doesn’t work (one guy actually came back to me and said, “I couldn’t find any information on www.justfuckinggoogleit.com). So I’ve decided to just post the instructions here.

NOTE: The easiest way to create a Go Daddy account is to purchase a domain name from them. Before you can check out and pay, the domain registration process will prompt you for your personal information and create an account for you.

To create a Go Daddy account

  1. Open your Web browser, and then go to GoDaddy.com.
  2. On the right side of the page, click the Create a New Account link (right below the logon box). The Create A New Customer Account page appears. Too lazy? Just click here then.
  3. Under Enter Your Contact Information, fill in the text boxes that are marked with an asterisk (*). The asterisk indicates required information.
  4. Under Stay Informed, indicate whether you want to receive promo and announcement email messages from Go Daddy. If you do not want to receive these types of email messages, click No for all the options in this box.
  5. Click Create a New Account.

The form refreshes and automatically logs you on to the GoDaddy.com Web site. You may now start purchasing Go Daddy products.

You should also receive an email confirmation from Go Daddy (at the email address you specified when you created your account), with your Go Daddy customer number. Record this number and keep it in a safe place. You can use your customer number (as an alternative to your logon name) to log on to the Go Daddy Web site.