I was checking over the referral urls section on my blog stats and it seems someone emailed a link to my blog to someone on yahoo. weird.
Putting all these thoughts together, I am about to attempt something a bit iffy. I am going to edit my BlogSpot template so it cuts out all the miscelaneous HTML crap, and leaves the pure post code. I will then download my posts to my computer, making it easier for me to migrate- a simple highlight, copy & paste from Notepad++ straight into WordPress.com.
No messing about with back and forwards buttons. No waiting for page loads. No triple message boxes on each back button press. No warnings about POST data. A step in the process will be simplified. Migration from BlogSpot to WordPress.com will no longer require access to BlogSpot.
I have an idea of how I’m going to make it work, but I’m not sure if it will.
With all these service delays, and no news getting to me on what’s causing them- is it technical problems with WordPress.com, technical problems with my sucky ISP etc- I’ve come to the following conclusions:
What this basically means is that while I love the WordPress platform, I’m starting to hate the WordPress.com site as for whatever reasons beyond my and the technical ppl over at WordPress.com control that are causing the server time out delays that are preventing me from blogging.
Basically, I’m stuck on what to do. I’m not even sure whether this post will actually make it to the blog when I click the Publish button.
So I had some free time between lectures at Uni today, so I thought I’d spend some time migrating the posts over from here to there. Aside from the issues I’ve been having with server time outs, that are- in fact- still present. My inability to access the WordPress.com server is the reason why I haven’t gotten anywhere near migrating and why I’ve missed two weekly news roundups. I’m getting thoroughly pissed off at this delay which is outside of my control- so much so that I’m actually regretting migrating in the first place.
Yes, I know WordPress is by far a superior blogging platform to BlogSpot, but BlogSpot rarely, if ever made it impossible for me to post. WordPress.com on the other hand has decided to think that it needs reinstalling. Every single blog hosted on WordPress.com, and the main site appears to have decided it needs reinstalling. While I was writing that sentence the problem appears to have gone. The timeouts are still there though, so I can’t update my wishlist to show that I’ve actually bought, received and installed the 512MB module on my system, and that I’ve bought but still waiting to receive most of what’s left. The timeout problems seem to have disapeared, although I don’t have the time to fool around migrating tonight.
After those server time-out problems appeared to have gone away, I’ve managed to get all my posts up to July migrated. Still crap loads to go though.
The fairly large amount of posts was always going to be a problem, but I keep forgetting to adjust header values to fit with the template I’m using here. Can’t wait for the XHTML 2 all-purpose header tag. Early posts used an <h1> tag in the post below an <h3> tag in published output and later posts used a more semantic <h4>. What was an <h4> is now an <h3>.
Let’s not forget ISP screw ups and intermittent service outages.
The little ‘security’ feature they have in place means I can’t use <dfn> tags for my potentiallyOffensive coding experiment (you’ll read more about potentiallyOffensive experiment when I get the posts migrated), and also cause problem with my class=”hidden” and class=”offscreen” coding experiments.
It’s a little experiment relating to censorship, freedom of speech and freedom of choice.
Personally I hate seeing full stops at the end of lists and header tags- <dt> and <th> included. The reason I put them there in the first place is back when I was working for Connexions, I was experimenting with some screen reader software, and the dumb piece of crap didn’t put a pause after each header or <li> tag in the navigation list. So I had to put full stops in the <li> tags, but hide them from view. Thus class=”hidden” was born (yes I realise other people may use it, but that was when I first used it). More recently I’ve needed to have some full stops (or other text) be hidden in @media screen, projection etc, and apparent in @media print, aural, braille, embossed, and others hidden in just @media screen, print, projection, handheld etc. Thus class=”offscreen” was born (early posts in Blogspot used class=”hidden”, later ones used class=”offscreen”).
However I have noticed that the code disappeared between manual coding (I don’t like WYSIWYG editors) and publishing.
I’ve found a small work-around to the problems I was experiencing with my ISP– do the migration from Uni.
So right now I’m sitting in Cell M1 in the Info Centre, typing away in an uncomfortable position because it’s not my comfy office chair, and my shoulders are hurting (although I suspect my wrists will follow) because there are no wrists rests in the entire University. I also can’t spell check my typing as although I’m using Firefox, it’s not my computer so I don’t have all my extensions, configurations at hand.
Grr.
It appears that my ISP has decided to be an ass again. In terms of beep beeping quality anyway. Access times to WordPress.com and BlogSpot were so crap today it became impossible to migrate any more posts. I’ve still got to correct a post slug as well.
I’ve mentioned in the past I wanted to eventually move off of the blogger platform, because while it is a good blogging platform, it didn’t meet all my needs. I checked my email a few minutes ago and I got my Golden Ticket!!
I’m in the process of setting it up now, hopefully I’ll be able to transfer my existing posts over without too much hassle.
If you want to try and win your own golden ticket to WordPress.com, take a visit over to WordPress.com.
I’m currently working on getting all my blogger posts migrated to my wordpress.com blog. Be back in an hour or so (or less hopefully).
Changed the rel attribute in the Comic Alert feed link, removing the alternate value just cos I felt like it. Oh and probably shouldn’t be there as it isn’t an alternate representation of this blog. Feed link for this blog is an alternate representation and has been amended as such.
Moved the Comic Alert feed link into a new section Syndication Feeds, added link to feed for this blog.
Added Megatokyo to the list of webcomics.