So, it's finally release time!

http://wakaba.c3.cx/releases/wakaba_3.0.0.zip
http://wakaba.c3.cx/releases/kareha_3.0.0.zip

I decided to bump the version number up to 3.0.0, partly because of a number of new features, and partly because there's been lots of messing around in the guts of the scripts, which means there are probably some new and interesting bugs. I do not recommend installing these scripts on any busy boards without doing some testing first, or waiting for others to test them for you. Conversely, testing is very welcome. Report those bugs!

Specific information will follow in the next posts.

First off, new features that are available in both scripts (either due to re-use of wakautils.pl or kopipe magic):

• Thanks to coda, there is now support for networked includes. wakautils.pl now has a function named get_http() which does HTTP downloads with caching. It can be used in header.html and friends by putting in a <const get_http("http://domain.com/header.html")>
• More options for displaying IDs. There are now "ip", "host" and "mask" options that replace the ID with either the poster's IP address, host name, or masked IP address. The masked IP is encrypted (and will change according to the thread, day and board options), but similar IPs produce similar strings.
• Bugfixed Javascript code. Cookies work better, and >> quoting should behave more sanely.

New Wakaba features:

• Thanks to dmpk2k, there are now a bunch of new (somewhat experimental) features. Unfortunately, I don't know all that much about how all of them work, and I hope dmpk2k will fill us in with some details. Anyway, there is:

  • Load balancing of images across multiple servers.
  • Proxy detection
  • Captcha overrides
  • SILLY_ANONYMOUS ported to Wakaba!
• Wakaba now rebuilds wakaba.html if it doesn't exist. This should cause less confusion on new installs.
• Admin logins can now use a cookie to stay logged in for easier admin work.
• There is some (somewhat untested) support for Hello Kittying (replacing deleted images with a stock image).

Kareha changes and features:

• Lots of page layout changes and CSS changes, mostly to better match 0ch. After upgrading a board, a shift-reload might be necessary. Also, the Amber style hasn't been updated, and should be deleted, because it's now even uglier than normal.
• The filetypes/ALLOW_UNKNOWN bug has been fixed.
• Kareha always shows >>1 when displaying normal post ranges.
• Most thread links now link to l50.
• Fusianasan has been implemented.
• Capcodes now support inserting HTML code (note that the config.pl format for capcodes has changed).
• There is now both manual and automatic thread closing.
• IDs can be configured to show "Heaven" only on sage.
• Fixed the ugly captcha CSS bug.
• Support for different kinds of markup.

More changes that affect both scripts, because I forgot a bunch in >>2:

• ASCII control codes are now filtered out and don't cause XML errors.
• Thumbnailing now supports GD (very untested, might break, might need gif2png installed), and sips (an image processing utility installed by default on Max OS X 10.4, and maybe older versions).
• Some fixes to make WakabaMark break a bit less.
• Javascript for inserting text works better in Firefox.
• Secure tripcode vulnerability has a better fix, and most of the crypto code has been upgraded to be more robust. As a consequence, secure tripcodes have changed!

Also, Kareha now has an admin script. However, I was sort of tired of workin on this for now, so the design is pretty ugly and half-assed. It does work, though. It still needs some things, like the easy interfacing with a banning script I mentioned earlier (if you want to do this, you can edit the templates to include the approriate links, though). It also needs a better layout and some non-ugly CSS. Squeeks has indicated he might do some work on the latter, but if anyone wants to help out with this, go right ahead.

Well, that is about that. I'm sure I forgot a bunch of stuff, though. I'll post more as I remember it.

Now, report those bugs!

So...who is testing it?

http://img.6channel.org/sexy/wakaba.html
I got it installed here.

Wakaba also can also now archive posts and images once they're bumped off the board, for our dear packrat administrators.

I also (highly) recommend administrators of current boards run cleanup.pl in wakaba's root, since 2.1.4 doesn't always get rid of thumbnails like it should. Make sure to make a backup copy of thumb/ first.

Old data is never deleted, just moved.

Anyway, some explanation of the load balancer. Let's assume the board is shii/* (ie: shii/wakaba.pl, shii/config.pl, etc):

