Wakaba 2.1.0 (48)

A new version with some minor improvements. I bumped the version number since it's not just a pure bugfix release, though. This one isn't a very essential upgrade, so no big rush to upgrade. Changes:

Slightly clearer error messages for template errors, for those who like to hack the templates.

Small fix for the example.htaccess.

Javascript code updates to behave better in XHTML mode.

FORCED_ANON implemented for Wakaba too, because recent events reminded me I never got around to that.

MAX_MEGABYTES option added, to limit the total size of the pictures on disk. Deletes old threads until the disk space limit is reached.

Slightly improved character set handling. Won't be noticed on anything but Shift_JIS boards, but I don't think any of those exist. Also, the world's most famous tripcode, #ｋａｍｉ, now works (as long as you're running Perl 5.8 or up).

Maybe I've just done something stupid, but it looks like using MAX_MEGABYTES prevents any posts but the latest from showing in wakaba.html (they're there in the admin panel and /res/postnr.html)Without MAX_MEGABYTES only the first post vanishes, after that things work as expected (I think) until I bump the hidden post, which makes the bottom post disappear. Madness.

Other than the required sql/password settings all I've set is a title, favicon and a higher filesize limit. Oh, and I'm running without captcha's...

I think I jumped to conclusions due to retarded testing earlier, or maybe nuking the board sorta fixed something, but what I'm seeing now (with MAX_MEGABYTES on) is the bottom post in the management panel not showing up in the html board pages.

Maybe nobody noticed the pages listing one less post than they should on boards that are actually populated? The fist post I made didn't show up, that's something you do notice...

I get this trying to follow the instructions to set up oekaki:Bareword "CSS_FILE" not allowed while "strict subs" in use at oekaki_style.pl line 332, <FILE> line 5.Compilation failed in require at wakaba.pl line 19, <FILE> line 5.BEGIN failed--compilation aborted at wakaba.pl line 19, <FILE> line 5.

I fixed it by forcing the CSS to css/futaba.css, but that kind of sucks.

18 Post deleted by user.

Oops. Actually the code that broke there isn't even used - it's some old left-over code from when I did some rewriting, that I forgot to remove. You can just remove that whole function and it'll work just fine. Alternatively, get the fixed version:

Shii found some bugs in the oekaki_style, and I found some more in the futaba_style (nothing very important, though). I also re-wrote some of the oekaki code to be less stupid and bothersome (it no longer needs to post through the webserver).

On Futaba and I also believe 2channel, I believe this to be used as a severe warning for asshats and trolls. It's not yet a ban, but a very harsh reduction of privacy and revealing of all the posts by the usually anonymous abuser to the public as coming from one person, etc.

-I'd like a 'view all posts from this ip/subnet/username' option in the admin panel if that's possible. I know we talked about it and static pages, etc. but it's worth an asking, I suppose. -Scaleable administration (ie, mod status and admin status with different permissions)-Forcenick and/or force anon for one user-Maybe word filters? Kinda silly but sometimes fun. If you do it, make sure to allow html injection in the filtered text, because what if someone wants to make it a picture?

I'm sure I'll come up with other stuff, which you can also feel free to ignore.

I've been thinking it would be useful to be able to add small bits of Perl code that are run for each post. These could then implement nick filters, word filters, or whatever mischief you feel like doing.

Also, there is already two levels of admin, after a fashion - the normal admin password, and the nuke password. I haven't yet seen any use for subdividing it further, though.

I'm not sure about converting GIF to PNG, though. There might be a small decrease in size, but generally I think it's a better idea to keep files untouched as far as possible, for the purpose of conserving checksums and the like.