The Dilemma

This brings me to the great dilemma one must face when carrying on with a blog – there is an inherent administrative burden by enabling people to post comments on your blog. The biggest problem comes where people spam the hell out of your comments with things like penis enlargers and sexual enhancement products – things that obviously have no business being splashed anywhere. The interruption in my daily routine to remove this rubbish from my blog is seemingly not worth it.

Opening My Eyes…

So I thought about it some more, and looked at things from the same perspective that I wrote the article about Mixx and Digg and I began to realize what a fool I was being for not allowing people to comment.  My focus is on social media and web development.  These are two things that rely on communities to provide input.  I took a step back, fell off my soap box, and realized the only way to fix this was to provide ready access to people for their commenting pleasure.

Bracing For Impact

In any case, I’ve enabled registrations (which I obviously encourage) but I’ve also granted access to not-logged-in comments. I don’t want to deter people from commenting due to a required registration.  I’ll just hope that this new ability is not abused to death by the darkness on the internet and is actually used for constructive feedback and discussion.  If it’s abused and ravaged by spammers then I’ll have to find a solution to that problem when it arrises.

Thank you father dearest.

The Problem – Why You Should Care

Other sites that you pull content from are not always going to be reliable.  They could be down, running slow, or some other possible problem.  If you are using something like twitter to display your status on your site but you have a lot of other content you want people to see then it would be wise to use client-side scripting to get the content.  You might be saying in your head “Oh but I have this sweet PHP script that does that for me.” but you should tell that voice in your head to shut up and just listen.

The Solution…

When you use server-side scripting then the server that is dishing out your website needs to go to the other (possibly) slow website.  If it’s waiting for this content then your user is waiting for your site to finish being generated server side and then sent to their browser.  This was a problem when twitter was doing its thing with the “fail whale” on a regular basis and was generally taking forever to display tweets.  This in turn was making my site very slow.  Realizing the problem, I took out the PHP widget that I had and replaced it with my own little creation that utilizes javascript and a tiny bit of PHP.

Let’s take a look at how to do that…

First thing you’re going to want to do is make a little div with some static text in it that gets killed when your stuff finishes loading.  You can make it kinda like this:

<div id=”twit_text”>
<ul id=”twitter_update_list”><li>Waiting for Twitter.com to reply.  Please hold.</li></ul>
</div>

The ul in there will be replaced by the script which actually sits right on twitter’s servers.  This is pretty simple and basic stuff.  It is advisable to put some static content in there so that users know that something else is going to happen and you don’t have a blank spot on the page.  There is one other piece of magic that actually uses a little bit of PHP but not for the same purpose the other scripts use it for…

<?
$currURL = currPageURL();

if (($currURL == “http://www.patricktulskie.com/”) || ($currURL == “http://patricktulskie.com/”))
{
echo “<script type=\”text/javascript\” src=\”http://twitter.com/javascripts/blogger.js\”></script>”;
echo “<script type=\”text/javascript\” src=\”http://twitter.com/statuses/user_timeline/PatrickTulskie.json?callback=twitterCallback2&count=1\”></script>”;
}
?>

This goes in the footer of the page to only load the javascript if the page you’re looking at is the index page.  You can modify the PHP to load on different pages but for my purposes I only want you to see the status on the index.  You can’t easily do this with a plugin because plugins are loaded entirely as the page loads.  The PHP above is in the very footer of the page and it only kicks off the javascript IF we’re on the index of the site AND after everything else on the page has already loaded.

One Other Thing…

I use this function to get the URL of the page.  You can put it in your wordpress theme’s functions or you can put it wherever you need it on your site.  It’s fairly reusable too.

function currPageURL()
{
$pageURL = ‘http’;
if ($_SERVER["HTTPS"] == “on”) {$pageURL .= “s”;}
$pageURL .= “://”;
if ($_SERVER["SERVER_PORT"] != “80″)
{
$pageURL .= $_SERVER["SERVER_NAME"].”:”.$_SERVER["SERVER_PORT"].$_SERVER["REQUEST_URI"];
}
else
{
$pageURL .= $_SERVER["SERVER_NAME"].$_SERVER["REQUEST_URI"];
}
return $pageURL;
}

I Hate Twitter

Well thats fine.  I’m sure it doesn’t like you much either.  Regardless, this is a really basic usability concept that many people don’t seem to grasp or even think about when creating a website.  Say you want to pull news feeds from a Digg category using an RSS parser on your page.  You have other stuff on the page but this Digg box is in your sidebar.  If you don’t think about where the script is going to execute in relation to your page loading, then you’re going to have problems when Digg is running slow or is down.  For those of you who don’t want to get into a full blown ajax setup, or simply don’t know how to then this is a great work around that uses really minimal coding.