The Legendary Next Update (365)

228 Name: Anonymous 2005-10-21 17:35 ID:13VMAtd0 [Del]

   ∧∧
  (  ・ω・)    It's late
  _| ⊃/(___
/ └-(____/

   ∧∧
  ( ・ω・ )    Good night!
  _| ⊃/(___
/ └-(____/

  <⌒/ヽ-、___
/<_/____/
 ̄ ̄

124 Name: Anonymous 2005-10-18 07:43 ID:9mxxoE2M [Del]

>>123
signed

64 Name:   2005-10-17 05:03 ID:gBva8ggI [Del]

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

165 Name: Shii the Metal Idol 2005-10-19 18:13 ID:z/kxsMjQ [Del]

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

190 Name:   2005-10-20 11:11 ID:Heaven [Del]

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

330 Name: 329 : 2005-10-26 20:02 ID:Heaven (Image: 1010x554 png, 76 kb) [Del]

src/1130378556374.png: 1010x554, 76 kb

Oops, here's the screenshot. orz

20 Name: !WAHa.06x36 2005-10-13 12:03 ID:gBva8ggI [Del]

>>19

I can't reproduce this on Firefox 1.0.4 nor Safari on the Mac, but that ancient Firebird had a similar problem (but even worse).

Anyone else? Try post with a | in your name.

201 Name: Anonymous 2005-10-20 18:28 ID:Heaven [Del]

> people like admins might prefer to use them

but they have capcodes now...

77 Name:   2005-10-17 09:10 ID:Heaven [Del]

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

86 Name: Anonymous 2005-10-17 12:33 ID:Heaven [Del]

> The Title field should go above the Name and Link fields in 2ch mode.

Why should it?

> From every practical standpoint, the current solution in Kareha is a lot more convenient

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.

> Futaba now uses "..." instead of ">>>" to prefix repy blocks.

Any idea why?

14 Name: !WAHa.06x36 2005-10-13 04:30 ID:gBva8ggI [Del]

I've been meaning to change some of the defaults away from Futaba-style to saner behaviours. Any suggestions for what to change are welcome. So far:

  • Pruning set to furthest-back instead of oldest.
  • Size limit instead of post number limit, maybe?
  • I'll add thread closing to Kareha, but I was thinking of setting the default behaviour to never permasage or close threads.

80 Name: 79 2005-10-17 09:17 ID:Heaven [Del]

Argh, beaten and >>n isn't even implemented. orz

58 Name: anon <-- Testing person 2005-10-16 21:13 ID:Heaven [Del]

huh?

213 Name:   2005-10-21 14:44 ID:Heaven [Del]

> More information on the all threads page, date of the last post? file size?

That might be somewhat useful, I suppose. I'll have a look at it.

> A quote button that puts >>n and puts the post prefixed by > in the reply box

There's already a way to put in >>n. However, quoting an entire post is seldom something you want to do anyway, so I don't think that's worth cluttering up the page with a million buttons for.

> Different secret strings for different functions (e.g. one for ID generation and one for secure tripcodes)

Most admins probably don't get point of the secret string anyway, and asking them to put in several is just too annoying. In retrospect, I'd like to add a second layer of hashing to these, but that'd mean breaking secure trips AGAIN.

> A trigger for turning wakabamark off and one for forcing a monospace font

I've been trying to work out a more elegant solution for this.

37 Name: Anonymous 2005-10-14 13:32 ID:Heaven [Del]

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.

349 Name: Anonymous : 2005-10-27 17:20 ID:Heaven [Del]

349 Name: Anonymous : 2005-10-27 17:20 ID:Heaven [Del]

251 Name: Anonymous 2005-10-22 13:00 ID:Heaven [Del]

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

278 Name: Anonymous : 2005-10-23 18:02 ID:Heaven [Del]

Text Art's description about auto-linking URLs and >> references is redundant. Not a bad solution with the layout, though (hiding the menu behind "More options..." still bugs me).

303 Name: !WAHa.06x36 : 2005-10-24 05:33 ID:Heaven [Del]

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

231 Name: Anonymous 2005-10-21 21:04 ID:Heaven [Del]

How about adding a link to 2ch in footer.html called "2ch mode"?

272 Name: Anonymous : 2005-10-23 16:33 ID:Heaven [Del]

PS. What's "Raw HTML"?

54 Name: Anonymous 2005-10-16 09:20 ID:Heaven [Del]

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

110 Name: anon!21anon4H3U 2005-10-17 20:22 ID:Heaven (Image: 1024x768 png, 36 kb) [Del]

src/1129602164301.png: 1024x768, 36 kb

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!

190 Name:   2005-10-20 11:11 ID:Heaven [Del]

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

356 Name: !WAHa.06x36 : 2005-10-28 20:05 ID:Heaven [Del]

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.

139 Name:   2005-10-18 20:03 ID:gBva8ggI [Del]

You can't document easter eggs! That's crazy talk!

Also, I find it insanely more annoying to write text in five-line tunnel vision than whatever annoyance might be caused by a comment box that expands.

30 Name: !tFiTnDB9dg 2005-10-14 00:56 ID:Heaven [Del]

testing #`¦

304 Name: Anonymous : 2005-10-24 11:09 ID:Heaven [Del]

Hmm, the new error page looks much better except the overlapping of the navigation bar with the error message box.

182 Name: Anonymous 2005-10-20 09:19 ID:Heaven [Del]

>>174

>Let people figure out things themselves, if they are so keen on changing their keywords.

If you really want to use your own custom trigger strings, you can easily search kareha.pl for instances where "sage" and "fusianasan" are used in that context and either replace them with those custom strings or append them as secondary strings. It's not something that warrants additional config.pl parameters.

This thread has been closed. You cannot post in this thread any longer.