The Legendary Next Update (365)

60 Name: Anonymous 2005-10-16 21:29 ID:Heaven [Del]

The test thread seems to be broken too.

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

huh?

49 Name: !WAHa.06x36 2005-10-15 19:03 ID:Heaven [Del]

>>48

That is an interesting idea, and one that deserves some more thought.

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

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.

184 Name:   2005-10-20 09:45 ID:Heaven [Del]

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

288 Name: Anonymous : 2005-10-23 19:30 ID:Heaven [Del]

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

199 Name:   2005-10-20 18:25 ID:Heaven [Del]

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

True, they're of limited usefulness, but people like admins might prefer to use them. And there are certain cases were you might use them temporarily for various purposes. I wrote the code already, so I might as well leave it in. It has some uses at least.

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

I think I'm too lazy to do it. It's kind of hairy. Besides, as I said, you can remove a lot of the drawbacks of seprate installations by using symlinks.

226 Name:   2005-10-21 17:12 ID:Heaven [Del]

That would be a bother too.

324 Name: Anonymous : 2005-10-26 18:34 ID:Heaven [Del]

> forced fusianasan

that seems kind of evil.

271 Name: Anonymous : 2005-10-23 16:32 ID:Heaven [Del]

Did you ditch customizable capcodes?

How about placing the Formatting menu to the left or right of the "File: " field? I'd also like to see WakabaMark changed to its real name (Markdown).

A few other considerations:

  • Using "◆" as the default tripkey character.
  • No need for the "Navigation: " text before the navigation links in subpages
  • In Pseud0ch, post numbers should be the same size/format as the rest of the header text
  • I'm still thinking that subback should be as minimal as possible: no navlinks, title, or last post/filesize data. Then again, I'm from the school of following 0ch blindly.
  • Variable admin permissions per password
  • Is the Admin bar gonna come back before the final version?

Small details aside, this is seriously shaping up to be an amazing release. Your efforts are much appreciated, WAHa.

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

42 Name: Anonymous 2005-10-14 16:30 ID:Heaven [Del]

Forgot this one:
The general functions of imageboards do not seem to be clear to most people that eventually come around, the influx of total newbies is still big. Many neither know what sage is, how to properly reply to threads, what tripcodes are, etc.
Because of that, I believe it would be good to include a default link at the bottom of the unordered list at the bottom of the new thread form that links to http://wakaba.c3.cx/docs/docs.html#UsersGuide

Relevant:
http://dis.iichan.net/idc/kareha.pl/1128824710/12-

212 Name: Anonymous 2005-10-21 14:44 ID:1Jq07X/h [Del]

>>210

monospace font? like this?

166 Name: 148,161 2005-10-19 18:40 ID:0dCD+kFU [Del]

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

It does get in your way though, I enumerated cases where this is the case (albeit edge cases).

>>>Then just make one post with your name/trip and one with fusianasan and let your ID show up in both.

fusiansan is just intended for rare or special cases anyway, as is the whole subject of identification on anonymous message boards.

You still end up with no way to link the fusianasan post with the name/trip one without IDs enabled (unless the ID method is known and no secret data is used).

>>>It's rarely needed anyway. Also, these things are pretty easy to remember. "sage" and "fusianasan" is all there is, really.

You spelled it fusiansan once.

Also, how is Kahera unrivaled when there are still large sites that are not running it? Shiichan is still on world4ch, Thorn on parts of wakachan for example.

http://wakaba.c3.cx/sup/kareha.pl/1127713568/l50 is also semi-relevant

288 Name: Anonymous : 2005-10-23 19:30 ID:Heaven [Del]

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

199 Name:   2005-10-20 18:25 ID:Heaven [Del]

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

True, they're of limited usefulness, but people like admins might prefer to use them. And there are certain cases were you might use them temporarily for various purposes. I wrote the code already, so I might as well leave it in. It has some uses at least.

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

I think I'm too lazy to do it. It's kind of hairy. Besides, as I said, you can remove a lot of the drawbacks of seprate installations by using symlinks.

61 Name: Anonymous 2005-10-17 02:10 ID:Heaven [Del]

>>58
Fuck you for giving me <blink>

106 Name: qube3.mackey.miyazaki.miyazaki.jp 2005-10-17 15:49 ID:JzjmoL7r [Del]

test

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.

358 Name: Anonymous : 2005-10-31 12:45 ID:QLQI2pST [Del]

...and admin posts that override all board/thread restrictions (ie, bumping a permasaged thread and possibly even posting in closed threads).

306 Name: !WAHa.06x36 : 2005-10-24 12:15 ID:Heaven [Del]

>>305

Shift-reload already! Also, most people are familiar with "More options..." links and know when and when not to click them. I might see about styling it, though.

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

Nothing specific, just protecting against any possible future ones.

205 Name: Anonymous 2005-10-21 03:15 ID:Heaven [Del]

If we must discuss Shiichan's bug (which I believe we don't): I like the one where it sometimes turns an existing thread at the end of the All thread list into a thread with no subject, creation date set as 31 Dec 1969: 19:00 and then set to -1 posts (!) - and when you post in it, you 0GET and your IP appears as the subject.

It's a brilliant, better than fusianasan! Try it out: http://dis.4chan.org/read.php/dis/1121735647/

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.

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.

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.

319 Name: Anonymous : 2005-10-25 18:35 ID:Heaven [Del]

rel=nofollow for internal links as discussed in http://wakaba.c3.cx/sup/kareha.pl/1127092367/

318 Name: Anonymous : 2005-10-25 17:35 ID:Heaven [Del]

style:none plz!

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?
This thread has been closed. You cannot post in this thread any longer.