The Legendary Next Update (365)

322 Name: Anonymous : 2005-10-26 10:38 ID:Heaven [Del]

You could add entire thread links to either the "num" or "posts" column in subback.

178 Name: Anonymous 2005-10-20 06:26 ID:Heaven [Del]

> and/or let your oldtime users tell newbies.

Like so? http://wakaba.c3.cx/soc/kareha.pl/1124991549/7

155 Name: Anonymous 2005-10-19 13:42 ID:Heaven [Del]

>>154
Kami! Nice ID.

136 Name: Anonymous 2005-10-18 18:52 ID:Heaven [Del]

Hey, I just noticed this: where did the admin link go? Or are you working on a separate interface already? :D

19 Name: Anonymous 2005-10-13 11:43 ID:Heaven [Del]

>>18
Firefox 1.0.7, WindowsXP Pro.

133 Name: c-24-91-21-117.hsd1.ma.comcast.net 2005-10-18 17:36 ID:z/kxsMjQ [Del]

test2. looks good!

127 Name: Anonymous 2005-10-18 16:23 ID:Heaven [Del]

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

103 Name: Anonymous 2005-10-17 15:05 ID:Heaven [Del]

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

90 Name: Anonymous 2005-10-17 13:23 ID:Heaven [Del]

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

Considering that the ratio of users who start new threads to those who don't is pretty small on most message boards, I think it does.
A seperate page could also be used to put a more visible disclaimer/set of rules, as a seperate page with a different layout is likely to generate more attention from the user. Stuff that can be put there also wouldn't clutter up the frontpage.
I don't think this is an urgent matter, though.

292 Name: Anonymous : 2005-10-23 20:18 ID:Heaven [Del]

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

98 Name: Anonymous 2005-10-17 14:26 ID:Heaven [Del]

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?

112 Name: Anonymous 2005-10-17 20:40 ID:UAOHJNRy [Del]

>>108
fusianasan is a voluntary function to show identity without having to memorize a tripcode. Works on all boards. Reveals your IP, of course...

Another feature I'd like is keyboard shortcuts like Wikipedia. Although you'd have to avoid stuff like Alt-D.

162 Name:   2005-10-19 16:45 ID:gBva8ggI [Del]

Well, there are some issues to consider here:

  • Hardly anybody needs to ever use fusianasan. It's a gimmick. Design decisions should not be made around it.
  • The strings may be strange, and combining fields isn't the best design possible, but this is a 0ch clone, after all. If I were designing something from scratch, I'd do things differently, but as it is, people are expecting 0ch behaviour, and it would confuse them if the script worked like 0ch in some ways but not others.
  • I might consider adding additional strings that trigger sage and fusianasan, but I'm not sure what they should be.

In the end, people actually enjoy the 0ch quirkiness. I know I do. I know about designing good interfaces, but there's something fun about an interface that is a little bit quirky, as long as it doesn't get in your way, and these things don't.

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

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

>>19

I can't reproduce this on Firefox 1.0.4 nor Safari on the Mac, but that ancient Firebird had a similar problem (but even worse).

Anyone else? Try post with a | in your name.

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.

363 Post deleted by moderator.

32 Name: Anonymous 2005-10-14 00:57 ID:Heaven [Del]

Well, both >>30 and >>31 didn't change the ¦ into ?U so I am out of ideas what happened...

265 Name: !WAHa.06x36 : 2005-10-23 14:24 ID:Heaven [Del]

All right, code updated again. This time, some experimenting! I've implemented a tentative system for changing markup types. This needs a bunch of testing, of course, so here's the test thread link once again: http://wakaba.c3.cx/sup/kareha.pl/1099697376/

Thoughts and comments are welcome. I'm still trying to figure out how exactly to do this.

There's a bunch of other changes and fixes too, so mention if anything breaks, as usual. Also, shift-reload!

277 Name: !WAHa.06x36 : 2005-10-23 17:59 ID:Heaven [Del]