To enable this, do the following:
a) Copy shii/extras/load_balancing/sender.pl into shii/
b) Create shii/redir/
c) in shii/config.pl, set ENABLE_LOAD => 1
Other options: LOAD_LOCAL is a variable that gives a rough estimate how much bandwidth the local boards has per month.
LOAD_HOSTS lists other hosts to send to, their access passwords, and their bandwidth per month. See example below.
d) If you have an old board already set up, you need to convert to the balancer mode. Do this by copy shii/extras/load_balancing/redir-convert.pl into wakaba's root, and run it.
e) Refresh cache from management panel.

Before you do all the above, you'll first want to copy shii/extras/load_balancing/loader.pl to the other hosts that will be helping balance. Make sure they can execute, have permission, and that the PASSWORD in loader.pl has been changed from CHANGEME.

An example:
I have three hosts.

• the main board, which has 100GB per month
• mirror A, which has 30GB per month, a password of "zOMG", and a loader address of www.zomg.com/shii/loader.pl
• mirror B, which has 50GB per month, a password of "mootykins", and a loader adddress of www.4chan.org/shii/loader.pl

LOAD_HOSTS in config.pl is set up as follows: ([host 1, password, bandwidth], [host 2, password, bandwidth], ..., [host n, password, bandwidth]). So, for the above example the line would become:

use constant LOAD_LOCAL => 100;
use constant LOAD_HOSTS => (['http://www.zomg.com/shii/loader.pl', 'zOMG', 30], ['http://www.4chan.org/shii/loader.pl', 'mootykins', 50]);

The proxy detection in wakaba is a lot fancier than in futaba, for example. It has an age/refresh mechanism where it never scans recognized IPs, so a poster will only be scanned once, unless their IP changes or they don't post again before their entry in the proxy code is deleted (default of seven days). The proxy detection is also somewhat voodoo, for two reasons:

• You need an external program (for now)
• You need to know how to configure that program.

Most of the hard work has been done though, so to get a basic anti-proxy system running, do the following:

Download proxycheck from http://www.corpit.ru/mjt/proxycheck.html and compile it. Put it in wakaba's root (or in my case, below root, but you'll need to add ../'s to PROXY_COMMAND)
Change PROXY_COMMAND in config.pl.

The default line in config.pl is a good guideline of what to start with. Don't change much other than the CHANGEME (and the "CHANGEME ESMTP", which should also just be "CHANGEME"). In other words, leave the option switches the same. If you want a ready-made line, here's what I use:

use constant PROXY_COMMAND => '../proxycheck -s -d achaea.com:23 -c chat::"Multi-User License: 100-0000-000" -aaaa';

What this does is attempt to connect through a potential proxy to achaea.com, port 23. Achaea is a MUD, and one of the strings it always returns on its own line is "Multi-User License: 100-0000-000". What proxycheck will be looking for is that line. The reason I chose this is because it never changes. You can use other things too, like an SMTP server, but only if you're certain that the greeting string never changes.

If you get PROXY_COMMAND wrong, or the string it's looking for goes out of date, no blocking will occur at all.

One last comment: I recommend every board set this up if possible, but leave ENABLE_PROXY_CHECK => 0 (in other words, leave it off). It's only meant for use when a board is under active attack, because it also will lock out some legitimate traffic. Some of the board users seem to have a habit of using a proxy, and they won't be able to post while this is enabled, so it won't just block hostiles.

Uh... never mind?

Captcha overrides are a little feature put together that allows certain tripcodes to post without ever entering a captcha. This is handy for mass posters, since they don't like repeatedly entering tripcodes.

To add a tripcode, go to the Bans/Whitelist of the management panel, and add the person's tripcode in the bottom-right form (the one with "Tripcode", "Comment" in it). The tripcode it the person's encoded tripcode, with the leading !.

So, for example, in "dmpk2k!hinhT6kz2E", the tripcode to enter would be "!hinhT6kz2E". For the comment field I usually put the poster's name, since I don't usually remember tripcodes.

Once you click on "No Captcha", and entry should appear in the table belog that specifies the tripcode as "NoCap". For this point on the target person won't need to enter a captcha. Be aware that this does open you to abuse if the person turns hostile, or someone else finds out their tripcode and goes on a spamming spree.

