The Legendary Next Update (365)

125 Name:   2005-10-18 07:50 ID:ReFmOAs0 [Del]

>>123

Noted. I've been struggling with that same problem for naming things internally in the code, and obviously it distracted me from noticing the same problem in the GUI.

216 Name: Anonymous 2005-10-21 15:04 ID:Heaven [Del]

>>208

> multi-page links (1-, 101-, 201-, etc) at the top of subpages

This is just implemented on some 0ch types. 2channel doesn't use it (at least on no board that I know of).

273 Name: Anonymous : 2005-10-23 16:34 ID:Heaven [Del]

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.

150 Name:   2005-10-19 08:46 ID:ReFmOAs0 [Del]

> That's what I thought, but then why is it in the Reply pages?

Er, that's a bug I guess.

> 1) rename the RENZOKU constants to something that makes sense

I dunno, they're pretty useless anyway, as has been pointed out, so I don't know if I care enough to change them.

> 2) Have the string to sage and fusianasan defined as a constant in config

I dunno, if different boards use different strings, that will only make for immense confusion.

> 3) A specific string for ID:Heaven instead of anything in the email field

Well, the only string that makes sense is sage, but yes, I should implement the Heaven-on-sage behaviour.

> 4) Cookie preferences such as "Don't use expanding textarea" which leaves it small or big.. or another option for that choice as well; an option to not save Name/Email automatically; anything else that is useful?

