>>116

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

>>152
What does that even mean? Does that mean nobody can come along and claim some sort of authorshop/copyright on Kareha or a slightly modified version of Kareha?

| stays |

Wow, >>243 sure looks like shit in Safari. What the hell? Looks right in Firefox, though.

>>110
Happened to me, too, sometimes it goes black, sometimes it goes white. Screen reappears if you just scroll up a bit but it's still strange.

>>19

I can't reproduce this on Firefox 1.0.4 nor Safari on the Mac, but that ancient Firebird had a similar problem (but even worse).

Anyone else? Try post with a | in your name.

The "Entire thread" link on the thread page is missing a "/" at the end.

>>342
Well, for example, in both forms the text labels are bolded when they shouldn't be, in Futaba and Blue Moon. If you take a look at Blue Moon, the text labels in Create new thread are larger than those in the Reply box.

>>251

Again, the list of tags allowed on that page don't correspond to what would be allowed in Kareha. Of course <img> tags wouldn't be allowed, for instance. This is just for testing the actual cleanup engine.

> What about a(n) (optional) preview page?

I've been considering that, but it's a goddamn pain to implement. It'd be pretty useful, though. Also, it could include the spell checker someone requested way back at the beginning of time.

>>236
I mean, thread titles in <h2> and post headers in <h3>.

>>154 YOUdqn!

>>123
signed

> The error page in mode_message should more closely resemble that of 0ch (complete with "ERROR!" title).

Signed. And the style selector on the error page is pretty useless.

>>174

>Let people figure out things themselves, if they are so keen on changing their keywords.

If you really want to use your own custom trigger strings, you can easily search kareha.pl for instances where "sage" and "fusianasan" are used in that context and either replace them with those custom strings or append them as secondary strings. It's not something that warrants additional config.pl parameters.

About the etyomology of "fusianasan":
http://4-ch.net/nihongo/kareha.pl/1102656968/224-

>>9
That's an option, you pick which one you want.

More information on the all threads page, date of the last post? file size?

A quote button that puts >>n and puts the post prefixed by > in the reply box

Different secret strings for different functions (e.g. one for ID generation and one for secure tripcodes)

>>210

monospace font? like this?

> some other trickery

I smell JavaScript coming in about >>90-120

Well, both >>30 and >>31 didn't change the ¦ into ?U so I am out of ideas what happened...

>>137
I also noticed that you removed the CSS selector in individual thread views. Personally, it seems both the Admin options and Style selector are a bit of a hindrance to the overall layout. Don't get me wrong -- I think the drop-in Style capability is fantastic-- but it just doesn't seem to play nice with the current 2ch page design.

The thing is, don't most or all major browsers these days allow users to change CSS styles from within the application itself? I know Firefox does, at least. Maybe the selector isn't really necessary.

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

Booo!

> who here finds enough use in the auto-expanding comment box to justify the annoyances when you click in or out of it?

I love that feature. Please don't remove it!

> I think the drop-in Style capability is fantastic-- but it just doesn't seem to play nice with the current 2ch page design.

plz 2 be keeping that feature too