The Legendary Next Update (365)

17 Name: !WAHa.06x36 2005-10-13 06:16 ID:ReFmOAs0 [Del]

>>16

Yes, it's throwing Javascript errors for me if I use that character. Gonna look into that some more.

158 Name: Anonymous 2005-10-19 14:19 ID:Heaven [Del]

> They can modify it an claim copyright on their modifications, at least as long as they're significant enough, but that doesn't affect existing works in the public domain.

Devil's advocate: What if they make significant changes you would want to add yourself? before you do? Can they then tell you to stop if they license their work first?

10 Name: Anonymous 2005-10-12 22:19 ID:UAOHJNRy [Del]

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

160 Name: Anonymous 2005-10-19 14:51 ID:Heaven [Del]

>>157
So the functions need to be hardcoded to a post element one way or another? If I wanted to, let's say, create a template for gazo-box or Shiichan (both use checkboxes for sage), I'd need to slightly modify kareha.pl to check that new checkbox input instead of the Link string input?

An interesting limitation. Thanks for explaining.

About permasaging/deleting after a certain thread filesize is reached: would this be the same as a limit on the total number of characters in a thread? Or would we also include WakabaMark formatting, hyperlinks (including navigation), name/date/title headers, reply boxes, and non-Unicode characters in the formula?

>>158
Chances are that most if not all major/fundamental changes made to Kareha's core scripts will clash with the philosophy of most people here (including WAHa), and they won't care for them anyway. There really aren't all that many big-bang end-user features left to be implemented in Kareha before it loses its minimalist charm.

P.S. Reminder for >>85

300 Name: Anonymous : 2005-10-23 23:06 ID:Heaven [Del]

>>299
Seconded. This'll go a long way to resolving headaches with WakabaMark and SJIS art, and there really isn't anything egregious about its current implementation into the mode_message template (nothing compared to putting it in a separate area, for example)

Going back to the CSS selector: since switching styles is not inherently supported in all browser GUIs, how about having a third party create extensions for those browsers and freeing up the real estate on the actual page? The selector to me seems out of place with the rest of the layout, simply because it's only there for the purpose of presentation, not the actual page content. How many people out there change styles from board defaults on a regular basis because of readability preferences?

69 Name:   2005-10-17 07:26 ID:Heaven [Del]

>>66-67

Noted and fixed in development version.

245 Name:   2005-10-22 10:56 ID:Heaven [Del]

Wow, >>243 sure looks like shit in Safari. What the hell? Looks right in Firefox, though.

196 Name: Anonymous 2005-10-20 12:51 ID:tlSRz7E3 [Del]

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

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

huh?

50 Name: !WAHa.06x36 2005-10-15 19:03 ID:Heaven [Del]

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

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

PS. What's "Raw HTML"?

23 Name: Anonymous 2005-10-13 22:46 ID:0dCD+kFU [Del]

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.

266 Name: Anonymous : 2005-10-23 14:52 ID:Heaven [Del]

ugh "More options..."

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

out! out!

320 Name: Anonymous : 2005-10-25 20:17 ID:Heaven [Del]

358 Name: Anonymous : 2005-10-31 12:45 ID:QLQI2pST [Del]

...and admin posts that override all board/thread restrictions (ie, bumping a permasaged thread and possibly even posting in closed threads).

73 Name: Anonymous 2005-10-17 08:21 ID:Heaven [Del]

>>71
forgot to add that turning the CSS selector and Admin functions into drop-down menus and moving them to the right side of board and thread title headers would remove that top bar entirely on the front page.

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.

230 Name: Anonymous 2005-10-21 18:43 ID:Heaven [Del]

I think it'd be a better idea to have some kind of load-balancing/distributed server cluster approach, like what dmpk2k was working on for Wakaba.

325 Name: Anonymous : 2005-10-26 18:47 ID:Heaven [Del]

>>324
I've heard they use it on a per-IP basis for troublesome posters on 2ch. It could also discourage people from being jisakujien (supposing ID is disabled) or posting in a certain thread unless they're totally willing to have their host revealed.

