Some asshole (or assholes) keeps registering new accounts here, all from the same obviously spammy domain. I’m tired of deleting them, so I’ve disabled new-account creation for a bit. If you’re a half-mind and you want an account, let me know through email and I’ll create one.
A disconnect somehow occurred between MySQL and the script that sends reminders of upcoming events. I found it when I needed to resend them after updating tomorrow’s hash info; it’s been fixed. (As a side benefit, nobody received email with “location: TBA” in it, at least.)
I heard from another user on Slashdot that Cox had enabled IPv6 for most of its residential customers. After upgrading my router firmware and rebooting it, and then renewing the DHCP lease on my computer, it looks like I now have IPv6 working at home.
I then tried pinging the hash website. At first, DNS lookup failed. Log into the DNS provider, create an AAAA record, renew the DHCP lease again…ping6 www.lasvegashhh.com now works. It also works for our new Red Dress Run site at rdr.lasvegashhh.com.
A new version showed up. Gentoo doesn’t have it in Portage yet, but I have my own overlay on which I can do version bumps…so the WordPress 4.4.2 ebuild turned into a WordPress 4.5 ebuild with a simple
The upgrade was rather uneventful, as far as the hash website goes…just had to tweak the configuration a little bit and restart. It was a little more problematic for the Diaspora and GNU Social nodes that I also run, but they’re back in business as well.
Apache 2.4 has been around a few years now, but Gentoo just got around to declaring it “stable.” I think it previously had issues with Perl (which would’ve affected AWStats), but those issues must’ve been resolved.
Looking for a date to hare? Dates and times have been set through the end of September. Your next open opportunity to hare is 2 April (or 5 March if you want to co-hare with me on the #1337 G33K TR41L…send me mail if you’re interested). Contact Koresh or me if you want to pick an available date.
Heard from a harriette this morning that the reminder for tomorrow’s trail said 7 AM go. That definitely wasn’t correct, as the calendar says 3 PM. Must’ve been an unneeded timezone conversion in the mailer script…took it out, saw that the time was correct, and fired off another round of reminders with the correct time.
Derp! When I copied-and-pasted the Apache SSL settings from one of my other sites to this site, a lengthy string listing allowable encryption settings got cut off. This kept the site from coming up on all but the latest versions of most web browsers.
This has been fixed. The only browser anybody’s even somewhat likely to be using that still won’t work is Internet Explorer on Windows XP, and that will never work because it doesn’t support SNI. (SNI support is needed to access HTTPS websites that share a webserver with other HTTPS websites.) IE should work on newer versions of Windows (and Edge works on Windows 10). Safari and Chrome will work wherever they’re supported. As long as it’s not too old and crusty, it’ll probably work. (Hell, Safari on my old iPad that’s stuck at iOS 5.something works!)
When the new website went live, I forgot to update the mailer script with the updated iCal URL it needs to read events…oops. There was also some character-set confusion going on. That’s why the reminder for tomorrow’s trail didn’t make it out until about 8:30 (it’s scheduled for 3 AM).
On the other hand, there are 15 new subscribers since I last checked, so that part of the system is working OK. 🙂
Lazy douchebags link directly to other webservers’ images, leeching their bandwidth instead of serving up their own copy of the image. We now have protection against this at the server level. Hotlinking douchebags will get this image plastered all over their pages, instead of what they were hoping to rip off:
If I really wanted to be obnoxious, I could use Mr. Goatse.cx instead of Captain Picard, but that’d be overkill. (Don’t know about Goatse.cx? You could google it, but fair warning: what has been seen cannot be unseen.)