The Legendary Next Update (365)
34 Name: Anonymous 2005-10-14 12:36 ID:hjzD4Li4
Tell me more about these pre-compiled binaries. I thought that was impractical...I mean, instruction set differences and so on.
202 Name: &height=16)
2005-10-20 19:06 ID:Heaven
Yeah, no, maybe. Using secure trips for capcodes also adds extra protections against accidentially misspellingyour capcode and leaving it open to attack.
160 Name: Anonymous 2005-10-19 14:51 ID:Heaven
>>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
237 Name: Anonymous 2005-10-21 22:39 ID:Heaven
>>236
I mean, thread titles in <h2> and post headers in <h3>.
106 Name: qube3.mackey.miyazaki.miyazaki.jp 2005-10-17 15:49 ID:JzjmoL7r
test
179 Post deleted by user.
11 Name: Anonymous 2005-10-13 01:41 ID:Heaven
>>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.
85 Name: Anonymous 2005-10-17 12:26 ID:1l2MEdqn
I'll sign that partition for a separate admin script and XHTML interface (one that includes the banning, board nuking, and spamlist-changing functions in Wakaba).
How about adding flexibility to the DELETE_FIRST option in config.pl, using booleans to define when to keep or remove a thread (including AND/OR/NOT arguments)?
Also, options for both automated permasaging and pruning by postcount, creation date/time, and board position (all configurable in config.pl of course).
Some other layout points:
- The Title field should go above the Name and Link fields in 2ch mode.
- 2ch's "new thread" post box is at the bottom of the main page. From every practical standpoint, the current solution in Kareha is a lot more convenient, but you may want to go over that just in case.
- Futaba now uses "..." instead of ">>>" to prefix repy blocks.
263 Name: 2005-10-22 16:55 ID:Heaven
122 Name: Anonymous 2005-10-18 06:32 ID:Heaven
About the etyomology of "fusianasan":
http://4-ch.net/nihongo/kareha.pl/1102656968/224-
88 Name: Anonymous 2005-10-17 12:39 ID:Heaven
>Why should it?
Because it's one of the two requirements for creating a new thread, and it's a lot more important to have a well-defined topic than to fill in your name.
>It's more convenient if you want to start a new thread, but for those who don't it's one more form to have to scroll by.
Good point.
>Any idea why?
I dunno. I guess it's just another one of Futaba's countless layout quirks.
179 Post deleted by user.
11 Name: Anonymous 2005-10-13 01:41 ID:Heaven
>>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.
200 Name: 2005-10-20 18:28 ID:Heaven
Thanks for reminding me that I need to fix the CSS for the captcha!
282 Name: !WAHa.06x36 : 2005-10-23 18:24 ID:Heaven
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.
94 Name: 2005-10-17 14:06 ID:gBva8ggI
> 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?
292 Name: Anonymous : 2005-10-23 20:18 ID:Heaven
> No, because that would be immensely useless and annoying, because nobody would know it's there,
Nobody knows how to use WakabaMark as it is now either and I don't see a big fat ugly WakabaMark FAQ next to the post form either.
> and even if they did, they'd have to go somewhere else every time they wanted to post something using a different markup.
I am just guessing here, but I am pretty sure most people will only change their settings in very rare cases.
I really think this is something that would be more useful in some sort of browser extension than in the actual software.
251 Name: Anonymous 2005-10-22 13:00 ID:Heaven
>>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).
288 Name: Anonymous : 2005-10-23 19:30 ID:Heaven
0ch's error page provides a link to return to the board from which the error originated, which I think is pretty reasonable. Sometimes I think the navigation bar and CSS selector are used somewhat excessively in mode_message (though the latter's presence has been diminished significantly throughout the course of this thread).
197 Name: Anonymous 2005-10-20 14:02 ID:Heaven
>>196
Actually, a solution to >> links with static pages is to simply make them reference a certain point on a certain page number for that thread (ie, http://wakaba.c3.cx/sup/1129153864/index2.html#197).
98 Name: Anonymous 2005-10-17 14:26 ID:Heaven
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?
176 Name: Anonymous 2005-10-20 02:32 ID:Heaven
PS: I just tested fusianasan + tripcode on 2ch, it works fine.
196 Name: Anonymous 2005-10-20 12:51 ID:tlSRz7E3
>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.
>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.