The Legendary Next Update (365)

227 Name: Anonymous 2005-10-21 17:21 ID:Heaven [Del]

>>226
(´・ω・`)

223 Name: 214 2005-10-21 16:41 ID:Heaven [Del]

I want a 1001th post! :(

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?

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

>>108
I don't think that restricting specific users' posting priviliges is useful in any way except restricting them from posting.

>>108,113
"fusianasan" is for when a user wants to prove that he is posting from a certain place (like a school, a company's network or a military base).

>>112
A keyboard shortcut for "reply" in Kareha or "submit" in Wakaba would be nice to have.

65 Name: 61 2005-10-17 05:14 ID:Heaven [Del]

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

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

244 Name: Anonymous 2005-10-22 10:55 ID:Heaven [Del]

I don't know if this is a bug or not, but could you change the Futaba template so that hovering over/clicking on a post header doesn't count as doing the same to the deletion checkbox next to it? Same goes for the "[File Only]" area at the bottom with its checkbox.

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!

164 Name: Anonymous 2005-10-19 18:08 ID:Heaven [Del]

>>161

>3) was about a string to trigger ID:Heaven, not a constant for the Heaven part (which is already configurable)

That's what I was referring to also in >>154 (S_NOID being the theoretical trigger string for ID:Heaven).

Concerning localization: there are certain compromises with input triggers that must be made in order to maintain interoperability with Japanese users coming from 2ch/Futaba. They're not going to care about a system where "sage" and "fusianasan" (in Roman too I'm guessing, can someone confirm this?) don't work in their respective fields. In effect, 2ch set a standard of usability that we need to follow if we want to build a bridge between both communities.

On the flipside, I think there should also be a secondary set of trigger strings that would be more coherent to Western users and universal to all Western boards. Making them configurable from site to site is really dumb, because it would create an unthinkable usability mess. With Shiichan's death, Kareha stands unrivaled, and setting these strings in stone would ingrain them in the culture like "sage" and "fusianasan" have been in Japan. Thinking very optimistically, if a Western BBS site should grow into something large enough for 2channers to strongly take notice of, they would pick up on these triggers and possibly make their own concessions to implement them in 0ch.

What they should be is yet to be determined. Unfortunately, they'll probably have to be pretty dull in comparison to the witty botanical references and word puns in 2ch and Futaba.

>>163

>I don't think so, not in these cases. What's the alternative? Having a different field for fusianasan, a new checkbox for sage, etc.? That's just cluttering up the interface.

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.

>Huh?

He meant saging a thread just because a part of the actual e-mail address contains the word "sage."

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.

296 Name: !WAHa.06x36 : 2005-10-23 20:44 ID:Heaven [Del]

Should be fixed now.

233 Name: Anonymous 2005-10-21 22:16 ID:Heaven [Del]

>>232
Nothing! But since mode_image's footer.html includes a link to Futaba called "Futaba mode," I think mode_message should have the same.

43 Name: Anonymous 2005-10-14 16:31 ID:Heaven [Del]

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

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.

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?

311 Name: !WAHa.06x36 : 2005-10-24 17:24 ID:Heaven [Del]

> Why not make None or Text Art the default?

Because >>309. I don't want to implement half of WakabaMark for the None mode, and without it you don't get stuff like quote highlighting.

> Also, can you make >> links into anchors('#') when you're on the reply/entire thread page, especially in Wakaba?

Er, that is exactly how Wakaba works right now? And Kareha can't change the contents of posts dynamically, so it'll never do it.

58 Name: anon <-- Testing person 2005-10-16 21:13 ID:Heaven [Del]

huh?

75 Name: 74 2005-10-17 08:41 ID:Heaven [Del]

> 2channel does not do this either by default. It can make browsing a bit more convenient (and I suspect dedicated 2channel browsers to insert & read these in some kind of standardized way) but I don't think that's reason enough to impose it on users by default.

whoops, I misread "postcount" as "posticon". Nevermind!

101 Name: sjcd-dmzweb-ce8.cisco.com 2005-10-17 15:04 ID:95ZECAi3 [Del]

sup

356 Name: !WAHa.06x36 : 2005-10-28 20:05 ID:Heaven [Del]

I'm not sure I want to make a ban system. I'd rather just make it easy to interface with a simple banning script that does whatever's needed for the server it's running on.

15 Name: Anonymous 2005-10-13 06:01 ID:Heaven [Del]

> Pruning set to furthest-back instead of oldest.

I don't like this one. You just have to continually age a topic (until it hits the permasage treshold) in order for it so survive a long time. Normal users might have good reason to ignore simply it, though...

> Size limit instead of post number limit, maybe?

Sounds good.

> I was thinking of setting the default behaviour to never permasage or close threads.

I guess I don't have a strong opinion on this one. As long as the values will be customizable, I don't really care, I suppose.
Also: I just noticed that "¦" in tripcodes will work correctly but turn into "�U" through the cookie on /soc/ but not on the sandbox.

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.

237 Name: Anonymous 2005-10-21 22:39 ID:Heaven [Del]

>>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 [Del]

test

12 Name: test 2005-10-13 02:11 ID:Heaven [Del]

>>10
Exactly, but considering a lot of people can't make heads from tails in config.pl, how about a saner default?

>>11
That's true, but if least-popular threads are set to be deleted, instead of oldest-first, you don't have to guess.

138 Name: Anonymous 2005-10-18 19:55 ID:Heaven [Del]

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

43 Name: Anonymous 2005-10-14 16:31 ID:Heaven [Del]

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

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.

10 Name: Anonymous 2005-10-12 22:19 ID:UAOHJNRy [Del]

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

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