Monthly Archives: May 2008

Long, rambling thoughts on WPMU

I’m posting this a bit late, but just about two weeks ago I finally caught a few spare minutes to upgrade this thing to the latest released version of WordPress MU. Things went surprisingly well, especially since until that point I’d been running a “custom” version (more on that later), and this was the release that synced up all the new admin changes released in the 2.5 “regular” WP release.

I run this domain (freepressblog.org) with several blogs as well as two other domains (”sites” in WPMU terminology), each with their own set of blogs. So far no reports of any problems; the transition went pretty smoothly. Prior to the upgrade, I heard a lot of noise about the new admin UI being a hard adjustment, but in my experience, I haven’t encountered any difficulties, and haven’t heard of any from the other people who use this install.

I’ve been wanting to the “big” upgrade for quite a while now, since it was kind of a pain to be maintaining my own hacked together version. The unfortunate thing was that I didn’t really have much of a choice in that matter, as the “main” line of development in the WP project had been getting all sorts of urgent security patches and MU just doesn’t really keep up with them to the degree that I’d like.

As an example, you may remember the password hashing / salting and cookie authentication vulnerabilities from WP 2.3. These two issues were initially reported (to “regular” WP) November of 2007, and patched in that code base relatively quickly (December 2007). There was a similar ticket for incorporating the same changes into WPMU, and it was arguably (IMHO) even more important to do there, since MU installations generally have more registered, non-admin users.

I’m using these two in particular as an example because I’m familiar with them; later that month (12/2007) I submitted a patch that corrected these two issues for MU users as well, and I’ve been running it without error here on this installation ever since. Unfortunately, it was decided that these changes should follow the same path as the rest of MU - namely wait and eventually do a huge sync-up release that ports all the latest stuff from standard to MU.

The problem is that this “sync-up” release only just happened earlier this month (May 2008). This means that for anyone running only “released” versions of the software, they had been lacking these (and other) security fixes for 5-6 months. Personally, I consider that to be a problem, since running only released versions of the software should be a reasonable and safe choice for people who aren’t willing or able to hack together their own code.

There are various things that have recently kept me from being as involved in WP development stuff as I was at one point. Mostly it’s just other priorities / demands on my personal time, but I do have to admit that part of the motivation I initially had after WordCamp in San Franciso last July has certainly faded.

Even that I won’t attribute entirely to the issues I’m “complaining” about here; a good deal of it is probably just a shift in interest for me personally. But I also have to honestly admit that I do not feel as interested in pushing for / working on the kinds of things I’d like to contribute to in a project like this, since I think it’s clear that they often don’t quite line up with the values / priorities of the people who control the direction of the WP project, for better or for worse.

I imagine it’s this way with any open source project with a healthy number of contributors, and I certainly do believe whole-heartedly in the benevolent dicatorship model of guiding changes in open source projects like this. It’s just a bit discouraging when you’re on the wrong side of that equation, and don’t have the time or energy to campaign for your position, getting your patches in, etc.

Even that I wouldn’t mind much, assuming that rational discussion would be an effective way to discuss / debate the differences. There have been some unfortunate situations in which such discussions, even from core contributors, were basically ignored (here’s one, admittedly very minor issue, but still). At other times I’ve seen (and once experienced personally) what I’d consider to be reactions more grounded in emotional involvement / defensiveness than concern for the actual issue at hand.

I’ve struggled with this state of affairs for a while now, but have yet to come to a satisfactory conclusion on what to do about it. At this point, I’d switch if there were a better alternative, but I haven’t seen one yet.

I still think it’s a great platform overall, but I do think that there’s certainly some room for more serious competition. I hope to see such strong competition arise, not just for my own benefit, but for the benefit of WordPress as well.

Link - Jeffrey Zeldman Presents : Fish tacos FTW nom nom nom

Jeffrey Zeldman Presents : Fish tacos FTW nom nom nom

Fine writers are using Twitter—they’re using it even more than they’re using their personal sites, because it’s an even faster means of distributing what they have to offer, which is jokes, poems, and ideas.

