Hey, what’s a web site without fraudulent threats of legal action? There’s a guy out there who has bullied and blustered his way into a business running pay web sites for Playboy models under various names, primarily “Alpha Interactive” (no links provided; after all, my goal here is to convince you to spend your money elsewhere).
This is old news, but I couldn’t resist the urge to yank his chain by reposting his threats and explaining his motive in making them.
Teresa Nielsen Hayden of Making Light has a charming way of dealing with obnoxious commenters: she disemvowels them. This seems to be far more effective than simply trying to delete their comments or ban their IP addresses. She apparently does it by hand, in BBEdit. Bryant liked the idea enough to make a plugin that automatically strips the vowels out of comments coming from a specific set of IP addresses.
I don’t have any comments to deal with at the moment, but the concept amused me, and I wanted to start tinkering with the guts of MT, so I quickly knocked together a plugin that allows you to mark individual entries for disemvoweling. While I was at it, I included another way to molest obnoxious comments.
Simple little MT plugin, created as a generalized alternative to FlipFlop.
Given a list of keywords to be substituted into the template, each call to
So, after months of benign neglect and minor catastrophes, I’m updating my web sites again. We got the old munitions.com server back intact, I’ve upgraded the machine to OpenBSD 3.3, and I’ve moved this page into Movable Type. I’m even reasonably happy with the layout.
I’ve got lots of abandoned projects to resurrect, the most popular of which is of course my photo archive. I think I still get at least 20,000 hits a day from people who want it back, but the hate mail has tapered off.
So, I just got another notice about a sleazy bastard printing out my photographs and selling them on eBay. Joy. This is the sort of behavior that led me to stop posting large JPEGs a while back.
My blushes. I’ve been hacking in Perl since version 2.0 was released. In some ways, it’s my native programming language. It’s certainly the one I use the most, and the tool I reach for first when I need to solve a problem.
But I haven’t kept up. Until quite recently, I was really still writing Perl3 with some Perl4 features, and regarded many of the Perl5-isms with horror. It felt like the Uh-Oh programmers had crufted up my favorite toy, and it didn’t help that the largest example of the “New Perl” that I had to deal with was massive, sluggish, and an unbelievable memory hog (over 9,000 lines of Perl plus an 8,000 line C++ library, and it uses up 3 Gigabytes of physical memory and 3 dedicated CPUs for its 25-hour runtime (“Hi, Andrew!”)).
David Brin usually writes interesting stuff (although I was horribly disappointed by his most recent Uplift novel). This article is no exception. Unfortunately, it looks hideous. Not only is the entire thing deliberately set in Helvetica Bold, it has medium-blue text on a light-gray background, no leading, and the lines are fully justified (something that’s rarely appropriate on the web).
For more fun, the text is broken up into pseudo-paragraphs by pairs of
tags, something I haven’t seen done in years. The only nice thing I can say about the article, apart from the content, is that the lines would be a comfortable length for reading if he’d used either a few points of leading or a non-bold font.
So I went to Apple’s support site to search the knowledge base, and couldn’t read a damn thing. My eyes were a bit tired, and the search results were displayed in 9.5pt Arial. Of the many preferences you can set when you log in with your Apple ID, legibility isn’t one of them. Gosh, I wonder what would happen if I searched for “Universal Access?”