The Legendary Next Update (365)

259 Name: coda 2005-10-22 15:01 ID:1jzeBBcT [Del]

the text

c < d

causes a <d> tag to be opened, which is not on the list, and therefore all the text until the next tag will be deleted. a better behavior in this case would be to just convert that < to &lt;. you even ought to do this for

a < b

too, despite the fact that b is a valid tag, because who the hell leaves the closing angle bracket out of their HTML tag?

creating the correct regexes for this is an exercise left to the reader.

161 Name: 148 2005-10-19 16:30 ID:0dCD+kFU [Del]

RENZOKU are the flood detection things... even if they are useless MAX_POSTS_PER_MINUTE makes a lot more sense than RENZOKU2

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

Re: email/link field

Just because it works one way on 2ch/whatever does not mean it is the best way. Having 'fusianasan' as the only way to trigger the effect is just narrow-minded. Functions should have descriptive names to the people using them; should we keep the field names in Japanese because the Japanese have them in Japanese? Having all of the applicable things configurable is something that makes sense, and you can easily have both 'fusianasan' and 'show_ip' that work at the same time. Frankly, the combinations of many things into unrelated fields is a design flaw. What if you want to use a name/trip and fusianasan? What if your email address contains the string 'sage'? What if you want to sage a thread, but have an ID still?
I think the confusion of existing users is worth reducing the learning curve and improving the intuitiveness.

I'm not saying that the default behaviour needs to change, but being able to easily configure the strings used allows for easier localization.

I probably misspelled fusianasan too, why should I have to remember something so foreign?

130 Name: Anonymous 2005-10-18 17:19 ID:Heaven [Del]

Oh, and I apologize for indirectly causing you too much trouble with this change.

344 Name: !WAHa.06x36 : 2005-10-27 10:34 ID:SjmelPTB [Del]

>>343

"When they shouldn't be?" They've always been bolded.

106 Name: qube3.mackey.miyazaki.miyazaki.jp 2005-10-17 15:49 ID:JzjmoL7r [Del]

test

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

Oh yeah, regarding the CSS selector: HTML dropdowns aren't styleable, and will look like shit. I'll look into using some other trickery for that, though.

211 Name:   2005-10-21 14:41 ID:Heaven [Del]

> change the no-ID-on-email option to no-ID-on-sage
> multi-page links (1-, 101-, 201-, etc) at the top of subpages

Already implemented.

> config.pl parameter to permasage after a certain thread filesize/total number of characters has been reached

Isn't this essentially the same as saying "Please don't talk so much?"

> no EMAIL_ID parameter (most if not everyone uses "Heaven" anyway, and if they really want to change it they can easily find the string in kareha.pl)

The choice of this string is so weird and arbitary, I feel better keeping it as an option so that I can disclaim responsibility!

> better configuration of date and time (with optional timezone offsets), parsing certain characters for individual elements (ie, yyyy/MM/dd(D) hh:mm:ss -5:00:00) and also accepting numerical inputs for fixed dates and times (Eternal September)
> red, bold thread filesize indicator near the bottom of subpages

Pretty useless. I'd rather not waste work and code on something that has no actual use. (Timezone offsets would be useful, but this is such an incredibly hairy issue to get right, I don't want to even try. Just handling Daylight Savings Time would make my head explode, and I can't just leave it out, because then either the admin has to keep changing the offset, or the time will be wrong half the year anyway.)

> non-bolded post numbers
> colons before dates
> colons before names (thread subpages only)

what

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.

217 Name: 214 2005-10-21 15:06 ID:Heaven [Del]

> More information on the all threads page [...] file size?

If (optional) closing on filesize should be implemented, this would probably be a good idea.

313 Name: !WAHa.06x36 : 2005-10-24 18:41 ID:Heaven [Del]

Well, I don't want to have to read posts without highlighting. It's annoying. Just for that, I don't want leave it off.

On another topic, a vote: I could make the secure tripcodes and other parts of the script that use the SECRET more secure by some small changes, but this would make secure trips change when you install the new version.

Good idea, y/n?

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.

12 Name: test 2005-10-13 02:11 ID:Heaven [Del]

>>10
Exactly, but considering a lot of people can't make heads from tails in config.pl, how about a saner default?

