(I'm the one who wrote the blog post, by the way)
"It's probably still a drop in the bucket, but at least she came away feeling like she did something, rather than sitting still."
Valid point. This is just something that's always frustrated me as someone who creates work with value (to those who need it), but which is also easily copied. Since sometime in my mid-teens, I've consistently failed to understand the entitlement mentality that allows people to justify the behavior that compels authors and publishers to spend time and/or money combating the behavior.
I suppose, ultimately, efforts like the one the nearly-pirated author made are the probably the most effective as they at least have a chance at educating people as to the effects of the actions they take.
Doesn't make it less frustrating though
you're spending time doing things that aren't writing, and aren't working.
People spend a lot of time doing things that aren't directly related to putting source code into the repository. That is pretty irrelevant to this issue.
But the blog post author's response is interesting to me, particularly:
"Actually going after one of these sites legally is not likely to work out well for most self-published authors: It’s like playing whack-a-mole: another one will spring up in its place if you manage to get one.You don’t have the resources big publishers do, and those guys still aren’t able to shut this stuff down."
What he seems to be missing here is that whether your response is to try to shut these things down, or whether you're going to each site and humanizing yourself - the cost is the same: you're spending time doing things that aren't writing, and aren't working.
It seems to have worked out (possibly) for the author in this case, but it's not scalable as we like to say here. You're still playing whack-a-mole, you're just doing it with a feather duster instead of a sledgehammer.