n is implemented, but not for >> yet.

Also, >>1 is, as it is, only added to URLs of the form xx-yy and lxx. 2ch doesn't add >>1 for single-reply URLs, and if you're using commas, I figure you can add >>1 yourself if you want it. I'm not sure if this is the best behaviour, but that's how it works at the moment.

Too late! Already released!

> partition to kill secure tripcodes

signed

> add functionality for multiple uploads in one post.

I think this was decided against before.

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

>>231 What would it do?

>>140

So, does that mean you approve of removing the style selector on subpages? I just woke up and I'm confused.

Anyway, Safari doesn't, as far as I know, let you pick stylesheets. And IE obviously doesn't. Also, not even Firefox will actually remember your choice, making the ability completely useless anyway, unless coupled with Javascript on the page to save the setting.

> The Futaba template is missing the "No File" checkbox next to the File field in the Post New Thread area.

That's because Kareha has no "No File" check in the first place, and I'm not sure I want to add code just for that (since it'd have to be optional anyway).

> To more closely resemble the 2ch look, how about prefixing thread title headers in the main board page with a 【position:postcount】thingie?

I find the "1. Thread title (1000)" format much more readable in the post list. And for the main titles, I don't see any value is putting the position in there. That serves no discernable purpose.

> And as suggested before, the navigation links on the bottom of individual thread pages should include "Previous 100" (ie, all posts before the first post in the URL) and "Next 100" (ie, all posts after the last post in the URL).

They already do, but only if there are enough posts in the thread for this to make sense. Or, try a short range like 23-27 to see it in action.

> The "First 100" link should also be removed from the bottom of individual thread pages, and there should be a link to to thread-list included below the reply box of each previewed thread on the front page.

I've been wondering about the justifications for which navigation links should go where. 2ch has it pretty much worked out, I'm sure, but I don't quite see why there should be a "First 100" at the top but not at the bottom.

> Change "Del" links to widget buttons.

Would be very ugly. Those buttons are big.

> In order for the CSS selector not to take over the entire header, how about turning it into a drop-down menu?

I was meaning to do that from the start, but there was some problem with gettting it right. I forget what exactly.

> The same could be done with the Admin functions (appearing only after one correctly inputs the password), placing it on the right side of the board and thread title headers (this would also allow admins the convenience of deleting and permasaging threads from the front-page).

Squeeks would prefer to have a separate script for admining. I'm not sure which is the best approach here.

> and would something like this work (given that all boards share the same root directory)?
> >>>>sup/1129153864/1-100
> >>>1129153864/1-100

Maybe, but I don't see the value in adding code for this, given that you can just paste the URL in there.

> P.S. When you mentioned serving dynamic pages in >>46, were you referring to individual thread pages? As I mentioned before, it'd be nice to make the front page as dynamic and flexible as thread pages when it comes to viewing options (via PATH_INFO).

The front page gets lots of hits. This would drive up CPU usage something fierce.

> Oh, and please bring back MAX_LINES.

I still don't think it serves any useful purpose.

> Maybe the thread title should be an l50 link?

That's what I've been saying in >>3!

> If anything, the role of capcodes should be minimized or altogether eradicated, in favor of ninja moderation.

It's up to the administration of the site how to use them. I am advocating that if they are used at all (and yes, there are useful instances for this and yes, these are and should be rare) then it would be helpful to be able to differentiate between site owner/admin/supermod/mod/maid/etc

test1

Ah, there was an XHTML error in the cutesy capcode, and of Safari won't handle XHTML correctly and die on errors. Gah. Fixed.

I don't know if this is a bug or not, but could you change the Futaba template so that hovering over/clicking on a post header doesn't count as doing the same to the deletion checkbox next to it? Same goes for the "[File Only]" area at the bottom with its checkbox.

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.

"page top" is better imho

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

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

Ah, there was an XHTML error in the cutesy capcode, and of Safari won't handle XHTML correctly and die on errors. Gah. Fixed.

/-100 shows the first post two times.

>>151 It's all public domain, I believe.

http://wakaba.c3.cx/sup/kareha.pl/1099697376/101-101
(First "Next 100" link) does not include >>1 in that thread

There's also some weird bug where the entire browser windowd content goes black, dunno what that is about...

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

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

> Maybe the thread title should be an l50 link?

That's what I've been saying in >>3!

> If anything, the role of capcodes should be minimized or altogether eradicated, in favor of ninja moderation.

It's up to the administration of the site how to use them. I am advocating that if they are used at all (and yes, there are useful instances for this and yes, these are and should be rare) then it would be helpful to be able to differentiate between site owner/admin/supermod/mod/maid/etc

>>214

Point taken. I'll add it as an autoclose option.

> To more closely resemble the 2ch look, how about prefixing thread title headers in the main board page with a 【position:postcount】thingie?

I find the "1. Thread title (1000)" format much more readable in the post list. And for the main titles, I don't see any value is putting the position in there. That serves no discernable purpose.

> And as suggested before, the navigation links on the bottom of individual thread pages should include "Previous 100" (ie, all posts before the first post in the URL) and "Next 100" (ie, all posts after the last post in the URL).

They already do, but only if there are enough posts in the thread for this to make sense. Or, try a short range like 23-27 to see it in action.

> The "First 100" link should also be removed from the bottom of individual thread pages, and there should be a link to to thread-list included below the reply box of each previewed thread on the front page.

I've been wondering about the justifications for which navigation links should go where. 2ch has it pretty much worked out, I'm sure, but I don't quite see why there should be a "First 100" at the top but not at the bottom.

> Change "Del" links to widget buttons.

Would be very ugly. Those buttons are big.

> In order for the CSS selector not to take over the entire header, how about turning it into a drop-down menu?

I was meaning to do that from the start, but there was some problem with gettting it right. I forget what exactly.

> The same could be done with the Admin functions (appearing only after one correctly inputs the password), placing it on the right side of the board and thread title headers (this would also allow admins the convenience of deleting and permasaging threads from the front-page).

Squeeks would prefer to have a separate script for admining. I'm not sure which is the best approach here.

> and would something like this work (given that all boards share the same root directory)?
> >>>>sup/1129153864/1-100
> >>>1129153864/1-100

Maybe, but I don't see the value in adding code for this, given that you can just paste the URL in there.

> P.S. When you mentioned serving dynamic pages in >>46, were you referring to individual thread pages? As I mentioned before, it'd be nice to make the front page as dynamic and flexible as thread pages when it comes to viewing options (via PATH_INFO).

The front page gets lots of hits. This would drive up CPU usage something fierce.

> Oh, and please bring back MAX_LINES.

I still don't think it serves any useful purpose.

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

> Is it intentional that thread links without a trailing slash

Uh, I was wondering the same thing. I'm not sure. I guess I should fix that.