345 Name: Anonymous : 2005-10-27 10:50 ID:Heaven [Del]

>>344 orz

291 Name: Anonymous : 2005-10-23 19:54 ID:Heaven [Del]

No "2ch mode" link in the footer? I think Hiroyuki deserves some credit.

44 Name: !WAHa.06x36 2005-10-14 16:33 ID:Heaven [Del]

Uh, kind of a bug. I really should fix it, but, lazy.

362 Post deleted by moderator.

265 Name: !WAHa.06x36 : 2005-10-23 14:24 ID:Heaven [Del]

All right, code updated again. This time, some experimenting! I've implemented a tentative system for changing markup types. This needs a bunch of testing, of course, so here's the test thread link once again: http://wakaba.c3.cx/sup/kareha.pl/1099697376/

Thoughts and comments are welcome. I'm still trying to figure out how exactly to do this.

There's a bunch of other changes and fixes too, so mention if anything breaks, as usual. Also, shift-reload!

47 Name: Anonymous 2005-10-14 22:48 ID:1l2MEdqn [Del]

>>46
Well, I haven't checked to see exactly where the ban functionality exists in Kareha, but my idea is something along the lines of: (1) encrypting the offender's IP, (2) writing it to a bans.txt list, and (3) writing a parameter next to the IP specifying the time when the ban should be lifted. Of course, you also need underlying code to check bans.txt every time a user tries to post or reply, and also to remove a ban entry at its specified time.

242 Name:   2005-10-22 10:53 ID:Heaven [Del]

Here's a fun little game for you all!

I'm looking into adding support for using HTML markup in addition to WakabaMark, but since most boards use XHTML, I can't just let through any old HTML, and most people can't write well-formed XHTML. Also, I don't want any cross-site scripting going on. So I've tried to write a piece of code that takes any horribly written piece of HTML, sanitizes it by removing all tags and attributes that are not an approved list, checks the attribute values, and turns it into well-formed XML.

Now I'd like to see if anyone can break this. The objective is to get some Javascript onto the page, or making the page break in Firefox (or any other browser that parses XML strictly), or otherwise causing trouble. Have at it!

http://wakaba.c3.cx/test/sanitize.pl

57 Name:   2005-10-16 21:11 ID:gBva8ggI [Del]

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/

164 Name: Anonymous 2005-10-19 18:08 ID:Heaven [Del]

>>161

>3) was about a string to trigger ID:Heaven, not a constant for the Heaven part (which is already configurable)

That's what I was referring to also in >>154 (S_NOID being the theoretical trigger string for ID:Heaven).

Concerning localization: there are certain compromises with input triggers that must be made in order to maintain interoperability with Japanese users coming from 2ch/Futaba. They're not going to care about a system where "sage" and "fusianasan" (in Roman too I'm guessing, can someone confirm this?) don't work in their respective fields. In effect, 2ch set a standard of usability that we need to follow if we want to build a bridge between both communities.

On the flipside, I think there should also be a secondary set of trigger strings that would be more coherent to Western users and universal to all Western boards. Making them configurable from site to site is really dumb, because it would create an unthinkable usability mess. With Shiichan's death, Kareha stands unrivaled, and setting these strings in stone would ingrain them in the culture like "sage" and "fusianasan" have been in Japan. Thinking very optimistically, if a Western BBS site should grow into something large enough for 2channers to strongly take notice of, they would pick up on these triggers and possibly make their own concessions to implement them in 0ch.

What they should be is yet to be determined. Unfortunately, they'll probably have to be pretty dull in comparison to the witty botanical references and word puns in 2ch and Futaba.

>>163

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

Then why not simply boil it all down to the comment field, with trigger strings for inputting the name, e-mail, sage, ID:Heaven, and fusianasan? You can get a lot more minimal with the current interface.

>Huh?

He meant saging a thread just because a part of the actual e-mail address contains the word "sage."

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

352 Name: Anonymous : 2005-10-28 06:34 ID:Heaven [Del]

At least i got 350

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