Requesting Admin password and Remember me on this computer in the management panel be moved to the same line in a future update. It doesn't look nice the current way.

One last thing, for those who decide to use wakaba's load-balancer, please be aware that it still needs some bugs hammered out. The main one is that as of this writing I don't think it properly takes the bandwidth of each host into account.

In other words, even if you enter the 100, 30, 50 given in the example above (>>12), it seems that it's allocating redirects evenly between each one, not the 55%, 17%, 28% you'd expect.

If someone uses the load balancer extensively, please let me know so I can grab copies of what's in redir/. It'll help me confirm whether the ratios between board bandwidth is being considered or not.

Also, archiving is disabled by default. It can be enabled in config.pl. It needs the arch/ directory, with src/, thumb/ and res/ subdirectories.

You people are slow! I already found one bug: The RSS is kind of broken. Anything else before I package up a 3.0.1?

They're just stuffed in a directory. It's up to the admin what to do with the files later.

After login in Karehas admin.pl I always get an "Thread specified does not exist." error message if I call admin.pl without anything in PATH_INFO. Things like admin.pl/list or admin.pl/$thread do work.

That's weird, it works fine here... What Perl version?

Perl 5.8.7. It only happens if the total number of existing threads is less then THREADS_DISPLAYED in config.pl.

have you seen the new "newsticker" on 4chan? Worth emulation in an official release y/n?

> Anything else before I package up a 3.0.1?

I have several things I'd like to submit for Wakaba. Hopefully you only intend to keep major version number in sync between Kareha and Wakaba, not minor.

>>26
rules.html can be meant for board- or site-wide announcements.

>>20
Not a bug, but is there a reason you've consciously kept the image details italicized in both Futaba templates?

While we're on that topic, I got rid of a few moldy leftover interface strings in Kareha's mode_image and cleaned up the error strings for coherence and professionalism, on top of removing the <em> brackets in the file details header. Do what you wish with the changes.

http://rapidshare.de/files/7030610/templates.pl.html

>>26

As was pointed out, that's not really the task of the script, that just involves admins keeping rules.html updated in one way or another.

>>27

Neither, really.

>>30

It has been requested in the past. And I do think it makes it a lot easier to see.

plz2fix css
BAD:

body {
        background-color: #6B7B8D;
}

GOOD:

html {
        background-color: #6B7B8D;
}

Fix where? As far as I can recall, most of the CSS should use html, body. Did I miss any?

I looked through all the CSS files, and all of them define styles for both html and and body. I can only conclude that you are COMPLETELY CRAZY.

http://wakaba.c3.cx/releases/kareha_3.0.1.zip

>>20,23,28 fixed. Some of >>31 copied (error messages should be friendly, not professional, though), and some other strings changed a little. admin.pl can now edit spam.txt, too.

Also: Most of the translations are getting a bit out-of-date and are kind of full on English. They need updating, if anyone feels like doing some work.

Kareha 3.0.1, mode_message, perl 5.8.6.
I see the following warnings in my servers error.log:

kareha.pl: Warning: Use of "shift" without parentheses is ambiguous at /home/www/bbs/kareha.pl line 1145, <FILE> line 7.

The script works but the warnings are a bit annoying.

>>38

Find the line, and change shift to (shift). Should fix it.

>>34-35
the problem is that 'background-color' is in body instead of in html.

also, mode_image templates.pl doesn't have any way to choose formatting

>>40

Fixed, except in psed0ch where there's not much to be done about it.

>>41

Didn't really think it was necessary. Wakaba doesn't have it, either.

Kareha 3.0.1. The "permasage" link in admin.pl/$thread should be an "unpermasage" link for permasaged threads like in admin.pl/list.

>>43

The code to do that is there, but there was a typo that broke it. orz

There's at least one typo with regard to the DELETED_THUMBNAIL/DELETED_IMAGE parameters in futaba_style.pl.

Also, would it be possible to release a minor Kareha upgrade in the near future with a few tweaks (I've implemented most of them myself in a custom distribution, but it'd probably be good for the main version too)?

