The Legendary Next Update (365)

100 Name:   2005-10-17 14:52 ID:gBva8ggI [Del]

>>98

Well, that's what I've said from the start, but people keep requesting them.

FUDGE_BLOCKQUOTES is used by the Futaba style, and I guess I just want to keep it there to make it compatible with Futallaby-style CSS files.

6 Name: !WAHa.06x36 2005-10-12 17:30 ID:gBva8ggI [Del]

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.

262 Name: Anonymous 2005-10-22 16:46 ID:Heaven [Del]

"page top" is better imho

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.

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

>>280

I'm not sure. On the one hand, people expect that to work. On the other hand, it can be a bit annoying. On the third hand, it's not all that annoying anyway.

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

>>266

I told you to shift-reload!

206 Name: 205 2005-10-21 03:39 ID:Heaven [Del]

Congratulations to 82.94.251.206!
So the subject line will look like this:
[username]<><>[unix timestamp from now]<>[content of comment box]<> <>[IP]

199 Name:   2005-10-20 18:25 ID:Heaven [Del]

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

306 Name: !WAHa.06x36 : 2005-10-24 12:15 ID:Heaven [Del]

>>305

Shift-reload already! Also, most people are familiar with "More options..." links and know when and when not to click them. I might see about styling it, though.

353 Name: !WAHa.06x36 : 2005-10-28 09:06 ID:Heaven [Del]

>>348

That's a Firefox bug.

343 Name: Anonymous : 2005-10-27 09:51 ID:Heaven [Del]

>>342
Well, for example, in both forms the text labels are bolded when they shouldn't be, in Futaba and Blue Moon. If you take a look at Blue Moon, the text labels in Create new thread are larger than those in the Reply box.

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!

46 Name: !WAHa.06x36 2005-10-14 21:01 ID:Heaven [Del]

> You mean requiring SQL software, or just making backwards-incompatible changes that would screw up old threads?

I mean, needing to alter the table that is already in the database. I don't want to try to do that any more than I have to, as it's pretty hard to get right in a database-independent manner.

> Are you only referring to flooding and spamming, or also trolls and flamewars?

Yes, only flooding and spamming. Trolling and flamewars are not a problem one should use banning to try and solve.

> Finally, out of curiosity: how much of the functionality in the .js file do you think could be properly implemented into a new or existing perl script?

Well, if you serve up dynamic pages, you can do the form-filling on the server, but that's about it. The rest is dynamic stuff.

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

>>66-67

Noted and fixed in development version.

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!

324 Name: Anonymous : 2005-10-26 18:34 ID:Heaven [Del]

> forced fusianasan

that seems kind of evil.

287 Name: Anonymous : 2005-10-23 19:25 ID:Heaven [Del]

Oh, and the navigation bar on the error page should probably look like the one on the thread page.

22 Name: | 2005-10-13 19:57 ID:Heaven [Del]

> statically linked executable

I have to disagree with this. It should run in perl too.

  • If you're running wakaba, obviously perl must be there
  • Most hosts that library-poor don't provide compilers (or shell) either

60 Name: Anonymous 2005-10-16 21:29 ID:Heaven [Del]

The test thread seems to be broken too.

140 Name: Anonymous 2005-10-18 20:03 ID:Heaven [Del]

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

335 Name: Anonymous : 2005-10-26 21:19 ID:Heaven [Del]

>>334
These kind of things are not very difficult to remove from the template if they truly bother you.

221 Name:   2005-10-21 15:48 ID:Heaven [Del]

>>214

Point taken. I'll add it as an autoclose option.

9 Name: test 2005-10-12 20:46 ID:Heaven [Del]

> Reintroduction of "Marked for deletion (old)"

I actually don't like that, and think wakaba should no longer use the futaba style of dropping threads by default. Why not use the least-popular option instead? If a thread is in demand, let it live.

312 Name: Anonymous : 2005-10-24 18:15 ID:Heaven [Del]

Oops. I got confused by the "link to parent post" thing. Maybe you could make that an anchor as well.

Not getting quote highlighting is the point, isn't it? I guess if you really want WakabaMark to spread you can force it on everyone who doesn't know how to change, but it would be nicer to make people choose it so we don't have to constantly see the results of accidental markup. This is more about social engineering than your program, though.

185 Name: Anonymous 2005-10-20 09:52 ID:Heaven [Del]

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

87 Name: Anonymous 2005-10-17 12:36 ID:Heaven [Del]

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.

48 Name: Anonymous 2005-10-15 17:08 ID:Heaven [Del]

I've also had an idea swimming around: an option to only count actual thread bumps in MAX_RES (not "sage" posts). I think it would lead to making each bump more valuable so that people don't do so wastefully and unnecessarily.

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.

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

>>191

Thanks for reminding me that I need to fix the CSS for the captcha!

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

> people like admins might prefer to use them

but they have capcodes now...

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