Posts Tagged ‘GoDaddy’

GoDaddy BackOrder Blues

Friday, 18 September 2009

Some years ago, Go Daddy added a back-order service whereby a domain already registered by another party would be monitored and, should its registeration lapse, the domain would be registered in the name of the purchaser of the service.

Some time after that, Go Daddy added an auction service. And, when registration lapses for which Go Daddy is the registrar, then duiring the grace period (42 days in the case of Go Daddy) Go Daddy itself puts the domain up for auction; the auction ends well before the grace period, and the auction results are cancelled if the prior registrant renews before the end of the grace period.

A registrant seeking to have a domain appraised might simply let the registration lapse, watch the auction, and then register before the end of the grace period. A late registration requires a higher fee, but that difference could be viewed as the cost of appraisal.

Now. here's where it gets ugly. Go Daddy holds such auctions even if there is a prior back-order. They hold the auctions even if the domain had a different registrar when the back-order was placed, but then switched to Go Daddy. They hold the auctions even if the back-order was placed before they had an auction service. If the domain should be bid to anything above an opening bid of US$10, the purchaser of the back-order must either pay more or let the domain go to some other party.

A Go Daddy back-order on a domain is worse than useless to its buyer if the domain may be expected to be registered with Go Daddy at the time whenever registration lapses. If the domain is sufficiently attractive that a back-order would be useful without an auction, then there will be competitive bidding in an auction.

Now, I'm sure that Go Daddy sent a notice that the old back-orders were going to be subjected to the new protocol, and that refunds were offered. But few if any customers would have understood the implications of a change, otherwise there would have been a lawsuit that Go Daddy would have lost, as simple refunds wouldn't have covered the economic loss avoidably being placed on these customers.

The Domain and 'Blog per Sese

Wednesday, 20 February 2008

The string oeconomist (or œconomist) is an old-fashioned spelling of economist. I am an economist; whether I would be seen as an old-fashioned economist would be a function of what one saw of my premises, methods, and conclusions.

I am not the first person to have registered this site-name. The last previous registration expired on 4 September 2007. A check of the Wayback Machine turned-up no archived pages, so perhaps the name were never actually assigned to a site.

Various people have previously used oeconomist as a regular identifier. I am not amongst them. (In particular, I am not (and never have been) the oeconomist at LiveJournal and at Infotrope.)

The site name is registered with GoDaddy. They're not wonderful as a registration service, but they're acceptable.

Hosting is provided by, so named because, if one orders their package of lowest price and one pays for their services a year at a time, the charge comes to about US$4 per month. I first went to to get hosting for a different site a few years ago, at the recommendation of Ronnie Ashlock, who used and uses it to host

A while back, was purchased by IDAGroup LLC. When last I knew, they'd not seemlessly integrated support. And AT&T has a proclivity to treat e.mail from as spam.

The 'blogging software that I'm presently using is WordPress. At the suggestion of Gaal, I added support for OpenID. I did this by installing a plug-in, WP-OpenID. Another plug-in, Post Levels, allows me to assign levels to posts and to registered users, such that when users are logged into the site they are able to read any posts at or below the level of their registration. And YATCP modifies the interface to support a tree structure of comments (so that comments meant in reply to other comments are nested under then and so forth). I also added WP-Polls, mostly just for minor fun. And I will look into Edit Comments XT, to give commenters an opportunity to fix typos and to withdraw things written in haste.