>>16

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

Hey, I just noticed this: where did the admin link go? Or are you working on a separate interface already? :D

>>123

Noted. I've been struggling with that same problem for naming things internally in the code, and obviously it distracted me from noticing the same problem in the GUI.

>>231 What would it do?

You could add entire thread links to either the "num" or "posts" column in subback.

>>116
Good question! I tried to find out myself but just found some interesting but rather unhelpful links:
http://d.hatena.ne.jp/keyword/fusianasan
http://info.2ch.net/guide/faq.html#G5
http://ansitu.xrea.jp/guidance/?FAQ1

Hey, I just noticed this: where did the admin link go? Or are you working on a separate interface already? :D

From here on, this thread is about Kareha again:
↓

>>183

No, that's just plain wrong. It is very much the job of the programmer to decide on such issues, and make sure they work consistently across boards.

Oh, and please bring back MAX_LINES.

>>129

That form just looks wrong with no title or clear separator, though. I might put in a title that is not the exact same as the button, though. Any suggestions?

The board title is inserted by template.pl, and rules.html is included after it.

rel=nofollow for internal links as discussed in http://wakaba.c3.cx/sup/kareha.pl/1127092367/

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

http://wakaba.c3.cx/test/sanitize.pl?html=%3Ccode%3E+%E3%8B%8B%E3%8F%A1%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A+%E3%82%94%E3%80%B2%E3%80%B0+%E3%82%94%E3%80%B2%E3%80%B2%E3%80%B0%E3%80%B0+%E3%82%94%E3%80%B2%E3%80%B0+%E3%82%94%E3%80%B2%E3%80%B0+%E3%82%94%E3%80%B2%E3%80%B0%E3%82%94+%E3%80%B2%E3%80%B0%E3%82%94+%E3%80%B2%E3%80%B0%E3%82%94%E3%80%B2%E3%80%B2%E3%80%B0%E3%82%94%E3%82%94%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E3%80%B3%E3%80%B5%E3%83%B7%E3%83%B7%E3%83%B7%E3%83%B7%E3%80%B0%E3%80%B0%E3%80%B0%E3%80%B3%E3%80%B5%E3%83%B7%E3%83%B7%E3%83%B7%E3%83%B7%E3%80%B0%E3%80%B0%E3%80%B0%E3%80%B3%E3%80%B5%E3%83%B7%E3%83%B7%E3%83%B7%E3%83%B7%E3%80%B0%E3%80%B0%E3%80%B0%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%28%E2%99%9B%E0%B8%BA%D0%94%29%28*%E3%82%9C%E2%88%80%E3%82%9C%29%EF%BD%9E%E2%99%A1%E2%84%B3%E0%B8%BA%E2%84%B4%E0%B8%BA%E2%84%AF%E0%B8%BA%E2%9D%A4%E2%84%92%E0%B8%BA%E2%84%B4%E0%B8%BA%CE%BD%E2%84%AF%E0%B8%BA..._%E3%80%86%28%E3%82%9C%E2%96%BD%E3%82%9C*%29%E3%8C%B0%E3%8C%B0+%E3%8D%89%E3%8D%8D%E3%8C%A7%E3%8C%94%E3%8C%B6%E3%8D%8A%E3%8C%A3%E3%8C%A6%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E3%8C%80%E3%8C%81%E3%8C%82%E3%8C%83%E3%8C%84%E3%8C%85%E3%8C%86%E3%8C%87%E3%8C%88%E3%8C%89%E3%8C%8A%E3%8C%8B%E3%8C%8C%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA+%E2%98%A0%E0%B8%BA%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E2%98%BC%E2%99%AD%E2%99%AC%E2%99%AB%E2%99%A8%E2%99%A9%E2%99%A7%E2%99%A6%E2%99%A5%E2%99%A4%E2%99%A3%E2%99%A2%E2%99%A0%E2%99%A1%E2%99%90%E0%B8%BA%E2%99%91%E0%B8%BA%E2%99%92%E0%B8%BA%E2%99%93%E0%B8%BA+%E2%99%94%E0%B8%BA%E2%99%95%E0%B8%BA+%E2%99%96%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E0%B8%BA%E2%99%97%E0%B8%BA%E2%99%98%E0%B8%BA%E2%99%99%E0%B8%BA%E2%99%9A%E0%B8%BA%E2%99%9B%E0%B8%BA%E2%99%9C%E0%B8%BA%E2%99%9D%28%EF%BD%A5%E2%88%80%EF%BD%A5%29%2F%E3%83%BE%7E%7E%E2%95%8B%E2%94%93%21%E3%8B%A6%E3%8B%B8%E3%8B%AD%C2%B0%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%7C%E5%A3%81%7C%E3%80%8D%E3%82%9C%CF%81%E3%82%9C%29%E3%80%8D%E3%80%80%E3%83%8E+%E3%83%BD%60%60%EF%BD%9E+%E5%8A%9B%E3%8B%A6%E3%8B%B8%E3%8B%AD%C2%B0%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E2%80%89%E3%80%80+%E3%80%80+%EF%BC%8F%E2%80%89%E2%8C%92%E3%83%BD+%E2%80%89%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E3%80%80%E2%80%89%E3%80%80%2F%E3%80%80%C2%B4_%E3%82%9D%60%EF%BC%89+I+am+sorry%E3%80%81%E2%80%89the+%CE%B2%E2%80%89%CE%B1%E2%80%89%CE%BA%E2%80%89%CE%B1%E2%80%89kopipe+couldn%27t+be+carried+out%E3%83%BB%E3%83%BB%E3%83%BB%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E3%80%80%E3%80%80%7C%E3%80%80%E2%80%89+%E3%80%80%E3%80%80%2F%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E2%80%89%E3%80%80%E3%80%80%7C+%2F%7C%E2%80%89%E3%80%80%7C%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E3%80%80+%2F%2F%E3%80%80%7C+%E2%80%89%7C%3C%2Fcode%3E%3Cbr+%2F%3E%0D%0A%E3%80%80%EF%BC%B5%E2%80%89%E3%80%80+.%EF%BC%B5+%E2%80%89%3C%2Fcode%3E%3Cbr+%2F%3E

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Partition for renaming "WakabaMark" to "WAHaMARk"!