All right, made another small update. Needs a shift-reload again to work quite right (there's a short description of the various markup modes now). Also fixed >>143 and removed "Raw HTML".

71 Name: Anonymous 2005-10-17 08:18 ID:Heaven [Del]

>>63
Nevermind, the issues seem to have resolved themselves within the hour of the new version being uploaded.

More stuff:

To more closely resemble the 2ch look, how about prefixing thread title headers in the main board page with a 【position:postcount】thingie?

And as suggested before, the navigation links on the bottom of individual thread pages should include "Previous 100" (ie, all posts before the first post in the URL) and "Next 100" (ie, all posts after the last post in the URL). Of course, this could get screwy if you're using reverse order and out-of-order posts in the URL, so I dunno how well it could be implemented.

The "First 100" link should also be removed from the bottom of individual thread pages, and there should be a link to to thread-list included below the reply box of each previewed thread on the front page.

Bonus:

Change "Del" links to widget buttons.

In order for the CSS selector not to take over the entire header, how about turning it into a drop-down menu? The same could be done with the Admin functions (appearing only after one correctly inputs the password), placing it on the right side of the board and thread title headers (this would also allow admins the convenience of deleting and permasaging threads from the front-page).

and would something like this work (given that all boards share the same root directory)?

>>>>sup/1129153864/1-100
>>>1129153864/1-100

P.S. When you mentioned serving dynamic pages in >>46, were you referring to individual thread pages? As I mentioned before, it'd be nice to make the front page as dynamic and flexible as thread pages when it comes to viewing options (via PATH_INFO).

355 Name: Anonymous : 2005-10-28 19:32 ID:m/57LIb/ [Del]

There needs to be a separate page for bans, at least.

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

> I don't see a big fat ugly WakabaMark FAQ next to the post form either.

You don't see the link to the WakabaMark page either?

> I am just guessing here, but I am pretty sure most people will only change their settings in very rare cases.

I just added the Text Art mode so that people could post AA on any board and have it work right, but the only way for that to work is if you can quickly change modes between posts.

Look, it's getting just a tiny bit annoying with the complaining. I've been putting a huge amount of effort into making this work well both for those who want markup and those who don't. If you don't like it, you turn it off and don't need to bother with it again. There's just a tiny little link there to let people do this. Is this really a such a huge bother to deal with? It's *two words*.

78 Name:   2005-10-17 09:13 ID:Heaven [Del]

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

149 Name: Anonymous 2005-10-19 08:31 ID:Heaven [Del]

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

Isn't that already an option in the config?

> 5) Seperation of sage et al from the email field to something else...

Strong oppose! I am of the (strong! lol) opinion that the current situation is the one working the best and also that it is widely accepted on almost all similiar board scripts (save for Shiichan and one obscure Japanese discussion board script that I once stumbled upon).

Previous discussion of this can be found here:
http://wakaba.c3.cx/sup/kareha.pl/1102984488/

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

160 Name: Anonymous 2005-10-19 14:51 ID:Heaven [Del]

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

272 Name: Anonymous : 2005-10-23 16:33 ID:Heaven [Del]

PS. What's "Raw HTML"?

351 Name: dmpk2k!hinhT6kz2E : 2005-10-28 04:55 ID:Heaven [Del]

I think you're a bit nutty, >>350...

340 Name: Anonymous : 2005-10-27 08:57 ID:Heaven (Image: 1010x554 png, 80 kb) [Del]

src/1130425040482.png: 1010x554, 80 kb

>>336
IMO minimalist web applications like Kareha should only focus on core content/functionality and leave the inconsequential presentation options up to browser extensions so that each user can tweak them to his whim. That's why I was pushing to offload the CSS selector to an extension.

>>337
Here's a better example, I think. Even if we can't remove the excessive side borders, is there a way to at least have rounded corners?

On formatting options: I think >>338 fails to understand that leaving the formatting options up to each individual user is a good thing by all means. Besides, they are absolutely necessary to the interface and core functionality, just like the Name and URL fields are. Preview functionality, on the other hand, should be implemented in an extension.

I think the issue that people have with the formatting options is that we don't have a Japanese counterpart to blindly model it after. Since we're going at this on our own, nobody is quite sure how it should be done. I'd like to see how it turns out on mode_image (if you feel the need to include it at all). :)

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