>>11
That's true, but if least-popular threads are set to be deleted, instead of oldest-first, you don't have to guess.

104 Name: 103 2005-10-17 15:05 ID:Heaven [Del]

I meant Remote host adress instead of IP.

durr hurr

184 Name:   2005-10-20 09:45 ID:Heaven [Del]

>>183

No, that's just plain wrong. It is very much the job of the programmer to decide on such issues, and make sure they work consistently across boards.

61 Name: Anonymous 2005-10-17 02:10 ID:Heaven [Del]

>>58
Fuck you for giving me <blink>

3 Name: Anonymous 2005-10-12 16:58 ID:Heaven [Del]

Kareha:

  • Conforming of navigation to 0ch standards for conveniency, efficiency, etc., i.e.
  • Navigation links also at the bottom of the thread pages
  • "First 100" to be replaced with "Next 100" (and "Previous 100") in thread pages
  • First post always showing up, even for later quoted ranges. Currently, you can supress this on 0ch by identing "n" before the post range.
  • Default l50 links in all lists
  • Automated archiving, i.e.
  • Automatic thread closing at a configured number of replies and/or thread size (recommended default values: 1000 posts or 512KB)
  • Automatic closing and moving of threads that do not get any activity in a certain timeframe (based on average activity frequency of the board)
  • Bonus features (not really important):
  • Fusianasan (reveal hostname by entering fusianasan or [string] into Name field)
  • Customizable Capcodes (please more than just "Admin", perhaps fancy colours)

13 Name: Anonymous 2005-10-13 02:13 ID:Heaven [Del]

I have always found that it's more difficult than one would think to implement features that will measure "popularity" in a satisfying way that isn't open to abuse in one way or another.

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

114 Name: Anonymous 2005-10-18 03:16 ID:Heaven [Del]

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

94 Name:   2005-10-17 14:06 ID:gBva8ggI [Del]

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

Well, since the current update has removed almost all links to entire threads, I won't do THAT, but I guess a Last 50 link could be snuck in somewhere... Maybe the thread title should be an l50 link?

279 Name: !WAHa.06x36 : 2005-10-23 18:05 ID:gBva8ggI [Del]

>>278

How do you figure it's redundant?

293 Name: Anonymous : 2005-10-23 20:19 ID:Heaven [Del]

Man, this really is annoying.

Partition for unified encoding! Outsource Markup to the select few who want it (I am pretty sure the vast majority of users can live without it).

295 Name: !WAHa.06x36 : 2005-10-23 20:39 ID:Heaven [Del]

Hmm, apparently there's some sort of bug in there still, since it's not marking up that.

171 Name: Shii the Metal Idol 2005-10-19 20:51 ID:z/kxsMjQ [Del]

>>170
But my good man, sage means down.

> Also, how is Kahera unrivaled when there are still large sites that are not running it? Shiichan is still on world4ch, Thorn on parts of wakachan for example.

These are temporary problems because the webmasters of both sites are too stubborn to upgrade.

33 Name: !WAHa.06x36 2005-10-14 05:01 ID:gBva8ggI [Del]

>>32

Your browser momentarily regressed to an old bug and then got better? Who can tell?

>>22

Running in pure perl would be ideal, portability-wise, but in practice implementing a JPEG loader and saver from scratch in Perl is both a lot more work than anyone wants to do, and the result will also be too slow.

As was already stated, making a statically linked executable lets you distribute pre-compiled binaries that people can just upload along with the script.

147 Name: Anonymous 2005-10-19 07:35 ID:Heaven [Del]

> Red, bold thread filesizes displayed near the bottom of subpages?

I support this, especially if thread-closing by filesize should be implemented.

103 Name: Anonymous 2005-10-17 15:05 ID:Heaven [Del]

>>101
If that is legit, then fusianasan needs to display IPs just like tripcodes: not bold/strong.

269 Name: !WAHa.06x36 : 2005-10-23 15:11 ID:Heaven [Del]

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

298 Name: !WAHa.06x36 : 2005-10-23 20:54 ID:Heaven [Del]

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.

132 Name: c-24-91-21-117.hsd1.ma.comcast.net 2005-10-18 17:36 ID:z/kxsMjQ [Del]

test1

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