>>343

"When they shouldn't be?" They've always been bolded.

> Making them configurable from site to site is really dumb, because it would create an unthinkable usability mess.

Why? Let people figure out things themselves, if they are so keen on changing their keywords. They can get together in their own webmaster threads and figure this out. I don't see why this should be solved here.
Of course I think this is a dumb idea in the first place. Nobody needs to know what fusianasan and sage are. Write a FAQ with two sentences about it and/or let your oldtime users tell newbies. Two frickin' words, and you people talk about it as if it were something like making up a new system of romanization!

> Then why not simply boil it all down to the comment field, with trigger strings for inputting the name, e-mail, sage, ID:Heaven, and fusianasan? You can get a lot more minimal with the current interface.

That's a bit too much. You want to talk about sage and fusianasan in the comment field, not trigger it with it.
I suspect you are joking here, though. Design is about what you can take away and still remain optimal conveniency/efficiency on the user part, not about taking as much away as you are technically capable of.

> You still end up with no way to link the fusianasan post with the name/trip one without IDs enabled (unless the ID method is known and no secret data is used).

You'd figure that people who know what fusianasan is will also know how to trigger IDs.

> You spelled it fusiansan once.

So I misspelled one word once.

Sue me!

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

Neither world4ch nor Pichan are by any means "large". Also, yes, as Shii said, their webmasters are stubborn.

>>55
I'm not complaining about the current system, just throwing around some new ideas for a change (instead of blindly following whatever new thing comes along on 2ch).

The point is to make a portable file, so you do not /have/ to compile it on the host. Statically linked lets you use libraries that the host does not have.

Sure, doing it in perl is an option though.

>>n74,76

It's good for referencing replies, too.

The "always show the first post" behaviour is sort of confusing at first. It seems more intrusive than useful.

> You mean requiring SQL software, or just making backwards-incompatible changes that would screw up old threads?

I mean, needing to alter the table that is already in the database. I don't want to try to do that any more than I have to, as it's pretty hard to get right in a database-independent manner.

> Are you only referring to flooding and spamming, or also trolls and flamewars?

Yes, only flooding and spamming. Trolling and flamewars are not a problem one should use banning to try and solve.

> Finally, out of curiosity: how much of the functionality in the .js file do you think could be properly implemented into a new or existing perl script?

Well, if you serve up dynamic pages, you can do the form-filling on the server, but that's about it. The rest is dynamic stuff.

Forgot this one:
The general functions of imageboards do not seem to be clear to most people that eventually come around, the influx of total newbies is still big. Many neither know what sage is, how to properly reply to threads, what tripcodes are, etc.
Because of that, I believe it would be good to include a default link at the bottom of the unordered list at the bottom of the new thread form that links to http://wakaba.c3.cx/docs/docs.html#UsersGuide

Relevant:
http://dis.iichan.net/idc/kareha.pl/1128824710/12-

One of the things I did when I modified and restructured the order of functions in post_stuff() was add specific error messages for each non-comment field. Would this be considered superfluous?

I found this:

fusianasan【ふしあなさん】［名・自ｽﾙ］
２ちゃんねるに書き込みする際に名前欄に「fusianasan」の文字列を入力すると、その書き込みをした人のリモートホストのＩＰアドレスがさらされるようになっている。
本来は「（固定ハンドル)@fusianasan」などとして、まだキャップを取得していない固定ハンドルが自らＩＰをさらすことで騙りを防ぐためのシステムである。
が、裏２ちゃん関係のコピペが横行するに至って、一時期うっかりＩＰをさらしてしまう。
エロな人間が続出し、fusianasan廃止要望まで唱えられるに至った(当然却下されたが)。
ＩＰをさらすことだけによる危険は、そのＩＰから手元で使用中のコンピュータを一意に特定でき
（ex：グローバルＩＰによる常時接続）、かつプロキシ・サーバー、ファイヤーウォールなどの防御策を怠っている場合にしか及ばないので、
fusianasanに引っかかったからといって実はそこまで神経質になることもなかったりする。
……過去にＩＰから仕事中に政府機関から２ちゃんねるにつないで裏２ちゃんに入ろうとしていた愚か者が釣れてさらされたという事例はあるが。
なお、現在では一部の板でデフォルトの名無しさん（名前欄未記入時の名前）が「fusianasanさん」などfusianasanを含む名前となっている場合がある。
また、串の性能を試すために敢えて裏２ちゃんに引っかかっていると思われる強者もちらほら見受けられる。

類義語：mokorikomo
参照：裏２ちゃん、キャップ