reStructuredText for WordPress

I’ve previously mentioned how Matthew Scott’s reStructuredText for WordPress is a good hack for making wordpress usable. However, revision 5 from the rest-wordpress bazaar repository was broken in a few ways.

The most annoying way was that the options I’d configured up the top of the file weren’t having the desired effect. I wasted the better part of an hour in debugging until I recalled how horrid PHP scoping was. It was a simple fix.

Continue reading “reStructuredText for WordPress” Marketplace spam

It came with the header:

Subject: Turn your skills into cash at Marketplace

At the very least it was annoying bacn, but it’s really spam.

In May 2007 there was an invitation to register interest in SourceForge’s new Marketplace product. I declined. Evidently sourceforge (or at least the Marketplace product manager) was disappointed in the uptake among developers, and started an opt-out bacn campaign, consisting of sending the same message to developers every few months telling them to check out the new service.

Well, bacn is one thing, but the most annoying thing was the obfuscated unsubscription procedure. The relevant sentence being:

… if you would prefer not
to receive information about Marketplace, please update your
communication preferences by visiting the Profile Center.

When these emails were sent, there was no text “Profile Center” on the SourceForge marketplace page. There have been some frustrated bug reports as a result.

So it turns out that the “Profile Center” text in the original email (which was small, light grey on white, and had no decorations differentiating it from the surrounding paragraph) was an indirect link (via to the Profile Center. The Profile Center leads to the Subscription Center, where

If you wish to unsubscribe from ALL publications
from Team, check the box and click the update button

Except that it’s not “ALL publications from [the] Team”, it’s just the spam from Marketplace.

wordpress it is *sigh*

While my search for good blogware has turned up the empty set, I’ve taken the easy option and gone with wordpress.

What did I want from my blogware? Well:

  • a minimal markup for inline formatting
  • the ability to copy and paste code without having to escape it or encode HTML entities
  • extending the code to be fun…

The only decent markup language I’ve come across is reStructuredText, although I can tolerate mediawiki’s. It does things right:

  • the markup is pretty close to what I’d use if I was posting in plain text
  • you can escape the markup if you need to
  • you don’t need to escape literal blocks (apart from indenting them)
  • it supports higher-level things like metadata, xrefs, citations

The only problem is that it’s very python-centric. Even though it’s semi-standardised, it evolves as the docutils dev team add features to the docutils processor. There aren’t processors for perl, ruby or C, so it’s not the why-aren’t-we-using-this-it’ll-work-ootb solution that, say, YAML is in its domain.

The plugin that sealed the deal with wordpress was reST for wordpress. It is a hack: it calls “rst2html“ and rips the body out, and recommends you turn off the “correct invalidly nested XHTML automatically” feature of wordpress (although this may be to avoid pre-processing, rather than because the rst output is broken).

I really wanted hobix to work. It wasn’t going to happen. Apart from the markup issues, its maintenance future doesn’t look bright. A bunch of stuff is broken, and from my exposure to that code base, adding my own plugins is likely to be anything but fun.

The motivation to post is at the critical lower bound as it is, without procrastinating about mending the posting-platform.