>>255
By replacing it with AN EVEN DUMBER PUN!

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

Let's get to 1000 by "I want a pretty pony" only! ヽ(´ー｀)ノ

First thought: It would eliminate the concept of sageing as a protest entirely.

I found this:

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

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

GDLib for thumbnails: http://wakaba.c3.cx/sup/kareha.pl/1113869490/5

>>103

Noted.

>>154 YOUdqn!

Whoops, sorry. I read "close" instead of "permasage".
Permasage on filesize seems pretty silly, yes.

Copyright only applies to the literal code, not to features, ideas, or algorithm. Patents do, to some extent, but that's not the issue here. Since I'm not going to write the exact same code, there's little they can do.

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

> and/or let your oldtime users tell newbies.

Like so? http://wakaba.c3.cx/soc/kareha.pl/1124991549/7

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

>>64
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeh? You are not the real >>64!!!

>>210

monospace font? like this?

Hmm, looks like my ISP fails at keeping my IP secret.

(Lots of stuff in here, click "whole post"!)

> How about listing what dmpk2k or you have done already?

Truth be told, I haven't even looked over his contributions yet. I'm doing some work on Kareha first. He did bandwidth load balancing for Wakaba across several servers, and image file archiving, at least. Plus some proxy checking and other goodies.

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

Bad idea. Adds a lot of code complexity without adding any new functionality. The current solution is simple and robust.

> Automatic closing and moving of threads that do not get any activity in a certain timeframe (based on average activity frequency of the board)

This is nearly impossible to get right, and I don't think I'm going to try unless someone can think up a reliable algorithm that uses the data that is availble (not much).

> Reintroduction of "Marked for deletion (old)" (it's just handy to have that)

I tried several times, and concluded it wasn't worth the code and database overhead it would take. This feature is relatively easy to implement for Futaba-style post number limited boards (and Futaba implements it really stupidly), but it gets tricky when you have different deletion modes and want to do it right.

> Prune-limit mode that is defined by number of files or size sum of files on a board

Size limit is already implemented. I might add file limit, but I'm not sure it's all that useful, when you already have the size limit.

The rest, I agree with, and I will try to get most of it done. I'm sure there's some more stuff hidden in old threads, though!

Nothing specific, just protecting against any possible future ones.

Also, I'd like to ask exactly how Kareha does automatically generates deletion passwords. I'm guessing it's similar if not identical to how it creates ID session codes with a user's IP.

>>16

What browser are you using? I think I've tracked down the problem, and it's most likely a browser bug. The ancient Firebird (not fox, even) version I tested at work had the same bug (character set issues in the escape() and unescape() functions). It looks like your browser also doesn't follow the spec for how they are supposed to work.

>considering the default prune behaviour of imgboards

One of the parameters Kareha uses to determine pruning is MAX_POSTS, so even if you sage a thread under this new condition, you still add to the board's total postcount and speed up the process for pruning that thread, regardless of MAX_RES. The only flew is this assumes pruning is based on thread creation date, not popularity (because someone could easily bump a shitty thread and save it from deletion).

I also agree that enabling this functionality would further make threads vulnerable to intentional bumping by trolls. I was sorta envisioning it being used in a mature community where trolling is minimal and quickly weeded out by regulars.

Here's a new idea: how about trying this in reverse? Only "sage" posts are counted in MAX_RES, in which case saging can again be used either in protest or as a courtesy to others. The only problem is that people can then freely bump threads without consequence.

> change the no-ID-on-email option to no-ID-on-sage
> multi-page links (1-, 101-, 201-, etc) at the top of subpages

Already implemented.

> 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?"

> no EMAIL_ID parameter (most if not everyone uses "Heaven" anyway, and if they really want to change it they can easily find the string in kareha.pl)

The choice of this string is so weird and arbitary, I feel better keeping it as an option so that I can disclaim responsibility!

> better configuration of date and time (with optional timezone offsets), parsing certain characters for individual elements (ie, yyyy/MM/dd(D) hh:mm:ss -5:00:00) and also accepting numerical inputs for fixed dates and times (Eternal September)
> red, bold thread filesize indicator near the bottom of subpages

Pretty useless. I'd rather not waste work and code on something that has no actual use. (Timezone offsets would be useful, but this is such an incredibly hairy issue to get right, I don't want to even try. Just handling Daylight Savings Time would make my head explode, and I can't just leave it out, because then either the admin has to keep changing the offset, or the time will be wrong half the year anyway.)

> non-bolded post numbers
> colons before dates
> colons before names (thread subpages only)

what

The problem reported in >>143 is still present.

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

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

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

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