I certainly did not set out to do this as an ANZAC tribute, but I when I realised that although ANZAC Day was yesterday, and that today is the national public holiday we have to celebrate it – (normally the same day, but with the 25th falling on a Sunday this year, the holiday is today) – I could not help but feel a sense of irony.

The ANZACs fought for our liberty against foreign threats. I am sure that many would be devastated that the latest threat to our freedom comes from within. Government controlled censorship. The buffoons in charge of this policy say “it is only about blocking refused classification (RC) material”. There is nothing to stop them from refusing classification to anything they choose.

That’s why their list will remain secret. That is how they are planning to restrict our freedoms online. At a time where we celebrate the pride our nation has for its forefathers, I’m not feeling a lot of pride for those who are here in power now.

I discovered this morning that one of my scripts received an error code back from an API that I had never seen before, so I had to make some minor changes to accommodate that – so at the same time I have rolled out my Twitter auto-tagging feature, meaning that tags on my postings here will automagically become hashtags over on Twitter.

I’ve also fixed an annoying “Operation Aborted” error message that you sometimes get when viewing with Internet Explorer – all the more reason not to use it though, I say!

Have a good weekend!

I was ready to yell at my stupid ISP – who are normally responsible for ridiculous crap that have in the past caused almost every kind of freakish outage imaginable – when the root cause of the problem reared it’s head.

Everything back to normal around 7:30pm AEST, after about 5 hours – I had to get home from work first!

So, I’ve fixed all that up. I’ve also taken the time to clean up a bit of the backend code for my custom plugins and widgets, so things will probably load a little faster in most instances with some neater code behind them.

Special thanks to Paul and the guys at Kilbot for their tireless efforts to get it all sorted out, and I recommend them for anyone looking for a hosting provider.

Almost everything has gone off without a hitch – but there are a few things that haven’t quite translated from my testing server, to the live server. So I have a little more tinkering to do.

Some stuff will be moving to a new site – namely the pages relating to the “Wyres” family name – I’ve recently managed to get a hold of the domain “wyres.com” – (after three earlier unsuccessful attempts) – so if you can’t find any of that here, you should find it over there within a couple of weeks.

As the first stage of removing the “technical barriers”, I’m currently in the process of re-engineering a couple of backend aspects of my site, so you might get a few odd things happen for the next few days.

Bear with me, everything will be back to normal very soon!

Well, my fault – I was doing some database maintenance, and inadvertently dropped the entire database. Normally, that wouldn’t be a bad thing.

Except when your backup script isn’t running. Gulp!

I’ve just moved the site from an older server, onto a newer one – and was cleaning up afterwards. Hence the need to do a little database maintenance. However, I’d not started using the database backup script on the new server yet.

Needless to say, I am now. I found enough data from old dumps, and RSS feeds, that I was able to piece it all back together.

And yes…I do feel like a dill! Moral of the story – completely wake up, and have at least one coffee before doing database maintenance.