PolarBlog V1.5.0 Beta
I'm now running what will be V1.5.0 on this blog. Let me know if you run into any problems in your travels. Until I get the documentation done, a quick rundown can be found in the changelog. This should be released next week.
I'm now running what will be V1.5.0 on this blog. Let me know if you run into any problems in your travels. Until I get the documentation done, a quick rundown can be found in the changelog. This should be released next week.
I don't know how I managed to do it, but I put the wrong link in the PolarBlog default config file for my own blog!!! Anyhow, if you left the link to my blog on your list, could you please update it? Open your config file and look for this block (near the bottom of the file):
$config['blogs'][0] = array( 'url' => 'https://www.polarlava.com/', 'title' => 'PolarLava', 'desc' => 'Brainwork from the lava flow...' );
If you would, please change the "url" value to read:
'url' => 'https://www.polarlava.com/blog/',
Thanks,
The Braindead Developer
Now that PolarBlog's usage has grown beyond, oh, I don't know…me, I've been contemplating putting a "user's page" on the site. This would basically just be a list of linked sites. I guess a "these people use PolarBlog" sort of thing. If you're a user and you'd be interested drop me an email (kevinp AT polarlava.com) or comment.
-klp
2/3/2005
Being that for the most part I'm the only one that reads my musings, I've gone through my referal logs and tracked down a number of sites that are currently running PolarBlog. From this I've now added a PolarBlog Users page to the PolarBlog site.
I guess the release of PolarBlog V1.4.0 was timed just right…
This morning when I checked my email I had a message that a comment was posted to my Ski Masks blog entry. Initially I thought there might be another bug because the message was just a URL, not a text message. Upon further review I must proclaim that PolarBlog is now officially "mainstream" as this is the first known incident of comment spamming. It came from 218.79.133.250 located in China. It says it's an assigned address so I'm going block it by the full IP and see if I need to block a range or not.
The next major milestone for PolarBlog is making it to "Big Time" status. That's when your PolarBlog installation starts getting flooded with automated comment spamming…which at this point I don't believe this to be. We shall see if the rogue returns.
PolarBlog V1.4.0 has been released. This release contains…
Enhancements