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.

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

>>99
Not in Kareha's case. Once threads/replies are created, the only way to keep them up to date is to modify the class names by hand in each html file.

http://pyc.h8r.net still exhibits the >>93 bug, even after updating wakautils and rebuilding the caches. Does the fix affect only new posts?

>>102

What in the... The fix has disappeared from all my files, too!

All right, I added it back one more time, and uploaded new files. Didn't bother to bump the version number, just re-download. The only file that's affected is wakautils.pl

>>103
Snacks is covertly undermining your efforts.

Also, new bug found: http://wakaba.c3.cx/soc/kareha.pl/1098492851
It happens when you put more than 3 whitespaces in front of a line of text.

Not a bug, it triggers code mode. Four space or one tab will make everything <pre> formatted. It's copied from Markdown, but it's a bit unfortunate since it's sort of easy to trigger by mistake. Haven't come up with a better solution though. Using only tabs would be hard to trigger accidentially, but most web browsers make it impossible to input tabs by anything except copy-paste.

http://validator.w3.org/check?uri=http%3A%2F%2Fwakaba.c3.cx%2Fsup&charset=%28detect+automatically%29&doctype=Inline

is this a bug:

http://4-ch.net/iaa/kareha.pl/1132249274/

>>108

Eh... Let's say it isn't.

This is the ■ ▲ ▼ for the 6th thread on the /dis/ board, and it's located at the very top of the page. css bug?

It's worth noting Pseud0ch is still borked in Opera. Namely, the [del] links. I'm not certain whether it's the -1.3em or the relative positioning, but deletebutton should be replaced with one of the ones in the other CSS.

BTW, Amber seems to work fine with 3.0, at least for normal posting modes.

>>111

That's not 3.0.

>>112

No, it doesn't. It's missing a ton of frames.

See here: http://forum.akatsukimanga.com/index.html

It's missing a ton of frames? So what? The differences are trivial. It also works better than Pseud0ch (cough).

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

Latest batch of bugfixes:

• Should fixes the validation errors in >>106.
• Fixes a warning in Wakaba that was spamming logs.
• Adds the missing link for deleting threads in admin.pl.
• admin.pl now never uses XHTML mode.
• Fixes a big where spaces in filenames got encoded as + instead of %20
• Now strips out numerical entities bigger than 1114111, which apparently causes Mozialla YSODs.
• Pseud0ch (and some other styles) fixed to work better in IE. I had no idea it wasn't working, you people need to tell me this stuff.

>>111 a missing position: relative; for sagethread in pseud0ch.css. This bug ist still present in kareha 3.0.9.

>>116

Thanks! Fixed and re-uploaded 3.0.9 without bumping the version number.

Some of the "Return" links match the referring url (eg: the error page when a thread doesn't exist) - but when there isn't a referer, those links go nowhere.

Did you make any substantial changes to how build_cache() and build_cache_page() work? The changes I did for my board were done with a nebulous understanding of the inner workings, so...

Umm... In Wakaba, no, in Kareha, yes. As I recall.

Pretty much. Not planning any big work in the near future.

>>122
So we will not have a working post preview in the near future?

>>123
Post preview shouldn't be implemented in the core functionality. It would work best as a browser extension.

>>123

It's not a very big thing, actually, if I implement it with XMLHttpRequest as mentioned elsewhere.

>>125
Then please do it so. :)

Kareha (in Futaba mode, at least) seems to have a bug where clicking a post number on a main page (to reference the post in a reply) produces a something like http://dongs.hadoken.net/kareha.pl/1134468901/#i%3E%3E1 in the URL bar. The link actually works for inserting post references -- that's why I'm not sure if it's a bug or not.

What happened to the dumplog.pl file came with kareha 2.x? How do I decode the IP address of a poster in kareha 3.x?

Aah, I didn't leave in any automatic way to do it, but you can edit admin.pl and change <var $masked_ip> to <var $ip> to have it show the real IPs instead of the masked ones.

age for >>127

>>127 isn't a bug.

http://dongs.hadoken.net/kareha.pl/1134468901/#ixbox%20is%20hueg
heh

i've found a bug in kareha... if i set CAPPED_TRIPS and rebuild caches, all posts on the board disappear from index.html and the thread views, but are still in the files in res/. if i comment out the line for CAPPED_TRIPS, the posts reappear when i rebuild caches.

What did you set it to?

>>134

use constant CAPPED_TRIPS => ('!hoTarufiRE!!yUegcdbn'=>'<span title="admin">!hoTarufiRE</span>');

That's very weird... I can't think of any way that could happen in the first place. I'm even using CAPPED_TRIPS right now on this board and it works fine.

Is there a function yet that limits the number of times you can post / start threads in a given time?

That can be controlled to some extent with the ancient RENZOKU options that were inherited from Futaba. For Kareha, no such options exist.

Maybe there should be. Just to be able to prevent people from scriptspamming.

Also: Is it possible to define a keyword that one could use as name or link and that would sage a thread but reveal the ID code (for boards that have it usually turned off or turned off when saged)?

>>140
yes, if you don't mind writing a little bit of perl.
i would do it for you, but i'm too lazy.
maybe WAHa will do it for you, but he's almost as lazy as me, so i wouldn't count on it.

http://wakaba.c3.cx/soc/kareha.pl/1100499906/q81 gives

Software error:

Undefined subroutine &main::get_reply_text called at /home/waha/public_html/soc/kareha.pl line 875.

For help, please send mail to the webmaster ([email protected]), giving this error message and the time and date of the error.

>>142
>>72

So, will Kareha maybe get its needed banning script soon maybe? Please?