• DELETED_THUMBNAIL/IMAGE parameters
• S_ANOTITLE and S_ANOTEXT parameters
• Removed capcode checks in kareha.pl and templates.pl (now that they're customizable, admins can easily add the <em> tags and append the name/cap string with '(Admin)')
• PAGE_GENERATION checks at least for mode_image's templates.pl(ie, if I set a board to 'single' it won't display the page list at the bottom)
• HOME parameter in mode_image's config.pl (so people stop wondering why the hell the link never works)
• Removed THREADS_LISTED parameter in mode_image's config.pl
• Non-styled (ie, no h1, no center alignment, no extra line break) error template in mode_image, with designated headers above and below -- the markup should have its own div class to be styled in CSS
• Tweaked mode_image CSS (at least for Futaba) that reduces the page header's <hr />'s width to 90% of the page width.
• Is there a way to replace the <br clear> tags with something more sane in CSS? AFAIK the clear parameter has been deprecated in XHTML.

> There's at least one typo with regard to the DELETED_THUMBNAIL/DELETED_IMAGE parameters in futaba_style.pl.

Well, what is the typo?

> DELETED_THUMBNAIL/IMAGE parameters

Not possible to implement without regexp trickery that is not guaranteed to work on different templates.

> S_ANOTITLE and S_ANOTEXT parameters

Meh, I never liked those much.

> Removed capcode checks in kareha.pl and templates.pl (now that they're customizable, admins can easily add the <em> tags and append the name/cap string with '(Admin)')

For mode_image? I think I forgot to update that, will fix.

> PAGE_GENERATION checks at least for mode_image's templates.pl(ie, if I set a board to 'single' it won't display the page list at the bottom)

PAGE_GENERATION isn't really an option you're supposed to change for a given template. Why would you want to run mode_image in single-page mode? That makes no sense, as there's no way to access the older threads.

> Non-styled (ie, no h1, no center alignment, no extra line break) error template in mode_image, with designated headers above and below -- the markup should have its own div class to be styled in CSS

You can just style h1, can't you? The entire page should have its own class so you can do that (if it doesn't, that's a bug), but I haven't bothered to style it. Thing is, though, I'm not touching the CSS for the Futaba-style templates, because I prefer it to be compatible. I could make the HTML more like the original Futaba/Futallaby error page, but it's not really an issue that has very high priority.

> Is there a way to replace the <br clear> tags with something more sane in CSS? AFAIK the clear parameter has been deprecated in XHTML.

XHTML 1.0 is just HTML 4.0 in XML. Maybe it's deprecated in XHTML 2.0, but this isn't that.

> Well, what is the typo?

Unfortunately, this computer doesn't have anything better than Notepad, so I can't give you the exact line numbers. Just search for "DELETE_THUMBNAIL".

> For mode_image? I think I forgot to update that, will fix.

In kareha.pl too though, since admin functions are now independent of whether you input a capped trip or not.

> You can just style h1, can't you?

I don't know if this is sarcasm or not, but I assumed it's possible in CSS.

> The entire page should have its own class so you can do that (if it doesn't, that's a bug), but I haven't bothered to style it.

Indeed there is no body class for mode_image's error template.

> Thing is, though, I'm not touching the CSS for the Futaba-style templates, because I prefer it to be compatible. I could make the HTML more like the original Futaba/Futallaby error page, but it's not really an issue that has very high priority.

Futaba's error page doesn't use header tags in HTML, but it does center the text (then again, it also centers "postarea" and right-aligns "userdelete")

About <br clear>: I'm really just echoing the W3C spec for HTML 4.01 (http://www.w3.org/TR/REC-html40/present/graphics.html#h-15.1.3.2), which states it's deprecated.

> Using style sheets, you could specify that all line breaks should behave this way for objects (images, tables, etc.) floating against the left margin. With CSS, you could achieve this as follows:

> <STYLE type="text/css">
> BR { clear: left }
> </STYLE>

> In kareha.pl too though, since admin functions are now independent of whether you input a capped trip or not.

No. They never had anything to do with admin functions before, either. What they DO let you do is post on a board where posting is disabled.

> Indeed there is no body class for mode_image's error template.

I'll have to fix that, then.

> About <br clear>: I'm really just echoing the W3C spec for HTML 4.01

