I have updated my lightbox comment form for Blogger to fix the redirection bug that some people were having.  Please change to the new code for step #6 to fix it.

Some of you may have noticed the gradual changes going on — most notably the 150 or so of you who read me by feed. I am moving my primary web presences from Blogger to a self-hosted WordPress on singpolyma.net.

My Technical, Personal, and XOXO blogs are all here (see tabs above) with all their content. If the old ones aren’t properly redirecting yet, they will be soon — going to a post on the old sites should take you to that post on this site. Feeds have not changed much, they are still on FeedBurner, but there is now a main feed (and blog) that combines posts from all three!

The site is not 100% done, obviously (a hacker’s site never is 😉 ), so if you see something that needs to be added/changed, feel free to contact me!

For this launch I have upgraded my FreshTags plugin and written Videntity and OldBlog redirection plugins. All my WordPress plugins now have thier own page.

Some of my TechBlog readers may fear (and, in fact, this has been voiced to me) that now that I am WordPress-powered I will forget Blogger. Not true at all. My existing hacks will receive maintenance, and new ones will be coming. I am not deleting my account or anything ;).

So, to finish this post up, I would like to thank those who made this site possible. If I forgot anyone or anything, it shall be added.

Just FYI to my readers – I cannot access the Blogger posting interface. This has been a problem on and off for the last six months and seems to be a problem with my ISP. I’ve used a proxy to get around it in the past, but Blogger’s new security features make that not work.

I can edit my template, but I can’t edit my posts. I’m posting this from Flock. Flock does not support Blogger labels, and thus all I am getting are Technorati links in my post footer. Old posts that should be updated with new information cannot be. I will try to do some of that from school, but I cannot from home.

I apologise for the inconvenience.

FreshTags’ core has been without update for quite some time (and, I believe, does not even render properly on the New Blogger. My version has not fared much better (although I did upgrade it to work with the new blogger ). Now it is time for some improvements!

For Blogger
Full integration with the New Blogger labels system! You have to paste a small code into your sidebar, and then FreshTags will pull its data directly from your local labels! Great for new users or people who have fully migrated. Best of all, to install this takes only a few steps on the wizard. Select ‘Blogger’ as the data source, enter your blog URL, change any other settings you might want, and click ‘Generate Code’. Copy the code presented into your sidebar and then click the generated button to instantly install the widget with your settings! (Does not work on FTP blogs.)

For Everywhere
There are now three wizards for my version of FreshTags. There is one to generate the JSON for individual widgets (hackers). There is one to generate the full code for anywhere (some knowledge necessary). Finally there is one that generates a one-click button (or instructions and a button) for the New Blogger.

For MediaWiki
That’s right. Go over to BloggerHacks to see it in action. FreshTags for MediaWiki! The wizards (above) can generate the code, but it’s a bit hackier to integrate with the sidebar. Check out the BloggerHacks Sidebar and Header Section to see how I did it (click the view source wiki tab for wikicode).

For WordPress
I have updated FreshTags for WordPress (with the help of my friend, Trevor Creech) to work as a WordPress Widget. If you don’t have widgets on your WordPress blog, don’t worry! It still works the old way.

The microformats-discuss mailing list reached an impossible signal/noise ratio for me awhile back. My inbox was just too flooded with discussions I did not find interesting and I archived 90% of it without even opening it. Well, today I went browsing through the archives and here is some of the interesting stuff I found summarised for those of you with similar issues:

• Scope was discussed again, some arguing that rel-tag needs to be defined as to where it applies. The upshot (which I fully support) was documented on the wiki.
• There was some discussion surrounding microformats detection and false-positives. Discussion concerned using the profile attribute of HTML to get around this, but since parsers should check for validity of uF as well as root class existence, it shouldn’t really be a problem.
• There is a bit of ongoing discussion which I do not 100% grok. It could have to do with saying an hCard is for the owner of a page, but that is determined by whether or not it is in an
  
  element. It could have to do with two hCards being for the same person, in which case I agree that class=url, rel=me on both of them pointing to each other demonstrates that very well. Or it may have to do with seeing if an hCard is useful at all… I don’t get that.
• There was some discussion caused by the announcement of Videntity’s hCard and XFN integration (yay!) Great potential there.
• There was the age-old ‘my rel-tag URLs are crap’ issue brought on by a Blogger-FTP issue. The Blogger problem makes sense and probably will not be ‘resolved’ except by removing rel=tag from FTP blogs. Blogger-FTP is crap.
• Someone questioned the value of XOXO itself! They were kindly directed here 😉
• There is a presentation (S3!) about AHAH. Of course, AHAH is built on AJAX and thus subject to cross-domain issues. They need a JSONP version.
• Finally, another bit on proving two hCards are for the same person. In a more dangerous way.