Maybe, but I'm not sure it's worth the effort (I'd have to implement a preferences page for it, too).

36 Name: Anonymous 2005-10-14 13:29 ID:8YdETsDh [Del]

I had a number of good old threads from this board bookmarked so I could read them later and wrap my head around their ideas, but then I lost them all in a hard drive crash (strike two, Western Digital!). I also had a number of Japanese BBS's linked from this board bookmarked so I could take a look at their software's functionality and get some other ideas.

Anyway, these are all non-template suggestions:

  • Topical category metadata in new thread creation so only one instance is necessary per site (further fine-grained behavior with PATH_INFO would let you nest one category inside another and view multiple categories of threads at once).
  • Thorough search functionality a-la notchan, using PATH_INFO. This might not be possible without implementing a per-post metadata system though.
  • Elaborating on the above, per-post metadata for "sage" status, for future-proofing in case someone wants to remove the functionality from the e-mail field (onto a checkbox, for example).
  • config.pl parameter for a generic image that takes the place of a deleted image (ie, Hello Kitty)
  • Fine-grained banning options that let you choose whether or not the user is blocked from reading a board, posting to a board, or both. Another parameter defines the duration of his ban ('0' for permaban), and another defines a reason/message displayed when the user tries to access a board.
  • Replace HTML error pages with dialog box equivalents using JavaScript.
  • Kill user deletion. I can't see any case for when it'd have constructive uses.
  • Conversion to mod_perl?

I also have an early idea swimming around in my head about only bumping threads a few positions up, instead of to the top. Another idea is actively bumping threads down, either by a few positions or to the bottom. I'm not exactly sure yet what good it'd be for.

Also...

>* I'll add thread closing to Kareha, but I was thinking of setting the default behaviour to never permasage or close threads.

I think this is ideal for the time, until we have enough statistical data to derive thorough auto-permasage and auto-delete/archive algorithms. Just add the functionality for mods to manually set these statuses, but remove the "permasage at 1000" behavior.

The standalone thumbnailer project is a great idea too. As a suggestion, how about adding functionality to also read and thumbnail document files like TXT, PDF, and DOC?

297 Name: Anonymous : 2005-10-23 20:52 ID:Heaven [Del]

How about appending an estimated (at the time of thread creation) time of pruning to the first post's header, if pruning-by-age is enabled?

348 Name: Anonymous : 2005-10-27 17:17 ID:Heaven [Del]

I notice some weirdness with the CSS changes sometimes. For example, the first post on a -100 page will sometimes have the first character of the post enlarged. >>2 looks something like
\
/>2 until it is mouse-overed or you change the CSS, but then it goes back to large again on refresh. Also can happen with lowercase letters. Some of the field labels also change size from refreshing in a certain CSS versus just switching to it.

>It's all a design & layout question. I'd like to have the interface reduced to what is absolutely neccessary, esp. since I do not think many people really want to even bother or bother very often with the whole markup question.

Why have a name field or link field? For the majority of posts they are not used, or only used for sage. As stated earlier, they are not even needed for the bare minimum of usage. You want to prove it is you posting? Use a gpg signature or something and a third-party extension, it is just fluff that is not needed at all!

I'm all for having a system that is easy to modify to the end-user's wants and needs. However, there are going to be plenty of users that are not hardcore enough to make or use such options. Therefore, the normal functionality should be pretty usable.

People seem to pop-up whenever something that would change the interface to shout it down. They seem to fear any change and normally give no reason other than it would clutter things up or some nonsense. Does the CSS selector -really- get in your way? It is probably a whole ten pixels! Is having the More options thing really ruining your experience, or are you just against it on some principle? Personally, I would move it below the comment text-area or something, as now the tab amounts between the main fields has changed.

245 Name:   2005-10-22 10:56 ID:Heaven [Del]

Wow, >>243 sure looks like shit in Safari. What the hell? Looks right in Firefox, though.

266 Name: Anonymous : 2005-10-23 14:52 ID:Heaven [Del]

ugh "More options..."

too much clickable elements! and it doesn't even do anything (Firefox 1.0.7 here)!

out! out!

24 Name: 19 2005-10-14 00:36 ID:Heaven [Del]

>>20
"|" is not "¦"

225 Name: 214 2005-10-21 17:05 ID:Heaven [Del]

Okay then, for starters, how about the closing message to exactly look like a post (although it's sad it won't be accesable with >>1001)?

11 Name: Anonymous 2005-10-13 01:41 ID:Heaven [Del]

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

278 Name: Anonymous : 2005-10-23 18:02 ID:Heaven [Del]

Text Art's description about auto-linking URLs and >> references is redundant. Not a bad solution with the layout, though (hiding the menu behind "More options..." still bugs me).

8 Name: test 2005-10-12 18:18 ID:Heaven [Del]

What wakaba needs is that SILLY_ANONYMOUS too! :D

219 Name: Anonymous 2005-10-21 15:25 ID:Heaven [Del]

>>216
I remember at least one or two boards on 2ch that used it, though I can't remember which (moon language and such, you see).

I apologize for the dumb question I made at the end of >>218. I forgot that Kareha permasages (not closes) a thread after the limit is exceeded, so there's no need for a hypothetical 1001th post anyway! orz

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

>>343

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

63 Name:   2005-10-17 04:54 ID:gBva8ggI [Del]

>>59-60

Details, please. Everything works for me.

300 Name: Anonymous : 2005-10-23 23:06 ID:Heaven [Del]

>>299
Seconded. This'll go a long way to resolving headaches with WakabaMark and SJIS art, and there really isn't anything egregious about its current implementation into the mode_message template (nothing compared to putting it in a separate area, for example)

Going back to the CSS selector: since switching styles is not inherently supported in all browser GUIs, how about having a third party create extensions for those browsers and freeing up the real estate on the actual page? The selector to me seems out of place with the rest of the layout, simply because it's only there for the purpose of presentation, not the actual page content. How many people out there change styles from board defaults on a regular basis because of readability preferences?

35 Name: !WAHa.06x36 2005-10-14 13:11 ID:gBva8ggI [Del]

Well, a lot of machines run on x86 these days, so that covers a lot of it. And you could pre-compile for a couple of other architectures, and have it pretty much covered. Linux and unixes in general make it ridiculously hard to distribute binaries, as opposed to Windows or Mac OS, but it's still possible with a bit of trickery. Avoiding dynamic libraries helps a lot.

357 Name: Anonymous : 2005-10-31 11:19 ID:Heaven [Del]

>>354
admin.pl with a separate HTML page in ./admin (so it can be accessed simply by appending "/admin" to the board URL). It should have every possible admin feature available in kareha.pl, including rebuilding caches, modifying the spamlist, and nuking the board.

337 Name: !WAHa.06x36 : 2005-10-27 04:53 ID:Heaven [Del]

I don't see what's so bad about >>330. The alternative is to force the table to be full width, which will make it uglier (because in HTML all columns will become wider, including the skinniest ones), and harder to read.

> No need for a database, just a text file. You're right about storing IPs, though, but then how can you implement a banning system? Do you use an encrypted IP like the algorithm to generate ID codes?

Banning is done through Apache, which really makes more sense than doing it in the script. I don't want to re-invent the wheel for that.

> I mean that (for example) if I wanted to replace the permasaging function under the MAX_POSTS condition (permasage after X posts) with the thread-closing function (close after X posts), all it would require is a simple replacement of the proper function references in post_stuff(), correct?

No, they're done at different different places, because they are essentially different functions. The permasage behaviour doesn't actually permasage a thread, it only refrains from bumping it. There's no permsage flag added to the thread. The closing, on the other hand, does add a flag to the thread.

> Making "More options..." an option in the configs.
> Seems sensible, when you already have the ability to turn off WakabaMark as a board admin.

No. And I actually removed the DISABLE_WAKABAMARK option since it's no longer really needed. The replacement will be an option to select the default markup for a board, which makes much more sense overall.

29 Name: Anonymous 2005-10-14 00:40 ID:Heaven [Del]

Funky, works... I am pretty sure the error has something to do with the characters preceeding the "¦" in the unprocessed tripcode. It begins with a "`"

316 Name: !WAHa.06x36 : 2005-10-25 05:01 ID:Heaven [Del]

Nothing specific, just protecting against any possible future ones.

210 Name: Anonymous 2005-10-21 14:23 ID:Heaven [Del]

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

30 Name: !tFiTnDB9dg 2005-10-14 00:56 ID:Heaven [Del]

testing #`¦

338 Name: Anonymous : 2005-10-27 05:06 ID:Heaven [Del]

> I don't understand the argument for OH NO ANOTHER BUTTON MY WHOLE LIFE IS RUINNED crowd

It's all a design & layout question. I'd like to have the interface reduced to what is absolutely neccessary, esp. since I do not think many people really want to even bother or bother very often with the whole markup question.

> The replacement will be an option to select the default markup for a board, which makes much more sense overall.

I agree, this seems to make the most sense. I understand the "More options..." will not be showing up on boards with fixed settings, so I'll shut my mouth from now on. Apologies to all who I've been bothering.

21 Name: !WAHa.06x36 2005-10-13 12:10 ID:gBva8ggI [Del]

Also, here's something that would be useful, but is a bit more work than I feel like doing right now:

A simple thumbnailing program, that has no external dependencies and can be compiled to a maximally compatible, statically linked executable, for those who have hosts that don't have any image processing software, and don't allow you to compile your own. Should be able to load GIF, JPEG and PNG images, and produce JPEG thumbnails. Should contain all the source code it needs without linking to external libraries (it's easy enough to just stuff libjpeg, libpng, and zlib into the distro).

If anyone is lacking a programming project, feel free to take up this one! If you do, I can provide some fairly fast and good-looking image scaling code (or just rip it out of mangariini yourself).

191 Name: Anonymous 2005-10-20 11:40 ID:Heaven [Del]

> the only boards that use them are image boards where you have to load images anyway.

Correction: http://www.akatsukimanga.com/kareha/

68 Name: 61 2005-10-17 07:23 ID:Heaven [Del]

http://wakaba.c3.cx/sup/kareha.pl/1099697376/101-101
(First "Next 100" link) does not include >>1 in that thread

There's also some weird bug where the entire browser windowd content goes black, dunno what that is about...

89 Name:   2005-10-17 13:10 ID:gBva8ggI [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.

Actually, no, the Javascript just strings some random numbers and letters together.

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

But the body text is even more important, and that goes at the bottom. So I dunno.

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

Would it maybe make sense to make a separate thread creation page?

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