Hmmm, I just noticed you still allow <a> tags, which would let posters use inline links. Are you gonna keep that?

>>313 Like lots of people use them anyway </sarcasm>. Yes, security is a good idea. What are the holes, anyway?

> the entire server occasionally breaks

Occasionally?

Well, that might be it, except that on world4ch at least one board breaks every week, if not more. Incidentally, as of this writing, 4chan's /dis/ and /sug/ are also toast (third time this month?).

As it is, I can't recall ever seeing kareha break.

I'm not sure I want to make a ban system. I'd rather just make it easy to interface with a simple banning script that does whatever's needed for the server it's running on.

I found this:

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

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

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

Also, for multiple board installations, use symlinks to allow you to keep just one installation of the main code files.

requesting features:

• >>n and >>q and anything else that can be used in the url.

• a "catalog" page for wakaba, like some futaba boards have.

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

>>321
Wait, why should l50 links be indexed/cached? IMO the only links that should be on Google at all are main pages and "entire thread" links.

Some final points (I hope) before the whole thing is wrapped up:

• The CSS in the All threads page is unsightly. Is there a way to properly wrap the outer color border(s) around the table of threads?

• I still say that the "Navigation: " text is extraneous when people can clearly see what the links do. Also still partitioning for 0ch-style error pages (with displayed user host and all).

• Now that we do have filesize indicators in the backlog page of mode_message, do you still find it useless to have the red bold filesizes near the bottom of thread subpages?

• Does mode_message now work in PAGE_GENERATION => 'paged'?

• Idea: forced anonymous/sage/ID/fusianasan by IP/thread/board/whole site (some of these combinations already exist, I know)?

• Finally, I imagine that the permasage/close/delete functions in kareha.pl will be easily interchangeable among the conditions in post_stuff(). Can you confirm this?

> Can't this be somewhere else but the post form?

No, because that would be immensely useless and annoying, because nobody would know it's there, and even if they did, they'd have to go somewhere else every time they wanted to post something using a different markup.

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

>>360
Doesn't mean we can't have separate releases for special scripts. :)

About rel=nofollow: What links should have it? Obviously not the "entire thread" link, but the l50 links in the thread list sort of need it, otherwise the search engine will never find them in the first place. But that means the l50 links will end up in the index.

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

>>180

The one with encoded Javascript that makes you post with fusianasan is cute.

> I don't understand the argument for OH NO ANOTHER BUTTON MY WHOLE LIFE IS RUINNED crowd

It's all a design & layout question. I'd like to have the interface reduced to what is absolutely neccessary, esp. since I do not think many people really want to even bother or bother very often with the whole markup question.

> The replacement will be an option to select the default markup for a board, which makes much more sense overall.

I agree, this seems to make the most sense. I understand the "More options..." will not be showing up on boards with fixed settings, so I'll shut my mouth from now on. Apologies to all who I've been bothering.

>>112
We already have the ID function, so why do we need such an egregious compromise of anonymity (and security) like voluntarily exposing your own IP?

>>59-60

Details, please. Everything works for me.

Oh okay.

I agree, for Kareha at least.

> Right, I guess it was dumb to mention 0ch/Futaba in the first place. The point is, as you said yourself, tripcodes are a gimmick, and if someone wants to maintain a persistent identity across multiple boards and sites (ie, everyone here with a tripcode), they have no choice but to use ordinary tripcodes. Secure tripcodes are useless because they limit your identity to a single board, supposing each board/site's cipher key is different -- which it should be, since that's the point of having a secure tripcode in the first place. No one should be so paranoid about a tripcode that they'd need to have a different one per board/site.

True, they're of limited usefulness, but people like admins might prefer to use them. And there are certain cases were you might use them temporarily for various purposes. I wrote the code already, so I might as well leave it in. It has some uses at least.

> Shouldn't we sacrifice some backwards compatibility for a more robust and scalable design? It might even be possible to provide an upgrade.pl for old threads.

I think I'm too lazy to do it. It's kind of hairy. Besides, as I said, you can remove a lot of the drawbacks of seprate installations by using symlinks.

Random post: The test thread could use some linking in the notes at the bottom (what's the common nomenclature for that one?).

> some other trickery

I smell JavaScript coming in about >>90-120

>>48

That is an interesting idea, and one that deserves some more thought.

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

>>91 Ohshi-, time paradox!

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.

>>54
I really don't understand what the problem with the current system is. You must be confused. ┐('～`；)┌