Ah, it's not listed as deprecated when you just look up the definition for the <br> tag. I don't think I'll be changing that, though, because the whole Futaba layout is heavily outdated in the first place. It's also nearly impossible to implement in proper modern XHTML/CSS, at least in such a way as to make it work in IE, too. I tried, but it was much more pain that it was worth.

>>48

> the whole Futaba layout is heavily outdated in the first place

You mean the actual Futaba software, or Kareha's Futaba mode template?

> It's also nearly impossible to implement in proper modern XHTML/CSS, at least in such a way as to make it work in IE, too. I tried, but it was much more pain that it was worth.

IE needs to die.

> You mean the actual Futaba software, or Kareha's Futaba mode template?

I mean the HTML code it uses. futaba_style.pl is an attempt to make it a bit more XHTML-like, and is at least in part based on thatdog's work of Futallaby, but there's only so much you can do with it.

> IE needs to die.

That it does, but it hasn't yet.

Well, here's the latest batch of bugfixes:

http://wakaba.c3.cx/releases/wakaba_3.0.1.zip
http://wakaba.c3.cx/releases/kareha_3.0.2.zip

Nothing terribly important, just getting these things uploaded so they'll be available.

>>50
I was under the impression that mode_image's template was 99% XHTML.

Sure, but you can write circa-1993 style HTML in XHTML too, just as long as you keep it well-formed.

>IE needs to be fixed or upgraded so it supports webstandards.

Fixed.

http://wakaba.c3.cx/releases/kareha_3.0.3.zip

Should implement the fixes in >>54 (although I was kind of sloppy with that, I might have missed some unused string), some fixes for the Japanese template, and there's now an option to turn off the ability of admins to edit include templates (since templates can execute code, that's a bit risky). It's off by default, so if you want editing, remember to turn it on.

I have to say that kareha has a much more professional feel to it now than it had before!

I installed a new copy of Kareha 3.0.0 (now upgraded to 3.0.2) and the tripcodes are acting funny. Each time I enter my name as "foo#bar" (with foo and bar being constants), the tripcode resulting from bar is different. I've gotten three tripcodes so far out of three posts, entering the same thing in the Name field each time. (Also, none of the three matches my tripcode on another, Kareha 2.0.4 forum.) Why might this happen?

That's strange... could you link to the board in question, or post the results here?

>>60
bar is equal to "super" and the results are hnaqdgEjIm, VT4sg21iYS, 8JCn9fwUsm, umVH01Gevu. The expected result (from Kareha 2.0.4) was oCplYpbPzw.

It does work as expected here. That's very strange. The only thing I can think of is that the crypt() function would for some reason be returning weird values, but that shouldn't just affect the one version. The code that generates the 2ch tripcodes hasn't changed at all between those versions, either. Do other tripcodes work as expected? Short ones? Long ones? Try posting in the test thread to compare.

Actually, this experiment is unscientific because one of the variables has changed. The 2.0.4 install is on a Linux server, while the 3.0.x is on a FreeBSD server. I will try installing 2.0.4 on the latter and see if it, too, produces ridiculous results. (Probably it will.)

If it doesn't work, then I suspect BSD has some weird-ass crypt() implementation that doesn't do what it's supposed to. I'm really not entirely sure what can be done about that, though.

Here is the FreeBSD crypt(3) manpage:

http://www.freebsd.org/cgi/man.cgi?query=crypt&sektion=3

