Removed it when redesigning the page head, haven't figured out quite what to do about it yet. It needs to be changed, but to what, I'm not yet sure.

The "Entire thread" link in the top navigation bar of the thread page is still broken.

>> config.pl parameter to permasage after a certain thread filesize/total number of characters has been reached

> Isn't this essentially the same as saying "Please don't talk so much?"

I am not >>208 but the first who suggested this here (long ago). I think it may be vital for future, actually popular boards to limit the filesize of a thread so that the board won't get hammered by repeated loads of whole threads without having to limit the size of posts themselves something fierce.

>>305

Shift-reload already! Also, most people are familiar with "More options..." links and know when and when not to click them. I might see about styling it, though.

Kareha can't use different layouts for posts on different pages, except by CSS trickery. I could add the second colon, though.

Also, I've implemented optional thread closing now, but there's no extra post. That would just be a total mess to implement, and would make re-opening threads annoying, if such a feature was requested. It replaces the posting form with a notice that the thread has been closed, instead.

PS: I always wanted to say this: The # anchors on the TiddlyWiki automatically scroll me (FF, 1.0.7) just below the actual text box of the entry. Is that a bug, a feature or... ?

Maybe. I just picked something at random.

It's also more markup when even the existing one isn't working as well as it should.

>>59-60

Details, please. Everything works for me.

All right, code updated again. This time, some experimenting! I've implemented a tentative system for changing markup types. This needs a bunch of testing, of course, so here's the test thread link once again: http://wakaba.c3.cx/sup/kareha.pl/1099697376/

Thoughts and comments are welcome. I'm still trying to figure out how exactly to do this.

There's a bunch of other changes and fixes too, so mention if anything breaks, as usual. Also, shift-reload!

Well, a lot of machines run on x86 these days, so that covers a lot of it. And you could pre-compile for a couple of other architectures, and have it pretty much covered. Linux and unixes in general make it ridiculously hard to distribute binaries, as opposed to Windows or Mac OS, but it's still possible with a bit of trickery. Avoiding dynamic libraries helps a lot.

Some semantical nitpicking: "replies" should probably be changed to "posts", since >>1 is not really a reply, which makes >>100 the 99th reply to a thread, thus contradicting the "First 100 replies" thing. Same goes for "Next 100 replies" and "Last 50 replies".

http://wakaba.c3.cx/sup/kareha.pl/1114201493/l50

Or use some sort of filter to replace them characters with underscores on upload.
This offcourse for files that keep their original filename.

>>196
Actually, a solution to >> links with static pages is to simply make them reference a certain point on a certain page number for that thread (ie, http://wakaba.c3.cx/sup/1129153864/index2.html#197).

All right, new version installed. This one has a bunch of layout changes, and some big changes in the CSS, so you'll need to make sure the CSS is loaded by shift-reloading. Also, fixing all the CSS files was a huge pain in the ass. Have a look around to see if there are any obvious mistakes, but be gentle, because this has given me a headache.

Also, I couldn't be arsed to fix Amber, since it was just a joke in the first place.

>>16

Yes, it's throwing Javascript errors for me if I use that character. Gonna look into that some more.

How about listing what dmpk2k or you have done already?

1. Split threads and posts into separate tables. You're repeating the lasthit and parent column over and over.

WAHa, WAHa, it's a bug!

Pressed back after creating an error message in karaha (trying to reply to this thread, forgetting to type something in here), refresh does nothing!

In mode_image: shouldn't the board title be in <h1>, and the post headers in <h2>?

Thanks. I did it the hard way and put in the proper transformations everywhere so filenames can be kept intact, though.

>>58
Fuck you for giving me <blink>

>>108
fusianasan is a voluntary function to show identity without having to memorize a tripcode. Works on all boards. Reveals your IP, of course...

Another feature I'd like is keyboard shortcuts like Wikipedia. Although you'd have to avoid stuff like Alt-D.

>>170
But my good man, sage means down.

> Also, how is Kahera unrivaled when there are still large sites that are not running it? Shiichan is still on world4ch, Thorn on parts of wakachan for example.

These are temporary problems because the webmasters of both sites are too stubborn to upgrade.

PS. What's "Raw HTML"?

>>249 Then the default should be no markup.

...and admin posts that override all board/thread restrictions (ie, bumping a permasaged thread and possibly even posting in closed threads).

>>116

Apparently it's not Japanese, because it's supposed to be pronounced as an English word. I have no clue, though.