Buckshot, Ep. 5: Sidegrading
- WordPress is on Slashdot, courtesy of the above image.
- I've upgraded myself, although based on the number of offers for help installing Habari I landed myself with one comment on WW, I'm going to give Habari another shot in the near future.
- That thread made me realize that Habari is not a WordPress fork at all, but a WordPress clone. It's the same relationship that Pidgin (Gaim) has to AIM: most of the features, none of the crap, none of the code.
- My only reason for upgrading is to work on adding the tagging features to Disconnected and Dream in Infrared. Dream in Infrared will most certainly drop support for UTW, as well as any compatibility with 2.0 . Disconnected will be a bit more difficult, since I'll need to maintain UTW/2.0 support in parallel with 2.3's tagging.
- The above assumes, based on the announcement, that there were no security patches in 2.3. Like Anil says, though, things like that should be crystal fucking clear in the announcement. Then again, we are talking about matt, who needs public outcry to explain simple things like privacy policies.
- Further problems resulting from the Refusal To Explain Anything:
as I was going through my list of plugins and upgrading them using SVN (it's even suggested in the announcement), i ran into more than a few plugins that are hosted on wordpress.org, but have to be updated the traditional way, because no one knows how to organize their repositories. The biggest offender is the Google Sitemap Generator, which has all of the translations in /trunk/. Subversion naturally balks at the encoding. Wget to the rescue.
- This is surprisingly not related to Matt or privacy, but I've switched to defensio anti-spam, because I'm a fickle sum-bitch, and easily enticed by betas. So far its false-positive ratio is about on par with Akismet, which has the usual social consequences (sorry Trent, Engtech). It does marry the excerpt concept from Akismet Auntie Spam with "Spaminess", which is vaguely similar to SK2's karma, giving it the best usability of the 3.
7 Comments
w00t. Here’s to not drinking the Kool-Aid.
When I use wget for the Sitemap plugin, I get encoding problems, because there’s some file in the trunk that’s not UTF8. Fucker.
wait, we’re toasting to not drinking?
I used SVN for sitemaps, so I can’t say what the error there is. I also don’t know if that’s an issue with the file, the webserver, or the wget/SVN client. damned confusing.
Mad props to you for getting sandbox 1.0 out the door before 2.3 dropped. Adding tags to themes is a pain. Supposedly Christine (UTW) is working on a plugin that just mapps the UTW tags to their corrosponding 2.3 template tags.
No problem on the “spam queue”. I’d spam me too if I was the filter
why - are you using Tor or something? I just snagged comment number 3 out of the bin.
Just joking! I guess this is spam 4?
What gave you the impression that Habari was a WordPress fork? Actually, I’d even disagree that it’s a WordPress “clone”.
Sure, we want most of the same features - it’s blogging software after all. But architecturally, we’ve made a lot of design decisions based on knowledge of how modern blogging works and what people may use their software for.
I think that users who try Habari will be pleasantly surprised by the subtle differences.
boy, i sure can’t remember where i would have got the idea that it was a fork
all kidding aside, it’s not that i’ve ever thought of it as a fork, but it’s commonly referred to as such on WW and other places. And yes, most clones outgrow their inspiration, (pidgin is a great example, again).
Post a Comment