Don't you think that Kareha has awfully bloated and complicated code for what it does? Come on, you can write it with maybe two hundred lines, and you don't have to include the sources of a http server... :)

The idea is very cool, but I'd be afraid to run this code on my server.

> you can write it with maybe two hundred lines,

then why don't you?

>>144
Use Apache/IIS/whatever. That kind of functionality is really not needed in Kareha.

>>145
What kind of bloat and complication are you referring to?

Actually, I might end up adding some banning functionality, just so I can put in traps to automatically ban spammers. But we'll see.

And >>145, are you sure you know "what it does"?

I think >>145 is looking for something more like http://www.graffitiwall.net/

>>146
I'm going to ;)
Got something like >>149 so far...

>>147
You know, including the sources of perl libraries you use just to make some changes in them... Copy-paste programming...

I know, I know, it's Perl, it must be ugly ;)

>>148
I thought so at the beginning, but the more I read the sources the less sure I am ;)

>>149
Much simplier, indeed, but lacks some of the less-frequently used functionalities of this board :).

Sorry for the harsh words, but I really think it could benefit greatly from some code cleanup.

> You know, including the sources of perl libraries you use just to make some changes in them...

Pretty much the only external library that is included is MIME::Base64. This is because it's not in all default installs, and most people can't install external libraries. A lot of other code is written from scratch, but duplicates functionality that exist in third-party modules, but since lots of people can't install those, I can't use them if I want people to be able to use the script.

>>151
If you want to be free of dependencies, why don't you make it into an operating system?

>>152

I always hate programs that require root access to install. It's a huge damper on popularity.

Ever written any software for public consumption, >>152? --;

>>152

To give a straigh answer to a rhethorical question: Because if people can't install modules because they're on a shared host, they can't install a new operating system either.

I'm not avoiding dependencies for the sake of it, I'm doing what is needed in order that the largest number of people be able to use the software.

Well, besides switching to PHP. There are limits.

I don't think using PHP would gain you much. Very few hosts that offer PHP don't offer the other two P's.

The main thing it would gain is that idiots who limit Perl to running in /cgi-bin/ usually don't apply the same restriction to PHP (making the restriction pretty useless in the first place, needless to say).

What's wrong with putting all the scripts in cgi-bin/ and your custom perl modules in some directory in your home?

It just works, unless you try to use some scripts with hardcoded paths in them.

It's not rocket science.

Most Perl modules use compiled code. Even for those modules that are pure Perl, most people don't know how to do this anyway. It is more work when installing, and people are more likely to not bother.

As it is now, you upload a handful of files, chmod, and it works pretty much just like that. The fact that your program will be more popular the less trouble it makes for your users shouldn't be this difficult to grasp.

You mean there are hosts that have all those fancy image processing libraries you use, but lack base64 modules? Come on...

Ban-script.

>>160
Wakaba can work without any of those libraries. It's not a good idea, but it's possible.

> As it is now, you upload a handful of files, chmod, and it works pretty much just like that.

I think it's quite telling that there are many people who have difficulty doing only this. If anything, the installation should be made significantly more easy.

So if they have problems with editing config.pl and using chmod, does anyone think they'll be able to do it if they need to install additional perl modules too?

The point is to have a running board. Making users jump hoops isn't.

>>161

Post preview.

I see, so ugly code and sloppy programming is for dummies...
Sounds fair. Sorry for my bitching, didn't think about the "marketing" part of programming.

Forsaking code reuse through external dependencies might not appeal to your sense of aesthetics, but I will take offense at "ugly" or "sloppy". If you want to make claims like that, you'd better come up with a better reason than not using external dependencies.

Well, wakaba (at least) could be cleaner. It's a prettier than the alternatives, but it has certainly grown a few hairs over time.

Yet I think worrying about this is silly. There's one main developer. This individual has a limited amount of time. What would be a better idea in spending it: refactoring code that isn't broken, or fixing code that is? What about adding requested features?

From a user's point of view, the former gives no return. Remember, successful software is "good enough". The perfectionists never go anywhere (except in circles), while the imperfect software is actually being useful to the market.

This is reality.

Well, right, for Wakaba, what I'd really like to do is cut certain parts up in modules, but there are only so many hours in the day. The moderation interface in particular could really use some sort of plugin system, so one could implement various kinds of other moderation options and features.

Anyone feel like doing that, go ahead.

>>166
Sorry, didn't mean to offend you, just got a little carried away.

I'll just shut up and go now.

Btw. Somehow didn't say it before, but it's really the best kind of "forum" I ever tried, and the idea that the code doesn't look as beautiful as it could comes from the assumption that it's really top quality.

It happens to the best of us. Donmai, donmai.

My host has Perl v5.6.1 and I'm having trouble installing kareha 3.0.9. I followed the instructions in the documentation but I get a software error when try to run kareha.pl

It said

Invalid [] range "}-\x" before HERE mark in regex m/([\x{100}-\x << HERE {ffff}])/
Compilation failed in require at templates.pl line 3.
BEGIN failed--compilation aborted at templates.pl line 3.
Compilation failed in require at /kunden/homepages/5/d92823313/htdocs/bbs2/kareha.pl line 14.
BEGIN failed--compilation aborted at /kunden/homepages/5/d92823313/htdocs/bbs2/kareha.pl line 14.

I also tried to install an earlier version (2.0.4) in another directory and that works just fine. Anyone know how to get 3.0.9 to work correctly? Any help would be greatly appreciated.

Oh, I seem to have accidentially gotten a 5.8-only feature in there without any checking for earlier versions. I'm pretty sure that line is not important, so you can just open up wakautils.pl, find the line, and comment it out. I'll have to fix that.