It looks like the problem might be that the format defaults to something other than DES (probably Blowfish). Can you do crypt_set_format("des") first? (I'm not familiar with how C functions are called from Perl.) Of course, you would only do this if (`uname` eq 'FreeBSD').

According to the manpages from NetBSD and OpenBSD, both of their crypt(3) implementations can be used in the traditional way, so no workarounds should be necessary for those.

> I'm not familiar with how C functions are called from Perl.

That's the problem, you can't, without an XS module in between. Searching for this on Google, I turn up lots of Japanese pages. I guess various tripcode-using programs would all have this problem. The only way out I see off hand is to use this suggestion from the man page:

> The global default format can be set using the /etc/auth.conf file using the crypt_default property.

Of course, if you're not allowed to do that, then you have a problem.

If you ask me, FreeBSD should not go around changing how well-established system calls work on a whim, but what the hell do I know.

Does anybody else see a little line above the style picker on the Society board?

That's a pretty useless question unless you specify what style you use and what you mean by a "little line".

Stardard futuba, a 2-3 pixel this <> background-color line where the board into text and the style selector are.

In firefox, too.

A picture alright?

Ordered HTML lists in WakabaMark ("1. foobar..") seem to cause infinite loops in the wakautils.pl version included in Kareha 3.0.3.

http://wakaba.c3.cx/releases/wakaba_3.0.2.zip
http://wakaba.c3.cx/releases/kareha_3.0.4.zip

>>69 fixed (although I'm tempted to call it a Firefox bug, because it was pretty hard to reproduce, and it took a sort of ugly hack to work around it), and also >>70 (which I thought I fixed once already but apparently it didn't take).

Now that ordered lists work:

1. Go to http://wakaba.c3.cx/sup/kareha.pl/1106698024/1
2. Click on "Replies"
3. Undefined subroutine &main::get_reply_text called at /home/waha/public_html/sup/kareha.pl line 871.

Dead code calling a nonexistent sub, should probably be removed completely in the next release.

http://wakaba.c3.cx/releases/kareha_3.0.5.zip

Yet another bugfix! There were a couple of bugs related to deleting files that were fixed. You only need to update if you're using images.

Oh, and can you include the fix for >>38 in the next release? I dont want to edit kareha.pl after every update.

I thought I fixed that?

>>75
Sorry, my fault, I looked in the wrong file.

I get a Mozilla yellow screen of death when using admin.pl:

XML Parsing Error: mismatched tag. Expected: </body>. Location: http://mysite/forum/admin.pl Line Number 8, Column 50:<br /></div></div></div> </div></div> </div> </div> <div id="navi"> Pages: 0 <a href="/forum/admin.pl/p1">1</a> <a href="/forum/admin.pl/p2">2</a> <a href="/forum/admin.pl/p3">3</a> <a href="/forum/admin.pl/p4">4</a> <a href="/forum/admin.pl/list">Thread list</a> </div> </body></html> -------------------------------------------------^

If you get around to it, the CSS files in Kareha's mode_image have a lot of old unused elements still defined -- and THREADS_LISTED still exists in config.pl, while HOME is nowhere to be found. Also:

• What CSS tag can be used to modify the "logo" element's <hr />'s width to 90% of the page?
• Error template div/body class in mode_image still missing -- on a side note, what font-size and/or font-weight would be appropriate to match h1 text styling in CSS?
• Back to capcode checking: why shouldn't admins be able to make admin posts anonymously? I think that as long as they have the password, they should be able to bypass all thread/board limitations without the need to use any sort of unique identification. This might require its own sub function that basically removes all such limitations (text/file posts, permasaged/closed threads, choice of whether to use ID, etc).

> the CSS files in Kareha's mode_image have a lot of old unused elements still define

Once again, the CSS for mode_image is the same as both Wakaba and Futallaby uses. It's not supposed to be perfectly tailored to Kareha, and I won't be doing any tweaking for that.

> and THREADS_LISTED still exists in config.pl,

All options exist in config.pl, even those that don't apply to the current style.

> Error template div/body class in mode_image still missing -- on a side note, what font-size and/or font-weight would be appropriate to match h1 text styling in CSS?

I decided that since neither Wakaba nor Futallaby have it, I'm not going to add it, for the same reason as above.

> This might require its own sub function that basically removes all such limitations (text/file posts, permasaged/closed threads, choice of whether to use ID, etc).

Because it's a lot of work for something that will hardly ever be used, and really isn't necessary for anything.

Also, yet another release:

http://wakaba.c3.cx/releases/kareha_3.0.6.zip

Fixes >>77 (which was tricky to track down, because it only happens when posts posted in AA mode get abbreviated), and some other more obscure and harmless bugs I found.

>>79

What's the point of supporting Futallaby CSS when the only stock styles available are "Futaba" and "Burichan," both of which are also included in the Wakaba and Kareha packages? If it were an issue of maintaining compatibility with Futaba (the software) I would understand, because it's freely available and used across countless Japanese sites, but there is really no reason to bind ourselves to 4chan's crappy exclusive software.

(BTW, don't take any of this personally, despite the strong tones :))

It's just easier to work against a set standard than constantly changing things on a whim, like I do with mode_message. It's a major pain in the ass, keeping all styles updated.

Besides, lots of people have now created more styles to this standard, even if they're using Wakaba and not Futallaby.

>>83

>It's a major pain in the ass, keeping all styles updated.

Why not just work on the stock styles (Futaba and Pseud0ch) and leave the others up to the community to update?

Because I made all of them except Blue Moon (and Pseud0ch which was a cooperation)?

>>85
That doesn't mean you're the only person capable of maintaining them. I'm sure there's enough of a following that if people really wanted to keep certain styles, they wouldn't mind updating them every once in a while (especially for such a large version jump like 2.0.0 to 3.0.0).

Can you make the path to log.txt configurable? This would make it easy to place log.txt outside of the servers document root (e.g. somewhere in your home directory). While it is possible to configure the server to forbid access to it not many people seem to do this: http://wakaba.c3.cx/sup/log.txt and even if the file is encrypted it is a threat to posters anonymity.

I thought I had put that in as an option, but maybe I forgot. I should also add some more crypto on the password field, so that one doesn't matter either.

http://wakaba.c3.cx/releases/kareha_3.0.7.zip

Added config options for LOG_FILE and INCLUDE_DIR, and also a KEEP_MAINPAGE_NEWLINES option to disable the stripping out of newlines when generating the main page. This keeps Google ads working. Also added more encryption to log.txt, so there's really nothing in there to identify anyone in any way.

Configurable CSS directory?

>>90

$ grep CSS mode_*/config.pl 
mode_image/config.pl:#use constant DEFAULT_STYLE => 'Futaba';           # Default CSS style title
mode_image/config.pl:#use constant CSS_DIR => 'css/';                           # CSS file directory
mode_message/config.pl:#use constant DEFAULT_STYLE => 'Headline';               # Default CSS style title
mode_message/config.pl:#use constant CSS_DIR => 'css/';                         # CSS file directory

Derp.

There's a bug with the post abbreviation code, which you can see at http://pyc.h8r.net

I've noticed that one, actually, but for the life of me I can't figure out what causes it.

http://wakaba.c3.cx/releases/wakaba_3.0.3.zip
http://wakaba.c3.cx/releases/kareha_3.0.8.zip

Well, I sat down and tried again, and I did finally figure >>93 out. It was a regexp bug. I also fixed another regexp bug that caused both Wakaba and Kareha to change "." in filenames to "%2e", which technically isn't wrong, but it's a pretty silly thing to do.

Yeah, I had noticed the %2e thing too. Thanks for the fixes.

I've been extensively tweaking and slimming down the mode_image template for Kareha over the weekend, and making the necessary adjustments to each CSS file (while converting some deprecated variable parameters). Some of it dealt with removing redundant div elements such as postername/commentpostername and filetitle/replytitle, and for others it was changing certain structure elements to more closely resemble the Futaba board layout.

Some shortcomings:

• as you will see in futaba.css, I tried to style the logo element header with no success, though I wish I could get it working.
• the page list table at the bottom of each main page is having some alignment issues, particularly the widget buttons.
• I kept playing around with styling rules.html so that it would left-align with the rest of the postarea table, but instead it just centers.
• reply table cells are larger than they should be around the blockquote text (most noticeably below).

Here's the template + CSS files: http://rapidshare.de/files/7635013/templatecss.zip.html

You can test it out on http://dongs.hadoken.net (WARNING: NWS), and use http://dongs.hadoken.net/kareha.pl/1131952971/ as the unofficial test thread. As you can see, older threads have been left in the dust due to these incompatible changes. The other possible issue is that I voluntarily removed the extra CSS elements that only Wakaba uses, but these can be easily readded if necessary. I hope you will find the changes useful.

Slight template update (changed body margin to 10px and removed the padding altogether).

http://rapidshare.de/files/7638487/templates.pl.html

I don't understand what you mean by "older threads have been left in the dust". Aren't they just created from the database when you rebuild caches?

Second update: created a CSS element each for the inner and outer page list table cells. For now, the border styles and widths are defined in templates.pl, but maybe they should be offloaded to individual CSS files. If not, they can just as easily be overriden.

http://rapidshare.de/files/7645370/templates.pl.html