Nik's Technology Blog

Travels through programming, networks, and computers

UK Reg Encourage Users to Buy Domains for 10 years Citing Google Patent

UK Reg, a domain registrar in the United Kingdom is using text written in one of Google's patent applications to help sell 10 year domain name registrations!
I was quite surprised to see a marketing technique used to sell a search engine marketing benefit.

Here's a screenshot from the site below:

UK Reg - Secure your domain
Clicking on the "Google patent application" link produces a pop-up which quotes the following sentence from the patent application Google made, with a link to the application in full:

"Certain signals may be used to distinguish between illegitimate and legitimate domains. For example, domains can be renewed up to a period of 10 years. Valuable (legitimate) domains are often paid for several years in advance, while doorway (illegitimate) domains rarely are used for more than a year. Therefore, the date when a domain expires in the future can be used as a factor in predicting the legitimacy of a domain and, thus, the documents associated therewith."

Google Paid Link Policing and other more Democratic Ranking Methods

Google's Webmaster Help Center explains Google's policy on paid links and encourages people to report them to Google. Here's a snippet from Google's statement:

"Buying or selling links that pass PageRank is in violation of Google's webmaster guidelines and can negatively impact a site's ranking in search results.

Not all paid links violate our guidelines. Buying and selling links is a normal part of the economy of the web when done for advertising purposes, and not for manipulation of search results. Links purchased for advertising should be designated as such."

Google essentially want websites to designate paid links with rel="nofollow" anchor tags, so link juice or PageRank is not passed on to the website who bought the link. The use of rel="nofollow" anchor tag was originally conceived to stop comment SPAM on blogs and discussion boards, but its use has now spread to the policing of paid links.

I understand the difficulties Google and the other search engines must have in determining when to pass link juice between websites, but leaving the webmaster in control of this is like asking Google to start ranking sites by meta keywords again.

I'm beginning to believe the future of web search lies in the democratic nature of the StumbleUpon, Digg and other social bookmarking methods like (del.icio.us and my favourite ma.gnolia), whereby users vote, tag and bookmark sites. Surely a combination of popularity and search algorithm is the way forward?

Updated: Shortly after I posted this blog entry, Google has been spotted testing Digg-style voting buttons on their results pages!

Updated: Matt Cutts and Maile Ohye posted on The Official Google Webmaster Central blog on 1 Dec 2007 a post that intends to clarify Google's stance on paid links.

Choosing a Flat-Screen TV: Built-in TV Tuners

Continuing my series of posts about choosing a High Definition TV (HDTV), I read an article today that could potentially make some people put off making an HDTV purchase for the time being.

In the UK there are 4 ways to get TV (excluding via broadband):

  1. Terrestrial
  2. Freeview (Digital Terrestrial)
  3. Sky (Satelite)
  4. Virgin Media (Cable)

Currently only Sky and Virgin Media have HD channels that allow you to enjoy television broadcasts that exploit a High Def TV. Both services require you to have special HD set-top boxes to receive these broadcasts, you also get charged more than the standard definition (SD) package cost for the privilege.

Terrestrial analogue signals are gradually being phased out between (2007-2012) to clear up the spectrum for HD over Freeview. Ofcom published a news release on 21 November 2007 detailing the Freeview upgrade.

Built-in Tuners

Now back to choosing an HDTV. It is becoming more common for HDTVs in the UK to come with built-in Freeview tuners. This means you don't need an external set-top box top get Freeview broadcasts, this is good since analogue terrestrial tuners won't be much use to us for too much longer. The problem is that HD Freeview will require a set-top box upgrade, it also uses a more advanced coding standard which isn't compatible with the current coding standard.

So unless current HDTV built-in tuners can be upgraded via a firmware upgrade at a later date, then you'll be needing to add an HD Freeview set-top box to your set-up when they become available.

Here's the paragraph from the Ofcom new release:

