No Pretty Lights

The other day I went to town the other day and bought a USB hub. So I looked around Harvey Norman and chose one that was compact and reasonable “cool” looking. I found one and purchased it. So I hooked it up that night, but only used it a day or so later. This thing was so cool. When you powered it up it had these very nice blue lights at the front for each port. They were that really great looking iridescent blue. Great I thought…

So a day or so later a hooked up the MP3 Player to transfer about 200 odd megs of podcasts and when I did that, I noticed something was a bit amiss. The transfer was as slow as a wet week. Turns out that the damn thing was a USB 1.1 device! I assumed that it was a USB 2.0, nothing on the box and since that’s the standard these days I thought that would be the case. Wrong. What it took was a hunt on the Internet to get the specs on it and there it was. But I was surprised to find that there was nothing on the box or in the documentation. So I waited for about 10 minutes while it transfer the files…

Yesterday I went back to the store and hunted for another USB hub. I found one. It is pretty basic and the only cool thing about it is that it is aluminium! The only light on it is a red one, at the back to say it is on. Bummer. Yeah sure this one is 2.0 compliant but I can tell you this hub is boring.

So I concluded that I want the one with the cool lights without the slow speed! I think also I am more disappointed that the cool lights had to go back and I have a boring alloy Hub. So I like things to look good and be functional, I am disappointed in myself, I always thought that I did not mind what something looked like, as long as it did the job! Seems not.

Advertisement

WordPress Response

I am not going to move the blog. Great response and in a timely fashion impress me, to the point of me totally deciding to stay with WordPress.

I got a response from a previous email that said that we are working on the problem and that it should be fixed now. Well that was before the problems last night. So I wrote a fairly pointed email back saying that in no way was it fixed. In addition there have been a few mentions in the blogosphere about the issues.

Seems that WordPress has grown at a rate that they were not expecting and that they have had some difficultity keeping up. This has resulted in servers slowing down and being unreliable. I got a response from my email in under an hour, you can not get better than that! The first thing I got was an apology. The second thing was that I was informed that they have purchased more bandwidth which should speed up things around WordPress. I have been informed also that as fast as they install new hardware (by that I presume hard-drives) it fills up. I think this is just a reflection of the growth of the blogosphere, it is growing at a phenomenal rate and doesn’t look like slowing down. However this week it looks like they are having a mass install of new hardware in their data centres and that will make a world of difference, I hope it does.

This is evident in the WordPress Blog so that’s good to hear:

We’re in the very final stages of bringing the new systems online, just waiting the last few bits of configuration to come online. As we’re more than doubling the servers we’re using, it should address all performance issues and help us prevent any for a long time to come.

Finally, I was told that they are working very hard at making WordPress a great domain that just works. The response also said that they have not been achieving that recently and that they have dissapointed their users. But they have the solution and they are working on it. So hang in there bloggers there is light at the end of the tunnel.

Interestingly Sebastian and I mentioned in the podcast last week that the ping times for WordPress to Technorati are terrible and that bloggers need to manually ping Technorati to see some benefits from it. This is a problem with Ping-O-Matic and Technorati recognised by WordPress as Matt has been talking to Technorati about resolving the issue. My advice keep doing it manually as this has not been resolved yet, I will try to keep you posted.

Great response from WordPress and I hope that I can continue to support WordPress as I like their style and they are excellent in the support stakes.

Slow Progress & A Steep Learning Curve

Another day and my brain is yet again straining. I am tackling the whole domain thing, how to use them and how to manage them. Which if you are like me is not an easy concept. So for me this whole exercise is quite slow, but I am learning heaps along the way.

So I’ve got these two Domains now what; I say to myself. So after a bit of digging and a phone call to my brother (a real geek), I think I have most of what I want to do sorted out into what I have to do to make it work. I have one domain that I want to use as the domain for the website where the podcast is being hosted. The other domain I want to be able to “point” to the one that I chose. For those asking why; the second domain has a slight variation to it, I want to catch those people putting in that slight variation into their browser. This equates simply to: if a person puts X into their browser then they end up at Y (Y = the podcast homepage). They won’t see what happened but they will be where they intended to go. Plus I don’t want anyone stealing the domain by just making a small change.

Then I go to Libsyn and click on the Sign up page to have a look. It is then I discover that there are name servers to assign a domain if I own one to use on the site. It is here that the phone call to James comes in. Currently my domains are “parked”, I own them but they are not being used for anything. So what I have discovered is that I need to “activate” the domain, and I do this by assigning it name servers, or is that assign it to name servers? So anyways, I see on my administration for my doamins that I can do this. So thats the last job that I have to do tonight. That will take about four to six hours for the .com domains (which mine are) to become active. I am not sure what happens behind it all but this means that when people visit the podcast page they will see the domain as a URL in the address bar. Very cool.

So then the other thing that I need to do is set up domain forwarding for that other domain that I own; this is the X & Y thing. The administration screen for my domains calls it forwarding but apparently for the more geek of you that’s not actually correct, but as I said I am new to all this. That in itself seems a simple process, I can change it back or modify it if I find something isn’t working, which is good. But according to James domains are serious mojo and you can really stuff things up if it isn’t done correctly, so I am checking and double checking everything before I do it. It still scares the hell out of me though.

So the state of The Roosters brain is somewhat mashed up, but I think I am understanding a little bit more as I go on. I hope that this might help anyone else that is trying to get their head around domains and how to use them… Oh crap I was going to talk about web 2.0, oh well time for that and I really want to talk about it – stay tuned.

Lastly, for any errors I apologize in advance, I am not a geek rather just trying my best. So if the terminology is wrong or something is not quite right let me know.

Thanks to Rob Irwin who was the first person that was not family to post a comment, you made my day to think that someone else was reading my blog!