One bad change you may have noticed is that a handful of the posts here are now password-protected. This isn’t something I’m especially happy about, since these posts are about things I think are cool, and which I want to share with everyone. But someone smart (and with a significant stake in the matter) made the case that these posts also leaked information which could put me and others at risk.

I’ve tried to adopt the most measured response that still fixes the problem: hide only the posts I have to, and put those behind a wall rather than destroy them entirely. While I hope this is the last time I’ll have to do this retroactively, we don’t always get what we want or expect.

If you see a password-protected article, and have reason to believe I know and trust you, then you can always send email and ask for the password. Unless that trust is already established, though, you’re wasting your time — if it were something I could show to just anybody, I’d already be doing that.

Additional information (if any) will be added to this post as it becomes available.

Back on September 29th of 2009, I wrote a short article about my experiences installing Linux on the Zipit Z2. It wasn’t a huge article. It wasn’t the best thing I’ve ever written. I doubt it was read by more than a handful of people. But, dammit, it was my original work.

Today, I was doing a simple Google search for some Zipit-related information, and what comes up in my search results but a copy of my article. Seeing that it wasn’t here on mythopoeic.org, I followed the link. Imagine my surprise when I found that one Dwi Handayani had reposted my entire article verbatim. So far, so good — it’s under a CC “attribution share-alike” license; you can do that.

Screenshot of Infringing Page

He’d skipped the whole attribution part. In fact, he did one better and posted the article over his own by-line.

Here’s a link to the original URL of the scene of the crime: http://handayani-dwi.blogspot.com/2009/10/linux-on-zipit.html

If you miss the old-school flavor of Geocities, check out the screenshot to the right.

(I expect that link to be dead shortly about a day and a half from the time of my report. The Google folks are generally pretty responsive to stuff like this.)

So, to cases: No, Dwi, you didn’t write that. When you reposted it without attribution, you became a thief. When you put it on a web page above the words “posted by Dwi Handayani” you became a liar as well. The DMCA is a bad law: badly conceived, badly written, inconsistently enforced and generally an exercise in pandering to greedy corporate middle-men who are trying to drag our entire culture down along with their antiquated business model.

But for all that, the DMCA is also an excellent bludgeon to use on people like you, Dwi: people who can’t be bothered to take five seconds to comply with my incredibly generous licensing terms. My disdain for the DMCA may take the enjoyment out of using it to get your copy of my page yanked, but that won’t stop me doing so.

On calmer reflection, there are some useful lessons here as well:

• give credit — Plagiarism is among the worst academic sins, and educated people tend to react to it with outrage. It isn’t hard or expensive to throw out a credit or a link to the orignal.
• CC license is a real copyright license — “Creative Commons” doesn’t mean you can do whatever you feel like. It might mean that you can do what you want without money changing hands, but read the license first.
• provide contact information — My first reflex was to write Dwi some email asking what’s up. Had I been able to find a working contact link, we might have been able to resolve this like adults.
• allow comments — Maybe it’s my Adblock Plus, or maybe my NoScript, but I couldn’t manage to leave a comment on Dwi’s stolen copy of my article. Had I been able to say “I wrote this, and you can read the original here” then I’d have been satisfied. It was only after I found that I couldn’t that I became seriously angry.
• don’t compound theft with vandalism — I was irritated more than a little bit by the stolen copy of my article having been stripped of all formatting. Presenting my words as your own is bad enough, but making it look like I wrote a wall of undifferentiated brick-text adds insult to… well, other insult I suppose.
• be vigilant — I’d been under the impression that everything on this blog, and especially the Zipit article, was well under the “not worth stealing” threshold. I guess I was wrong about that.
• make license information easy to find — Not that it excuses plagiarism, but finding license information for posts on Small Golden Sceptre requires clicking the “Policy” link at the top of each page. Maybe I should stick the little CC banner up in the header or something?

I’m leaving out “don’t mortally insult someone while simultaneously handing them a huge stick” from the list of lessons. That’s not a lesson, that’s a thing that should be bloody obvious to anyone who takes a moment to think about what they’re doing.

Update 29 Oct 2009 1548CDT: The infringing page is still up, which is surprising (and a little annoying). I guess on balance I’d prefer the Google guys to move slowly on DMCA takedowns than for them to move quickly. My inner cynic tells me it’s because I’m not a big media conglomerate with a stable full of lawyers. I think I’ll give it at least a week before I escalate.

I was able to leave a comment on the infringing page using a bare-naked browser running in a throwaway VM. Of course, it was “held pending moderation” and I think we all know what the outcome of that’s going to be, don’t we?

It looks like Dwi’s blog is nothing but the cut-and-pasted unattributed works of others, slapped together in a big pile to drive search hits thus site visits thus ad revenues. I don’t think commerce is evil. I don’t think commerce on the web is evil. I don’t even disapprove of Google’s business model. But when they provide pointy-clicky ways for Joe Random Luser to “monetize” a web site, they have to expect that this sort of thing will be the outcome in a sad minority of cases. I just wish they were better about policing it.

Update 29 Oct 2009 2104CDT: And, it’s gone. Not just the infringing page; the whole blog. Thanks, Google team. (I have no idea if my notice had anything to do with it, but the important part is it’s gone.)

Update: 03 Nov 2009: I just got a form letter from Blogger. Dwi’s blog is back up (and seems to still consist entirely of the unattributed work of others, and ads). However, the page I complained about is no longer present. As much as can be expected, I suppose.

I’ve been henke@insync.net for a long damn time.

To the best of my ability to recall, my first email address was something or other @lanl.gov. This would be around or about 1987. After a four-year (somewhat overlapping) stint as something boring @rice.edu (Go Owls!), I wallowed in low-grade snark and minor infamy as henke@netcom.com and henke@scaly.ssc.gov. This would bring our timeline to approximately 1993.

After that, it was a move to Houston and henke@phoenix.net. I have fond memories of the phoenix account, notably the improvement in the signal-to-noise ratio of my email stream stemming from the inability of stupid people to spell “phoenix”. This was about the time spam was becoming a real problem, so although I was a frequent poster to UseNet, I munged addresses.

That brings us to 1999 (party as though it were same) and henke@insync.net. As of this writing, that account it still active. As of the dawn of 2010, it will not be. Alas, the fantastic, local, hacker-run insync.net was too good for this troubled world, and was gobbled up by texas.net lo, these many years ago. While the original domain still stands, I’ve grown tired of shelling out the Croessian sum of twenty bucks a month for a simple email forward and POP mailbox.

Thus, I’ve hired hostmonster and registered the domain ‘mythopoeic.org’, at which I’m dhenke (as there’s an ahenke also, with whom I desire email parity — while I’m still Henke of Clan Henke, that’s only for formal occasions).

While hand-crafting HTML (and/or XHTML) with a plain old text editor has long been my habit, I have come around to the view that time spent on that sort of attention to detail is time that would serve both my readers and myself better were I to spend it on content. And, Hostmonster had an easy way to install WordPress, so, well… here we are.