moeffju.net

Habari 0.1.1 released

Okay, seriously. Habari 0.1.1 Developer Release is now available for download and hacking:

The 0.1.1 version includes a fix for the search XSS problem and removes the misleading warning in the installer. I don’t recommend using it on a public site without being aware of the problems! At the very least, you should put your Habari install on a different domain that does not hold any important data.

You’re welcome to drop by on irc.freenode.net #habari and join us in our inspired fork… barbe… hacking!

Habari DR released; forked

Hey, don’t worry! We’re just kidding! You’re reading Habari’s April Fools joke.

Update: ForkPress made 20,070,401 downloads already! I can’t believe it!

It started with great promise, great promises, and at an opportune time. Everyone and their mother were starting to get disgruntled with WordPress - it had its share of scandals, its codebase contained a lot of baggage from ye olde times, some of Matt’s decisions didn’t go over so well with people, and some didn’t like the whole dot-com stuff going on.

Habari promised everything - a complete rewrite, using today’s technology, under a truly free license, and with a meritocratic development process. And it had a number of big names behind it.

It was a nice idea while it lasted.

It is now obvious to me that both the meritocratic process as well as truly free licenses absolutely and utterly fail to produce open, free software.

You might think this to be a strange thing to say, considering Habari finally released the Developer Review version today. Well, see for yourselves:

If I appear to be angry, it’s because I am! Scott (skippy) and Owen - both cofounders of Habari - have left the very project they founded in the dust, choosing to pursue commercial interests instead. The best part is that the codebase for their fork is probably Habari, and our choice of license allowed - encouraged - them to just take the code! Considering the timing of this decision, and the polish that went into their new projects already, it seems obvious to me that this move has been planned since quite some time — taking the hard work of volunteers, and going dot-com. And the worst part? They probably won’t hire me either, just like Automattic didn’t! In short: WTF BBQ.

I must say I feel happy about Habari’s Development Review release, but at the same time, I feel utterly betrayed. On the bright side, it is a statement about Habari’s quality, but still…

Skippy, Owen… good luck with your new ventures — ForkPress and bbqPress.

Hire me?

Update: Chris J. Davis also talks about the topic.

Habari

Habari is a new blogging platform being developed by a number of well known people, some of which are fed up with open source, others just looking for new challenges.

The thing about Habari is that is starts from scratch, and today. That means it doesn’t have to worry about a lot of existing legacy code and thus, downward compatibility. It is also being designed from the grounds up, using the latest available technology. Heck, it’s full OOP! It abstracts database access! You can plug in different theme engines (and, of course, there are plugins). In short, it could easily be the greatest thing since pressed words.

I wrote my first patches against Habari trunk today, one fixing a locale bug and making basic i18n work, the other mostly style changes. How could I resist joining the development frenzy!

Find me in the habari-dev group and on the Habari IRC channel, #habari on irc.freenode.net.

Reader Bar 0.21

Reader Bar marks the previous scroll position (the screen area visible prior to scrolling, to be exact). It helps to keep track of your reading position, especially when scrolling at the very bottom or very top of a page, when scroll steps are not integral.

Available in userscript and bookmarklet flavours. Tested with Firefox and Firefox w/ Greasemonkey.

Changes from 0.2 to 0.21: Added z-index to the marker element, to make it work right on sites like Wikipedia.

Update Jan 10th: The marker currently blocks clicks in a part of the page. This will be fixed shortly.