http://wakaba.c3.cx/releases/wakaba_20041113.zip
This release incorporates some changes ported over from the new Kareha release, and a couple of requested features.
>>1
references (implemented client-side in Javascript as opposed to Futallaby's server-side, though).>>1
reference in the comment field - another stoled feature.People upgrading may want to make the same change I mentioned for Kareha: Edit config.pl to remove all entries that are just set to defaults. This makes things cleaner and easier to maintain. The config_defaults.pl file will handle setting all unspecified options to default values.
Next up for Wakaba is an attempt to re-do it in proper structured XHTML, to better support styles and such. Let's see how that goes.
I almost forgot to mention: there's now also support for not using a thumbnailer at all! If you turn on STUPID_THUMBNAILING
, Wakaba will inline the image and use width
and height
attributes to resize it, just as stupidly as futaba does!
Don't do that.
Oops, left in a small mistake (wakaba.pl was trying to use the experimental wakaba_style.pl instead of futaba_style.pl). Fixed here:
Feature request for next version: make upgrading less of a PITA, please. :/ True multiple-board support (instead of having to have a different copy of the script for each board) would help; I would only have to do things once instead of four times... I imagine that'd be a heck of a change to implement, though.
Yes, that will probably never happen. I enjoy the simplicity offered by dealing with just one board at a time. Upgrading should, however, be much simpler now with the new config system.
Also, I've been meaning to put together a tips and tricks section for the docs to explain these things, but there are many things you can do to make this easier. On iichan, for instance, we had just one copy of the script files, and each board had softlinks to this, and its own config.pl.
And again!
http://wakaba.c3.cx/releases/wakaba_20041114.zip
This time, another really small bugfix. I ported over the ALTERNATE_REDIRECT option from Kareha, which is needed to run properly on IIS, it seems. No need to upgrade unless you are actually running on IIS.
>On iichan, for instance, we had just one copy of the script files, and each board had softlinks to this, and its own config.pl.
Hmm. That's actually a good idea. I'm trying to do something similar by keeping most of the common files (like futaba_style.pl) at /
, but then I have to go through wakaba.pl and such and tell them that that script is now at ../futaba_style.pl
. Soft links would definitely be an improvement over that. I'll keep that in mind next time it's time to upgrade. Thanks.
hmm... how about rss feeds for wakaba?
http://hotaru.freelinuxhost.com/w/
http://www.nchan.tk/
I was going to say that it just promotes leeching, but I noticed you don't actually include an image link in that RSS file, which makes it a lot funnier.
Also, the comment link seems broken.
>>11
only the first link is broken, all the rest of the links work...
i'm not sure why the first one is broken...
I think the post abbreviation needs to be worked on. Right now, if the post is 1 line too long, just that 1 line is being hidden. I'd rather have it so that more would be hidden, i.e. that the default value for "too long" gets risen considerably. Also, I think post abbreviation should only be turned on by default on Kareha, not on Wakaba, as it rarely has a purpose on the latter.
Putting in a threshold like that isn't a bad idea, but a little bit trickier to implement. I'll put it On The List. If you disabled it, though, you know somebody would post about four thousand newlines just to be a dick. In all, the post abbreviation is much less annoying than the futaba-style disappearing newlines, which it replaces. However, I did set the APPROXIMATE_LINE_LENGTH lower in Wakaba than in Kareha, which makes it abbreviate a bit quicker. I'll change that so it's the same as in Kareha.