Officially, today is the 2,000th day of the survival of this website. When I first started off in late 2007, I was curious how long will it last before I take it down. 5 years later, it is still standing here today.
The significant part of it is, there will always be a post each month, since the day the websites was launched. I have made it a point to ensure no month is skipped. Well, I guessed the record remains in tact.
The second thing about the site is, every post (not page) is accompanied with an image. There were times when obtaining relevant image is an issue, but I’m glad there is always Google around for help.
Hitting the next 1,000 will be a challenge, hopefully the site will still be around when it reaches the next thousand.
This happened about a few minutes ago. Whilst checking for SPAM, I saw a remark at the top of my WordPress Admin site saying that Akismet has detected a problem. I don’t know if it’s only me, but it happened across another WordPress site owned by me (hosted on the same server).
I hope that this is only a temporary issue and that it gets resolved soon. Spam is growing every second and I cannot wait for another tick on the clock to inform me how many thousands of spams have been generated on the site.
Ever since I started writing on this website, I installed Akismet and today, collected 5 years worth of data. From the trend, spam is growing at a pace that it is slowly spinning out of control. Thanks to Akismet, my website has been kept alive by constantly removing spams, which could potentially overload the server with resource demands.
Simply by looking at the past 24 months of data, we are only at midway through 2012. Already, we have exceeded the volume of spam that was generated in 2011. I expect the volume for 2012 to be doubled.
This is the downside for all website owners who have to live with these spam creators. Be thankful that we still have Akismet – but if one day Akismet decides to charge for using the service, that will be D-day for all website owners.
Today, I decided to log on to my Bluehost account to check the health of my account. To my surprise, my web hosting company has been tweaking the server, such that my sites have been heavily throttled.
So, what does that mean? When the server throttles, CPU power is limited to that particular account. It makes a lot of difference if sites are running dynamic scripts, such as PHP, ASP or CGI scripts. HTML scripts, which are mainly static scripts, are less likely to be affected.
There are pros and cons to this. The positive side of it, is that the server will be more stable and unlikely to crash, which is invaluable especially where downtime is a major concern. The negative side of it is, it will take a longer time for the site to load. To some extent, if it is heavily throttled, the site may not even appear. This situation happens when sites do not enable caching, and encounter huge volume of traffic at the same time, consuming large amount of CPU resource.
So far, I have no complaint, as downtime is far more important to me. Perhaps, what I should do next is really optimise my sites – for those that encounter large volume of traffic – I should look at caching mechanism.
After so many years of sticking with Akismet, I remain a satisfied person without worrying that my blog site will be plagued with countless spams. Recalling back when even before I first started on this site, I am already a frequent user of Akismet, but just did not know how long I would stick with it.
Today, it has proven its worth as the leader of Blog Anti-Spam machine. I have even extended its use to forums, such as Simple Machine Forum (SMF), where Akismet could easily be installed with little or not hassle.
Once again, I would like to express my heartfelt thanks to the organisation for providing a “free” service to end users, like us. Keep the flame burning!
Google AdSense has recently sent me a reminder to advise me on how to improve the success of Ad Crawler on one of my websites that I hosted. It arises when Google detected a couple of failed crawl requests. I guess the reason is because Google is engaging a third party partner to help them work on crawling.
The following advise was given by Google:
Edit the robots.txt file to allow AdSense crawler by adding these two lines to the very top:
Note, that does not affect or impact the SEO or ranking of the site; but it does provide user with more relevant targeted ads.
Unbelieveable! ScribeFire Next 4.0 is the new redesigned interface of the classic ScribeFire plugin for Mozilla Firefox browser. The comment about this new product is such that it is simpler and easier to use. And it is absolutely right.
I wasted no time to create my first post instantly from this plugin. Furthermore, I could even upload images to the appropriate “upload” folder without a hitch.
Having done the initial testing, I urged all users to download and use this application. It simply helps you work more efficiently and effectively. I don’t see myself having to log back on to WordPress everytime I needed to create a new post. Good job, cfinke!
With a sense of curiosity, I decided to give WordPress 3.3. Beta 3 a try. Well, guess what? Besides the fanciful stuffs, such as new:
- Media uploader
- Improved admin bar
- Fly out admin menus
I realised I could not upload any image on this post. It may have got something to do with my plugin. So I’m going to check it out to see if that’s the case.
In addition, the new beta release seems no longer “respect” the function, $user_level. Not sure if it’s only me, but it is what’s happened to my script.