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

What wakaba needs is that SILLY_ANONYMOUS too! :D

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

Thanks. I did it the hard way and put in the proper transformations everywhere so filenames can be kept intact, though.

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

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

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

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

Currently, pruning by age is measured from the time of the newest post in the thread, so it wouldn't really work. I'm not sure if this is the best behaviour or not, but it seems it makes more sense to kill threads nobody cares about than to kill slow-moving threads just because they get old.

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

So, I made the All threads page a lot fancier. Might need some shift-reloading to get the proper CSS.

Is this about done, besides the admin bit? I'm getting a bit tired and distractions are looming to the left and right.

> (albeit edge cases)

Which is the crux of the matter - it mostly doesn't matter to the vast majority of users.

> 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 can use fusianasan with a tripcode, at least on Kareha. I suspect you can on 0ch too, but I haven't checked.

Put the Entire thread link on the top of the thread, not the bottom.

>>165

>There's no one English word that does the job of the pseudo-Japanese "sage".

How about "dontbump" or "nobump"? Using "down" is pretty misleading, since sage doesn't bump a thread up nor down; it just stays in its place until a thread below is bumped.

>>167 orz

In reference WAHa's post in http://wakaba.c3.cx/sup/kareha.pl/1127713568/l50

>It's been suggested to change the no-ID-on-email to no-ID-on-sage

That sounds good to me.

| stays |

>>180

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

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

>>266

I told you to shift-reload!

I almost forgot this:

For thread-closing, it would be nice if Kareha would post a last post, telling the thread is now over and closed (with some default message that can be customized for each board), akin to the 0ch 1001th post behaviour.

ugh "More options..."

too much clickable elements! and it doesn't even do anything (Firefox 1.0.7 here)!

out! out!

So, as Xee is almost done, and I'm mostly waiting for external contributions, I decided it was time to start working on the Legendary Next Update for Kareha and Wakaba.

Only problem is, it's been a long time, and I've forgotten most of what needs to be done. Most of it is mentioned SOMEWHERE on the board, though. So this is your chance to pipe up with your pet feature request, or if you're feeling really helpful, to dig out some old posts that mention things that need fixing.

Hop to it!

test1

>>249
<a href> opens up the possibility of using inline links, and img tags allow bandwidth leeching from other sites (plus the fact that the image itself may be unsanitary).

>>63
Nevermind, the issues seem to have resolved themselves within the hour of the new version being uploaded.

More stuff:

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

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). Of course, this could get screwy if you're using reverse order and out-of-order posts in the URL, so I dunno how well it could be implemented.

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.

Bonus:

Change "Del" links to widget buttons.

In order for the CSS selector not to take over the entire header, how about turning it into a drop-down menu? 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).

and would something like this work (given that all boards share the same root directory)?

>>>>sup/1129153864/1-100
>>>1129153864/1-100

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

Oops, forgot to link the first point to my original thread: http://wakaba.c3.cx/sup/kareha.pl/1127326007

Oh, and see if dmpk2k is willing to port over the proxy detection and load-balancing/distributed server cluster functions to Kareha. Those would be neat.

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

>>Well, then you are out of luck, aren't you? So you want to enter your E-Mail but cannot because then the post wouldn't bump then? Solution: Write it in the comment field, problem fixed.

There is no reason to change well-known keywords for this or even turn this into a frustratingly unconvenient tickbox/checkbox.
Having a specific trigger to trigger ID would also work.

>discussion of only one comment box, then you couldn't talk about sage/fusianasan/whatever

You could only trigger the functions in a specific format, say

:link-sage
:name-blah#faggot

lol comment

I do not believe this was an actual request, but it is obviously possible and usable. Another way would be escaping keywords that you want to post.

> partition to kill secure tripcodes

Why? If you are going to get rid of secure tripcodes you should get rid of tripcodes by the same reasons. On another note, why have I seen partition instead of petition multiple times?

>So I misspelled one word once. Sue me!

My point was that it is unnesessarily obtuse, not nit-picking that you misspelled it.

>This is a widely used system. There is a very low learning curve here. sage = does not bump thread when replying, that's all there is to know. People can then figure out why it is useful on their own.

You would think there is a low learning curve, but that is not really the case. For example, on an imageboard, what effect do you have making a sage post (with no real content) with prune oldest and a permasage limit? What about prune oldest with a permasage limit that excludes sage replies?

>trigger replacements

I'm not sure what to replace sage with, if anything. Down certainly doesn't describe it (to me it implies the reverse of age, which is not the case). don't_bump or dont_bump? show_host or show_ip works for fusianasan imo... show_ID to trigger ID?

>>182
That's not what I meant. What I meant was: If people want to change keywords to something, let them figure out at appropriate places what this something should be. Whether it should be "down", "stay_down" or "stay_put" is not really a discussion belongs here, not at this point anyway.