http://wakaba.c3.cx/releases/wakaba_2.1.0.zip

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).

This release seems to have come in the shadows of Kareha 2.0.0.

Anyway, it is appreciated. I will update my boards later this day.

Shouldn't there be some way to select language in config.pl?

That would maybe be a more elegant solution, but for now you have to change the strings_*.pl line in wakaba.pl.

what's #ｋａｍｉ

>>5

It's THE WORLD'S MOST FAMOUS TRIPCODE.

hm?

>>6

Question: why?

>>7 needs more #ｋａｍｉ instead of #kami.

>>8

Back when 2ch was using 8-character tripcodes, somebody noticed #ｋａｍｉ gave the tripcode AhoNiShI, which means something like "idiot west". Hilarity ensued.

Ｉ’ｍ　ｗｒｉｔｉｎｇ　ａｌｐｈａｎｕｍｅｒｉｃ．

Ｗａｈ，#　ｃｏｕｌｄｎ’ｔ　ｂｅ　＃．

I just upgraded to 2.1.0 and posts are disappearing...

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.

Hmm, that sounds pretty weird. Lots of boards run 2.1.0, but none have reported anything like that. What other options do you use?

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...

Hmm. I'll look into it.

Turns out you're right, the last post is always ignored when generating the main pages. Fixed in this version:

http://wakaba.c3.cx/releases/wakaba_2.1.1.zip

I also added the USE_XHTML option to disable application/xhtml+xml mode if you don't like it. Changes to wakaba.pl, wakautils.pl and config_defaults.pl.

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.

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:

http://wakaba.c3.cx/releases/wakaba_2.1.2.zip

Changes only to oekaki_style.pl and config_defaults.pl (for the version number).

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).

http://wakaba.c3.cx/releases/wakaba_2.1.3.zip

Changes to wakaba.pl, wakautils.pl, futaba_style.pl, config_defaults.pl, and a lot of the oekaki files.

Oops, didn't get it quite right. Fixed fixed:

http://wakaba.c3.cx/releases/wakaba_2.1.4.zip

Changes to wakautils.pl, finish.pl, oekaki_style.pl and config_defaults.pl.

So what do you think will be the next "OMG go upgrade" feature in Wakaba? Is one planned?

>>23

I vote IP revealing feature for mods.

Ideas for future features, for whenever I feel like writing some code:

• Catalogue mode, like on futaba's /b/.
• Automatic hello kittying for mods.
• IP revealing.

Anything else?

> Anything else?

• Marked for deletion (old)

http://wakaba.c3.cx/sup/kareha.pl/1107187664

• Turning off Wakamark when AA in Link field

http://wakaba.c3.cx/sup/kareha.pl/1102984488/46

IP revealing? You mean being able to display someone's IP by going into the Admin panel? What for?

Is there a way to add a single file type to the allowed list?

> Automatic hello kittying for mods.

what

>>28

Hmm? Just add it as usual to FILETYPES in the config file? Or did you mean something else?

>>29

BlackMage has taken to replacing certain images with Hello Kitty instead of deleting them. It amuses me so I thought I could add an interface to do it.

> BlackMage has taken to replacing certain images with Hello Kitty instead of deleting them. It amuses me so I thought I could add an interface to do it.

Awesome option.

>>27

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.

>>30
Oops. It's not entirely clear that FILETYPES does more than add icons. Although the lack of anything else should make it obvious...heh.

-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.

>>34

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.

Label which gif files are animated? They usually contain the string "NETSCAPE2.0" near the start, if that helps.

Hmm, would need a new column in the database, and I am trying to avoid that. Unless I'd use some TRICKERY, which isn't too tempting either.

Also, would ruin the "animated" joke.

Ok, fine, it's dead anyway.

how about allowing people to upload bmp images and automatically converting them to png?

This would certainly be possible, but it would teach them nothing. Give a man a fish...

how about non-animated GIF to PNG? also fixes >>36's beef

>>40
You could put a big message with "Bitmaps are for buffoons" before redirecting to the thread after posting, or set it as forced text in the message body, like "User was banned for this post".

USER'S LAME BMP FILE WAS UPGRADED FOR THIS POST

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.

Does the latest version move all the x.html files to another directory? The base directory can get cluttered if you have a high thread limit.

>>44

No. Maybe that should be an option, though.

wakaba.pl, line 1278, 2.1.4:

I got a bareword not allowed error for USE_XHTML. I stuck a qw() around it. Is that horribly insecure?

The updating procedure was: copy random files (everything in the base, and /extras) into the directory, restore config.pl, rebuild caches, and hope nothing breaks. It appears to work.

Did you copy the new config_defaults.pl in there?

Gee, don't I feel stupid. Thanks for the help.