Dianne Feinstein should resign

Here’s a nice opinion piece. By the Christian Science Monitor, no less.

I concur.

Dianne Feinstein has a history of getting policy around cryptography and security utterly and disastrously wrong. She backed the regressive ITAR regulations banning export of strong crypto (which had the actual — and intentional — effect of reducing security of software in the US). She backed the Clipper Chip program in the 1990s, claiming a need for “balance” by mandating that US citizens use only government-approved cryptography (the Clipper protocol contained serious flaws which were exposed a few months after the specification was published). She backs the FISA secret courts. She has refused to investigate wrongdoings by the NSA and other intelligence communities, or to investigate the clear and blatant lying by government officials about surveillance programs to congress (last I checked perjury was still a pretty serious offense; Senator Feinstein is apparently just fine with it).

She has so clearly demonstrated her incompetence and misservice to her constituents and to the US at large that we should be done with her. Dianne Feinstein is a danger to our collective security, and she should either step down, or be removed from the Senate Intelligence Committee.

Attending a modern political debate


Don’t use pine for your sign handle. Instead, find some good ash or hickory, the kind they use to turn out good quality baseball bats and axe handles. For the sign itself, a thicker gauge of sheet steel is best. Steel is heavier but lots more durable than cardboard or aluminum, and it takes and gives a beating. Steel also carries a nice, sharp edge that is unparalleled when you need to make an effective argument, and it will get your message across even if you can’t spell worth a damn.

Get a real pair of boots, okay? You may be into hi-top sneakers or loafers, but a good pair of steel-toed work boots will do wonders for your confidence. Just knowing that you can kick the shit out of someone who’s holding onto a weak or immoral position will have you unconciously holding your head high, your shoulders back, and wishing that you’d sprung for the fifty dollar truncheon instead of the one from the bargain bin.

Speaking of truncheons: Rubber-coated, steel core and integrated lanyard. That’s all you need. If you have something that takes batteries, that’s a goddamned flashlight and you’re going to look awfully silly trying to make your point once the D-cells have flown across the room because you forgot to Lok-Tite the cap. Use the right tool for the job.

That super-sized, cherry-red can of Obliterator! brand pepper spray indicates that you are a nOOb. Watch the old timers; they choose their targets with economy, generating maximum outrage and news footage with a few well-placed shots. You honestly don’t need more than a couple of ounces, and even a little of the cheap stuff goes a long way. Try some on yourself if you don’t believe me.

It’s amazing how many people will fight to the death for their right to remain indifferent.

Feinstein wants to ban crypto again

Senator Dianne Feinstein is introducing a bill that attempts to ban the use of strong cryptography in the US. Link.

She supported crypto bans in the 1990s. I was a constituent of hers then, wrote her with my concerns, and her canned reply was a basic “FU, we need balance, blah blah.”

Now she’s at it again.

Q: Feinstein is a lying and puppeted sack of crap, one of the worst things to happen to civil liberties since J Edgar Hoover, and can’t leave office soon enough. Discuss.

Oh yeah, call your senator. Do that.

Yeah, pretty much done with GoDaddy

While I’m sure y’all are nice folks at GoDaddy, I think you get what you pay for in this industry. And I’m willing to pay a little more to get better service. Like, a web server infrastructure that doesn’t randomly throw 403 errors (sometimes for days). And something that won’t utterly collapse if I get noticed by HN or Reddit. (Collapsing is understandable, but I expect the hosting system to at least put up a good fight).

So I’m shopping around for a better provider. I don’t need much: WordPress (maybe), and shell access. And a reasonable expectation that the company will be around some years hence. That’s about it.

Any recommendations?

Documentation is for the weak

I spent several hours reading some “documentation” today for a certain component of an enterprise product. Actually what I was doing was a repeated loop of the following:

  • Go to a page with a promising-looking title (e.g., The Fuckwidget Survival Guide)
  • Read some of the marketing-class vacuous bullshittery there, with a table of contents consisting of:
    • Overview of Fuckwidget
    • Introduction to Fuckwidget
    • Fuckwidget Operations Guide Overview
    • Fuckwidget Migration Patterns
    • Fuckwidget Introduction [didn’t we do that one already?]
    • Using Fuckwidget
    • Fuckwidget Infrastructure Templates
    • Fuckwidget for Beginners
    • Executive Guide to Fuckwidget
    • Fuckwidget Tutorial for Knuckledraggers and Mouthbreathers [didn’t we just do that one?]
    • Let’s Do Fuckwidget! (plus a crayon drawing of a cat by some VP’s kid)
    • Make Fuckwidget work for you with this One Weird Trick!
    • 10 Things You Didn’t Know about Fuckwidget
    • Fuckwidget FAQ

“Oh ho!” I whoop, and click on the promising-looking FAQ, and like a hall of mirrors I’d find myself in a document pretty much the same, but slightly different. Repeat for hours. Every time the documentation was about to admit a tidbit of actual, useful info, there was a link, and the link led to even more bullshittery.


  1. Cry out “God in heaven, does any of this crap lead to any actual information about how you set up and use Fuckwidget?”
  2. Wait for an answer.
  3. No answer from God. He must be using Fuckwidget Message Queues for incoming prayers, it would explain a lot.
  4. Do another web search for “real fuckwidget documentation dear lord let it all end now” and start over.

This is an actual picture and probable copyright violation [ask me if I care] from some of that “documentation” –


I think there’s a bug here, where they left out the part where you’re supposed to feed the security policy to a magic goat, whereupon magic shit happens that materializes into a security policy. Frankly I don’t think that anyone will be able to prove my little repurposing above, since I’m probably the first person to ever get far enough into the maze to find it.

Can we analyze this bit of art? Is it useful at all, to anyone? Well, yes, it turns out:

  1. Once upon a time there was a documentation team, on contract and paid by the hour by a large, soulless corporation that confuses quantity for quality.
  2. This team knew a good deal when they saw one, and sat in their seats and typed like crazed monkeys for as many hours as they could bill. They wrote introductions and overviews and guides and planning thingies and checklists and templates and any number of click-here-do-this-click-that instructionoids of the kind you find on really sketchy “How do I use a can-opener?” sites. The result was a massive collection of pages with a remarkable lack of useful information. And this was absolutely intentional, because:
  3. When the stone had been completely wrung dry and the documentation team could extract no more hours, the large corporation shipped the documentation out to users, and:
  4. The doc writers went back home and wrote a real reference and are happy to sell it to you for hard cash. It’s probably really popular on Amazon. I do not have the heart to search for it.

I think if I sat down for a couple of hours I could distill the documentation for this product down to about three pages, starting with an introduction like:

Hi. We know why you’re reading this, and we’re real sorry. It may help you to know that all of the suffering you are about to endure is the same suffering we went through. Of course, we had the advantage of access to the original team, so maybe we didn’t suffer quite as much. On the other hand, it may bring a smile to your face that the feedback we provided to the developers and managers was in some cases sufficiently convincing so as to ensure they will never be repeating the mistakes they made on this project. They’ll never woik in dis bidness again.

In the end, I kind-of got Fuckwidgets working. I wrote a wiki page for my coworkers with some “click here, do this-and-that” type instructions, and I feel filthy.

Bullshit triumphs when a good man does nothing.