"Viewers who wanted to access the new services on offer would need to buy a new DTT set-top box or integrated television, which was compatible with MPEG4 and DVB-T2."

"However, viewers with existing DTT set-top boxes or integrated televisions would still be able to access Freeview services with their current equipment."

Choosing a Flat-Screen TV: Screen Size

It's coming up to Christmas time again, and lots of people are thinking of splashing out on a new flat screen TV. Prices are becoming cheaper all the time which is a good thing, but the sheer range available can make it a daunting task. Even though prices are falling each month, deciding which make, model and size is one thing, but what about resolution, high-definition (HD) readiness, connections, built-in tuners, plasma or LCD etc?

I'm going to start by finding the most suitable screen size.

What HDTV Screen Size Should I Buy?

Choosing a suitable screen size will depend on where the television will be going, and how far away from the screen you'll be sitting. Obviously for a home theatre set-up you'll be wanting a big screen, whereas for a bedroom or kitchen you'll want a smaller size.

You don't want to give yourself eyestrain, or be so close that you can see individual pixels on the screen, but on the other-hand you don't want to be so far away that you don't become immersed in the content. Luckily there are size charts available on the web that can help determine the appropriate size for different rooms and TV placements.

Buying New PC Hardware? - Make Sure It Supports Vista!

It's fast approaching the anniversary of the release of Windows Vista to business users, home users have been buying new PCs with Vista pre-loaded since the end of January 2007.
I haven't upgraded to Vista yet; my DVD upgrade is still in its box. I've installed it a couple of times to have a play around with it, to see which pieces of hardware and software are compatible, but that's it.
There are a couple of reasons why I haven't taken the plunge. Firstly, my PC can run the new Aero UI on Home Premium, but when I add the CPU monitor widget to the desktop to see how well it copes, it tends to max my processor out just opening windows etc. This is probably to be expected with a 4 year old computer. The second reason is the hardware and software support for Vista. You would have thought that manufacturers would have started to factor in support for a new Microsoft operating system, wouldn't you?
The word that springs to mind when talking about Vista compatibility today is "patchy", and today is almost 12 months after the official launch!

Future Proof Your Hardware Purchases

Most people who buy hardware or software for their PC will be expecting it to work with Vista out-of-the-box. They don't want to be updating firmware, or worse still finding out that their new device only supports XP! Why does Microsoft bother having alpha and beta testing periods when the likes of Apple can't even make their flagship iTunes work?

My advise to anyone thinking of buying a new piece of hardware or software is to make sure it supports Vista, even if you're sticking to Windows XP for the foreseeable future. You never know when you might buy a new PC, and do you really want to have to replace your hardware once you've upgraded to Vista?

Enumerate Available Database Providers in ASP.NET

Using the DbProviderFactories class in ADO.NET you can retrieve a list of available database factories using the GetFactoryClasses method. This can be useful if you host your ASP.NET site on a shared server and don't have access to the web server and machine.config file.

The output of the GetFactoryClasses method is a DataTable of available factory classes, these are the factory classes that the .NET runtime will have access to.

Here's the kind of output you'll get...

NameDescriptionInvariantNameAssemblyQualifiedName
Odbc Data Provider .Net Framework Data Provider for Odbc System.Data.Odbc System.Data.Odbc.OdbcFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
OleDb Data Provider .Net Framework Data Provider for OleDb System.Data.OleDb System.Data.OleDb.OleDbFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
OracleClient Data Provider .Net Framework Data Provider for Oracle System.Data.OracleClient System.Data.OracleClient.OracleClientFactory, System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
SqlClient Data Provider .Net Framework Data Provider for SqlServer System.Data.SqlClient System.Data.SqlClient.SqlClientFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Here's the code you'll need in your code behind file.

DataTable providersList = null;
providersList = System.Data.Common.DbProviderFactories.GetFactoryClasses();
GridView providerGridView = new GridView();
providerGridView.DataSource = providersList;
providerGridView.DataBind();
form1.Controls.Add(providerGridView);