Train Ride Joke

I heard a good joke on the Boag World podcast the other day, and didn’t find a short, easily linkable version anywhere, so I figured I’d just copy it here to share:

The Train Ride

A man and a woman who have never met before find themselves assigned to the same sleeping room on a transcontinental train. After the initial embarrassment and uneasiness, they both go to sleep, the man in the upper berth, and the woman in the lower berth.

In the middle of the night the man leans over, wakes the woman and says, “I’m sorry to bother you, but I’m awfully cold and I was wondering if you could possibly reach over and get me another blanket?”

The woman leans out and, with a glint in her eye says, “I have a better idea. Just for tonight let’s pretend that we are married.”

The man happily says, “OK. Brilliant!”
The woman says “Good … get your own blanket.”

Link - How to hide and show initial content, depending on whether JavaScript support is available - Robert’s talk - Web development and Internet trends

How to hide and show initial content, depending on whether JavaScript support is available - Robert’s talk - Web development and Internet trends

The solution is to include a JavaScript file in the head part of the document. If JavaScript is enabled, it directly runs an anonymous function that in turn creates a link element which only contains CSS code to hide chosen elements if JavaScript is enabl

DRMTV - Speak now…

Broadcast flag… or forever hold your peace and don’t bother complaining later.

In case you missed it, something very important happened last week, when some DVR users were prevented from recording a particular NBC television program.

By all accounts of the parties involved, it may have been a “mistake” on the part of MS and/or NBC. Leaving that discussion aside (since it’s speculation and not the point anyway) , it’s critical to realize that a test of public opinion has been conducted. Whether this test was initiated intentionally or accidentally doesn’t matter nearly as much as the results of the test, and so far they’re not encouraging.

In case you’re wondering, the essence of the test is determining how the public will react to these sorts of restrictions. Ever since the Sony vs. Universal case of 1984 established the consumer’s right to time-shift their media-consuming experience, the content producers have been looking for ways to undermine that right. (See DIVX - for those of you not old enough to remember this, it would have changed the concept of DVDs as we know them)

With the advent of digital distribution, they sought to reassert this same old claim, this time using technological means, since it had already been denied them via legal channels. Fortunately, three years ago consumers successfully rallied to defeat the broadcast flag mandate, a collusion between the FCC and the studios to take back this right from the consumer again.

With that decision, it was established that while content producers could pass a flag indicating that they don’t wish particular content to be recorded, software and device manufacturers (and consumers) are under no obligation to honor that wish, since it would violate their previously established right.

As of last week, two things are clear: some manufacturers have decided to willingly honor it, and some content providers have decided to attempt to make use of it. The test is how we as consumers will respond to those two actions. Will we make it clear that such actions are not acceptable and force them to reconsider disrespecting that right, or will we not bother since it doesn’t really affect most of us right now?

The sad answer is probably the latter. After all, tons of people have already gotten used to the idea of “buying” crippled and restricted media (music and video) from stores like iTunes, essentially endorsing the same kind of perpetual producer-ownership mentality that is behind the broadcast flag, by voting in the way that’s most meaningful to the companies involved - their dollars.

Pownce Link

Wow, I thought this post on “issues” with the latest Ubuntu version was actually going to be something significant, which would have been a surprise to me since I’ve been running this version since early alpha. Turns out it’s just total nitpicking. Oh, well.
Shared Link

(Pownce source)

Link - Crusher ~ Send invites for free

Crusher ~ Send invites for free

Note to self: use this instead of evite

Link - First Moonlight Release - Miguel de Icaza

First Moonlight Release - Miguel de Icaza

Today we are making the first public release of Moonlight, supporting the Silverlight 1.0 profile for Linux.

Pownce Message

Linux install tip: always get the “minimal” or “network” CD image. It does take longer to install and requires a network connection, but the CD never goes “stale”, and you also don’t need to download updates right after installing. Plus you can put them on those cool tiny CDs.

(Pownce source)