> but when I hit refresh I get the same order.

Browser cache. Try shift-refresh.

It doesn't take a specific range, just >>r30 for 30 random posts.

> Did you ditch customizable capcodes?

No, I removed the dumbass capcode I put in as a demonstration, because I don't like capcodes.

> Using "◆" as the default tripkey character.

I dunno, I always thought that was a kind of big and annoying symbol. Especially when it's so close visually to the question-mark-in-diamond marker some fonts use for characters they don't support.

> How about placing the Formatting menu to the left or right of the "File: " field? I'd also like to see WakabaMark changed to its real name (Markdown).

The File field is almost never there. Also, WakabaMark is similar to, but not the same as Markdown. There are significant differences that make them incompatible (since Markdown is designed to be used when you know you're using it, but WakabaMark tries as best as it can to not do unexpected things if you don't know about it). I might add optional support for real Markdown at some point.

> In Pseud0ch, post numbers should be the same size/format as the rest of the header text

I tried, and it looked much worse than the current solution. Besides, post numbers in Kareha and 0ch aren't the same, since they're clickable here.

> PS. What's "Raw HTML"?

Pretty useless. I'll probably remove it. It's HTML input without turning newlines into <br/>.

> Oh, and "AA mode" should be changed to "Text art mode"

Maybe just "Text art"... hmm.

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.

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

Semantical nitpick: shouldn't the "Page top" link be called "Thread list"?

>>180

The one with encoded Javascript that makes you post with fusianasan is cute.

>>69
The sage seems a bit off...

What wakaba needs is that SILLY_ANONYMOUS too! :D

>>9
I mentioned the option because on highly active boards it's helpful to know which threads will be gone in the next few minutes.

0ch-PHP had this nifty feature where if it was a certain "high bandwidth" time of day, then you couldn't view the whole thread.

Hm... that is kind of useless on a worldwide forum, huh?

But there should still be an option to keep people from viewing more than 100-200 posts, as an emergency way of saving bandwidth.

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.

>>244

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

> Making them configurable from site to site is really dumb, because it would create an unthinkable usability mess.

Why? Let people figure out things themselves, if they are so keen on changing their keywords. They can get together in their own webmaster threads and figure this out. I don't see why this should be solved here.
Of course I think this is a dumb idea in the first place. Nobody needs to know what fusianasan and sage are. Write a FAQ with two sentences about it and/or let your oldtime users tell newbies. Two frickin' words, and you people talk about it as if it were something like making up a new system of romanization!

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

That's a bit too much. You want to talk about sage and fusianasan in the comment field, not trigger it with it.
I suspect you are joking here, though. Design is about what you can take away and still remain optimal conveniency/efficiency on the user part, not about taking as much away as you are technically capable of.

What does Thorn have to do with Kareha? Thorn's counterpart is Wakaba.

Anyway, the version of Shiichan on world4ch is bust. It's not a case of feature versus feature here, Shiichan simply doesn't work. It's not worth comparing until it doesn't break regularly.

If Shii were still working on it might be different, but Shiichan is effectively a dead project which incidentally has a closed and broken version working on world4ch.

PS: I always wanted to say this: The # anchors on the TiddlyWiki automatically scroll me (FF, 1.0.7) just below the actual text box of the entry. Is that a bug, a feature or... ?

I thought fusianasan was supposed to be a mod-only function to weed out bad posters. And what would be the difference between revealing the persons's IP and his ISP's domain?

>>99
I didn't mean to include Forcenick in there, sorry.
Adding to that, however, how about forced sage for specificed IPs? It'd make for a great slogan: Remember kids, tripcodes and aging are privileges, not rights!

Oh, and "AA mode" should be changed to "Text art mode" so we won't be incessantly quibbling about the difference between ASCII and SJIS art.

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)

How about listing what dmpk2k or you have done already?

1. Split threads and posts into separate tables. You're repeating the lasthit and parent column over and over.

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

What does Thorn have to do with Kareha? Thorn's counterpart is Wakaba.

Anyway, the version of Shiichan on world4ch is bust. It's not a case of feature versus feature here, Shiichan simply doesn't work. It's not worth comparing until it doesn't break regularly.

If Shii were still working on it might be different, but Shiichan is effectively a dead project which incidentally has a closed and broken version working on world4ch.

How about a function to replace an inappropriate image with a standard image? (aka HelloKitty.gif)

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

>>177

> It's not worth comparing until it doesn't break regularly.

The only problem with it is that it doesn't do paranoid file writes. The fact that the entire server occasionally breaks isn't related to how broken the script itself is.

>>64
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeh? You are not the real >>64!!!

> partition to kill secure tripcodes

signed

> add functionality for multiple uploads in one post.

I think this was decided against before.

>>66-67

Noted and fixed in development version.