>>58
Fuck you for giving me <blink>

Weird, ¦ now stays ¦.
Testing #¦ now.

>>70

?

> Personally, I find the reverse order listing, as well as the random order listing, to be a bit silly & useless.

Well, no, duh, that's the point. They're jokes.

> The only useful bonus feature here seems to be the comma range seperator, but it seems even in that case there is not much benefit to it (saves 1-3 links in the average case that it is needed, which is rare to begin with).

On the contrary, it's very useful when referring someone to a specific discussion in a thread where several discussions are going on, since you can make a link that only shows the relevant posts. Not just on the board but when linking to threads elsewhere.

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?

Partition for renaming "WakabaMark" to "WAHaMARk"!

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

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

About rel=nofollow: What links should have it? Obviously not the "entire thread" link, but the l50 links in the thread list sort of need it, otherwise the search engine will never find them in the first place. But that means the l50 links will end up in the index.

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

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

Whoops, sorry. I read "close" instead of "permasage".
Permasage on filesize seems pretty silly, yes.

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

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

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

testing #`¦

Oh:

> Getting back to inconsequential nitpicking: I find the "___ image replies omitted" phrase to be a bit redundant, and for one it confuses me as to whether or not those image replies are separate from text-only replies. How about simply calling it "images"?

Yes, that's a great idea, which is why I've always done just that. You're thinking of 4chan.

So, I made the All threads page a lot fancier. Might need some shift-reloading to get the proper CSS.

Is this about done, besides the admin bit? I'm getting a bit tired and distractions are looming to the left and right.

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

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

>>266

I told you to shift-reload!

> but I don't quite see why there should be a "First 100" at the top but not at the bottom.

Probably to avoid clutter and because of the assumption that if you arrive at the bottom of a page, you can do without the "First 100" link. "First 100" seems to be a navigational aid for beginners who are new to the thread, so it makes sense to only have it at the top.

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

n is implemented, but not for >> yet.

Also, >>1 is, as it is, only added to URLs of the form xx-yy and lxx. 2ch doesn't add >>1 for single-reply URLs, and if you're using commas, I figure you can add >>1 yourself if you want it. I'm not sure if this is the best behaviour, but that's how it works at the moment.

Also, wouldn't making capcodes even more prevalent be considered A Bad Thing®? If anything, the role of capcodes should be minimized or altogether eradicated, in favor of ninja moderation.

Another question: would FUDGE_BLOCKQUOTES be considered deprecated by now, or are there still CSS styles out there that require it?

>>n74,76

It's good for referencing replies, too.

The "always show the first post" behaviour is sort of confusing at first. It seems more intrusive than useful.

A 1001th post would be a bother.

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

>>137
I'd advocate going for a separate interface a-la Wakaba, but it might be a bit too much to do for this release.

Also, maybe Easter Eggs like the Eternal September timestamp and others (if they exist) should be documented in config.pl.

Lastly, a question: who here finds enough use in the auto-expanding comment box to justify the annoyances when you click in or out of it?