After recently posting that I’m using WPSuperCache, I had to turn it off. The .htaccess file manager wiped out the line that is needed for WordPress to do automatic updates on my hosting provider, and somehow managed to get itself in a state where the admin pages themselves were being cached. Nearly nothing worked, until I finally got the sense to backup the .htaccess files, disable WPSuperCache, and see what had been broken. The following line was needed to make the updates work again:

AddType x-mapp-php5 .php

Hopefully next time it breaks, I’ll think to look here.

This is my foursquare perl client – 4sq. There are two things you will need to do to make it work. First, base64 encode your username and password with a “:” between them, and stick that value into $password. Second, add location entries to a config file. (The format of this file is explained in the help section of the script). That’s it! You can then run it through cron or whatever you prefer.

The code could be a lot cleaner, but here it is. It’s been mostly a late night toy to play with – I finally got bored and figured it was done, so I booked a fake trip through my favorite travel agency, crontab -e.

Photos taken at high ISO values from Nikon’s new D7000 prosumer camera are starting to show up on the web. ISO 6400 is amazing, and the shots at ISO 25,600 don’t even look all that bad. This means that $1,200 USD buys you a camera that rivals the ISO performance of everything Nikon makes, other than the D3 series and possibly the D700. Those cameras are $2,400 and $4,000+ at the moment, and represent Nikon’s professional lineup of DSLR bodies.

The D7000 also has a higher megapixel count than everything other than the [$7,399 D3x][3].

Which means whatever Nikon releases to replace the D700 is should be amazing. And it’s getting really hard to wait for The Next Big Thing, when the New Big Thing looks pretty damn tasty. I’m sure there’s professional features on my D200 that are lacking in the D7000 (like the intervalometer), but the D200 (my current camera) tops out at ISO 1600, and looks pretty bad doing it.

[3]: The shots at ISO 25,600 don’t even look all that bad.

I’m writing a foursquare command line client in my free time – mostly so I can script my checkins, and learn the ins and outs of a staggeringly simple API. It’s also an excuse to play with AppConfig, IO::Socket::SSL and Getopt::Long. It’s an extension of an idea by Mayank Lahiri to have a perl script that can checkin to the service. I started with a very simple implementation, but I’ve expanded to slightly loftier goals. If anyone wants to grab the code and laugh at it, let me know, and I’ll post it.

Now that I’m posting somewhat more regularly, I’ve updated/activated WPSuperCache on the site. This means, on the off chance I get dugg/slashdotted/farked/whatever, the site may actually survive the traffic. It did require me to setup a proper permalink structure, which I’ve done – but not to worry, the old links still work. After the change,

<a href="http://www.gurucollege.net/blog?p=1000">http://www.gurucollege.net/blog?p=1000</a>

is the same as

<a href="http://www.gurucollege.net/blog/technology/dual-mode-networks/">http://www.gurucollege.net/blog/technology/dual-mode-networks/</a>

Make sense? Doesn’t matter, it works.

I must be tired. I was trying to debug a bit of code I had been working on last week before traveling this weekend, and I couldn’t figure out what had changed. Was the API different? Did something with the code break? Did I need to use SSL due to a recent API change?

No. I had added an “exit 0;” statement to keep my debugging from running amok, and had forgotten to take it back out.

A while ago, I wrote a Nagios plugin that checks the Google Apps Status Dashboard for problems, and reports WARNING level alerts when things happen. (I didn’t want to flag these issues as CRITICAL, as there’s nothing our on-call staff can do to fix the problems.) It would be best to attach the service definition to a hostless object – that is, a Nagios host object with the IP set to 127.0.0.1. This way, you don’t have to worry about reachability logic.

The script itself is written in perl, and requires the module JSON::PP. It also makes a hard coded system() call for ‘curl’ to pull the JSON data object from Google’s servers. (At some point I’ll move that to LWP::Simple or something similar, but at the moment it is what it is.)

Basic usage information:

`A while ago, I wrote a Nagios plugin that checks the Google Apps Status Dashboard for problems, and reports WARNING level alerts when things happen. (I didn’t want to flag these issues as CRITICAL, as there’s nothing our on-call staff can do to fix the problems.) It would be best to attach the service definition to a hostless object – that is, a Nagios host object with the IP set to 127.0.0.1. This way, you don’t have to worry about reachability logic.

The script itself is written in perl, and requires the module JSON::PP. It also makes a hard coded system() call for ‘curl’ to pull the JSON data object from Google’s servers. (At some point I’ll move that to LWP::Simple or something similar, but at the moment it is what it is.)

Basic usage information:

`

You will get the same thing if you call the script with a misspelled or nonexistent service name. Otherwise, you’ll see the status of the app in question:

``A while ago, I wrote a Nagios plugin that checks the Google Apps Status Dashboard for problems, and reports WARNING level alerts when things happen. (I didn’t want to flag these issues as CRITICAL, as there’s nothing our on-call staff can do to fix the problems.) It would be best to attach the service definition to a hostless object – that is, a Nagios host object with the IP set to 127.0.0.1. This way, you don’t have to worry about reachability logic.

The script itself is written in perl, and requires the module JSON::PP. It also makes a hard coded system() call for ‘curl’ to pull the JSON data object from Google’s servers. (At some point I’ll move that to LWP::Simple or something similar, but at the moment it is what it is.)

Basic usage information:

`A while ago, I wrote a Nagios plugin that checks the Google Apps Status Dashboard for problems, and reports WARNING level alerts when things happen. (I didn’t want to flag these issues as CRITICAL, as there’s nothing our on-call staff can do to fix the problems.) It would be best to attach the service definition to a hostless object – that is, a Nagios host object with the IP set to 127.0.0.1. This way, you don’t have to worry about reachability logic.

The script itself is written in perl, and requires the module JSON::PP. It also makes a hard coded system() call for ‘curl’ to pull the JSON data object from Google’s servers. (At some point I’ll move that to LWP::Simple or something similar, but at the moment it is what it is.)

Basic usage information:

`

You will get the same thing if you call the script with a misspelled or nonexistent service name. Otherwise, you’ll see the status of the app in question:

``

I hope to have the paperwork done in the next week or so.