Matt's Blog

Archive for the ‘Updates’ Category

New Theme Coming

Friday, July 6th, 2007

I’m currently creating a new Theme for Matt’s Blog… It’ll hopefully be much better than the current one, and much more browser compatible.

It has a much cleaner look to it, and the content will be much easier to read. It should also load much faster than the current one.

At the time of posting this, it looks the same in IE7 (for Vista), Firefox, Opera 9.20 (I need to upgrade to 9.21, though…) and Safari 3.02 Beta for Windows.

Once I shake a few bugs out of it, I’ll start making it into a WordPress Theme (right now it’s just an HTML file…) and then I’ll start adding some page-loading-time-saving AJAX and polishing it up. Expect to see it up in the coming weeks.

Matt’s Blog Gets Class B Compliance

Sunday, June 24th, 2007

I have just made it so that all traffic going to will be silently redirected to Which makes Matt’s Blog a Class B (the preferred class) in‘s books.

If you’ve never heard of before, it’s basically a campaign trying to raise the fact that www. is/should be deprecated. They have 3 “ranks” or “classes”. Class A, B and C.

Class A All traffic to and is accepted, and no redirect happens.
Class B The preferred class. All traffic to is silently redirected (301) to
Class C The hardcore class. Traffic to is denied and the user can only access the site through This class is not recommended.

Most hosts default their DNS to Class A. Where all traffic to and is accepted. The problem with Class A is that Search Engines might penalize you for having duplicate content (because you have the same content on and and you might end up with Search Results with and without the “www.“. You could even have 2 different PageRanks for your main page, depending on if you check with www. or no-www. Google allows you to define which domain you would like to show up in their Search Results. You can do this through Google Webmaster Tools. But, Google is only 1 of the many Search Engines.

So, how can you redirect to Well, it’s actually quite simple. This way will only work on Apache servers with mod_rewrite enabled. First, create a file (or open it, if it already exists) in your site’s root called .htaccess (including the period, but nothing before the period). Then, place this code in it (replace domain\.com with your domain name, make sure you escape the period):

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www\.domain\.com$ [NC]
RewriteRule ^(.*)$ http://domain\.com/$1 [R=301,L]

Let’s go over that code now.

RewriteEngine On simply tells Apache to allow you to use the mod_rewrite module (make sure it’s installed, first).

RewriteBase / makes sure we’re working on the root domain.

RewriteCond %{HTTP_HOST} ^www\.domain\.com$ [NC] tells the Server to see if the URI requested has the domain The [NC] tells it that it’s case-insensitive.

RewriteRule ^(.*)$ http://domain\.com/$1 [R=301,L] says that if RewriteCond is true to silently redirect the user to ^(.*)$ holds the value of what was after the original URI. $1 then makes sure that they’ll be redirected to the same page they requested. [R=301,L] will tell the User-Agent (browser, or bot) that the redirect type is 301 Permanent and and L tells the Server that it’s the last rule.

Note: If you’re using WordPress for the site in question, the above code must go above WordPress’ redirect stuff. So place it somewhere above # BEGIN WordPress.

Then, save the file and upload it to your site’s root. Now, all that’s left to do is to get Validated by Go here to do that. Your site should now be a Class B!

That’s it, your site is now even more Search Engine friendly.

Get it? Got it? Good!

WordPress 2.2 Released

Saturday, May 19th, 2007

WordPress 2.2 has been released! WP2.2 includes some sweet new features, such as Widgets.

I know, I know, this is old news… But I usually post about WP releases after I upgrade to them. I’ll be upgrading to 2.2 when I make a new Theme for this blog. Or, I might just improve some things on this theme… We’ll see.┬áThen, I’ll be rethinking all of the categories, renaming them, adding some, removing some, etc. Then, I’ll be going through all the posts and putting them in the proper categories.

So, go upgrade to WP2.2. ­čśŤ

Should I Make a New Theme?

Sunday, May 13th, 2007

With WordPress 2.2 just around the corner, the thought of my Theme for this Blog comes into my mind.

Will it work with 2.2 (it should)?

Did I go a little crazy with Blue?

Should the content by black text on a white background?

Is the Rage Italic font for my Post titles too hard to read?

Do most people even have Rage Italic on their computers?

Should I have used a little orange?

So, since my theme is a little blueish, maybe I should make a new Theme with more white, less blue and a touch of orange. Since 2.2 is coming out this week, this would be the best time to do this.

So, I’m asking you, my readers (should that be plural? ­čśŤ ), should I make a new Theme for this Blog, or do you like the current one. You can either post a comment on this post with the answer, or (if you don’t have anything else to say but the answer) you can Vote on the Poll I have on the sidebar (here, for those of you using a Feed Reader).

ReviewMe Accepted Me!

Tuesday, May 1st, 2007

That’s right, I got accepted into the ReviewMe service. Probably because of my new PageRank, or maybe my Alexa rank, or maybe my Technorati rank, or who knows.

ReviewMe is a service where people can order up a review on your site and, if you choose to accept it, you’d then go and write up a Review on the Site they want reviewed. Then, after 30 days, ReviewMe will confirm that the Review is still up, and you’ll get 50% of the price of the Review added to your account. The other 50% however, is kept by ReviewMe…

ReviewMe automatically generates the price for a Review each month. The price is, mostly, based on Rankings.

So, if you’d like to get reviewed on MattsBlog.Ca, click here.┬áThis Blog┬áhas a PageRank of 4 and has public Statistics available here.

Get Reviewed on This Blog for $30 USD.

Update: My site is no longer a part of ReviewMe, I never will (and never have) post paid-review posts on my blog.