Additionally, I'd like WakabaMark to be fixed somehow.
I don't know how, though. You know my resentments.

Finally, thanks for your fine work throughout all this time.
It is appreciated!

> 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

>>189

>The effect would be miniscule in comparison to the huge increase in bandwidth that would result from sending the entire static thread pages.

How about a config.pl parameter to split up thread subpages into X posts per page? The navigation links already use 100 posts per page for practically everything except "Last 50 posts".

Hmm, I just remembered: >> links would not work at all with static pages. Not good.

>Why? Even if 0ch or Futaba implemented secure tripcodes, you wouldn't get the same secure tripcode there as on another board. That's the nature of the security.

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.

>Not without doing a lot of changes throughout the code, and not without breaking current installations.

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.

>>193

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

That's a cool idea, though for now it would have to be left alone if we want to keep Kareha compatible with 2ch/Futaba conventions.

>>195
Exactly. The methods and the effects of saging a thread are separate subjects.

P.S. I recently discovered "rXX-XX" for threads in /soc/. How exactly does this work? From the sound of it, it's supposed to randomize the post order, but when I hit refresh I get the same order.

>>38
Sorry, I guess I should've worded that more clearly. I was referring to the ability for users to delete their own posts. It's counter-productive to discussions when a user deletes his own post and a quick replier later quotes or references it. It also encourages users to be lazy with posting, because they can always go back and hide their mistakes.

> Frankly, the combinations of many things into unrelated fields is a design flaw.

I don't think so, not in these cases. What's the alternative? Having a different field for fusianasan, a new checkbox for sage, etc.? That's just cluttering up the interface.

> What if you want to use a name/trip and fusianasan?

Then just make one post with your name/trip and one with fusianasan and let your ID show up in both.
fusiansan is just intended for rare or special cases anyway, as is the whole subject of identification on anonymous message boards.

> What if your email address contains the string 'sage'?

Huh?

> What if you want to sage a thread, but have an ID still?

Then the board has to be configurated to just do that (it already can).

> why should I have to remember something so foreign?

It's rarely needed anyway. Also, these things are pretty easy to remember. "sage" and "fusianasan" is all there is, really.

>>259

Fixed.

>>260-261

The test script doesn't try to handle charsets at all at the moment.

All right, a beta version with some new features is now installed for this board. It implements a couple of bug fixes, and navigational and 2ch-style improvements suggested in this thread. Try it out, and complain about stuff that doesn't work or doesn't make sense.

I also put in customizable capcodes now. You can define a string of arbitary HTML for the capcode, so you can put whatever kind of fagginess you want in there! Hooray! Try this out by posting with #test.

The good old test thread is still here: http://wakaba.c3.cx/sup/kareha.pl/1099697376/

Weird, ¦ now stays ¦.
Testing #¦ now.

What wakaba needs is that SILLY_ANONYMOUS too! :D

WAHa, WAHa, it's a bug!

Pressed back after creating an error message in karaha (trying to reply to this thread, forgetting to type something in here), refresh does nothing!

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

>>244

Er, that's a feature, not a bug. That's how most GUIs act.

Removed it when redesigning the page head, haven't figured out quite what to do about it yet. It needs to be changed, but to what, I'm not yet sure.

I fixed the Javascript a bit, and uploaded it for these boards. Try shift-reloading to get the new code, and see if cookies work better now that I'm not using cargo-cult code.

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

Actually, no, the Javascript just strings some random numbers and letters together.

> Because it's one of the two requirements for creating a new thread, and it's a lot more important to have a well-defined topic than to fill in your name.

But the body text is even more important, and that goes at the bottom. So I dunno.

>It's more convenient if you want to start a new thread, but for those who don't it's one more form to have to scroll by.

Would it maybe make sense to make a separate thread creation page?

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

> I'd like to have the interface reduced to what is absolutely neccessary

That's why there is a "More options..." link, instead of putting the controls there on every single thread everywhere.

> people like admins might prefer to use them

but they have capcodes now...

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

> forced fusianasan

that seems kind of evil.

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

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

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

> Huh?

You know, like [email protected].

Shiichan 2000 let you enter "down" to sage and "showip" for fusianasan, but it was mainly just a curiosity and was not used. There's no one English word that does the job of the pseudo-Japanese "sage". Better to have a tick-box and explain to people why it is useful. Or an option for it.

> Then the board has to be configurated to just do that (it already can).

No, 148 is referring to a user-end problem, not a server-end problem.

>>184
If people are going to decide to use custom names for paramaters, then there isn't much you can do about it anyway, or is there?

>>137
I also noticed that you removed the CSS selector in individual thread views. Personally, it seems both the Admin options and Style selector are a bit of a hindrance to the overall layout. Don't get me wrong -- I think the drop-in Style capability is fantastic-- but it just doesn't seem to play nice with the current 2ch page design.

The thing is, don't most or all major browsers these days allow users to change CSS styles from within the application itself? I know Firefox does, at least. Maybe the selector isn't really necessary.

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

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

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

> Does the CSS selector -really- get in your way?
> Is having the More options thing really ruining your experience,

Yes and yes and I already stated why.

I am sure you know this but text markup takes place on a whole different level than identification/bumping issues. Your comment about pgp signatures is very funny but I will not honour it with a comment.

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.