The Legendary Next Update (365)
290 Name: Anonymous : 2005-10-23 19:44 ID:Heaven
Well, you have links now in the current incarnation. I would think that this kinda thing (Return link vs. Back button) would be common knowledge by now among regular Internet users.
216 Name: Anonymous 2005-10-21 15:04 ID:Heaven
> 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).
55 Name: Anonymous 2005-10-16 10:35 ID:Heaven
>>54
I really don't understand what the problem with the current system is. You must be confused. ┐('～`；)┌
294 Name: !WAHa.06x36 : 2005-10-23 20:38 ID:Heaven
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*.
236 Name: Anonymous 2005-10-21 22:34 ID:Heaven
In mode_image: shouldn't the board title be in <h1>, and the post headers in <h2>?
181 Name: &height=16)
2005-10-20 06:39 ID:ReFmOAs0
The one with encoded Javascript that makes you post with fusianasan is cute.
179 Post deleted by user.
302 Name: Anonymous : 2005-10-24 01:33 ID:Heaven
> how about having a third party create extensions for those browsers and freeing up the real estate on the actual page?
What's with this obsession on removing the CSS options? It's a single line, and some of us find it useful.
Real estate? Scroll down.
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?
289 Name: !WAHa.06x36 : 2005-10-23 19:40 ID:Heaven
Return links are actually not a very good idea. I know some browsers will clear all input fields if you follow a link back to the page you came from, but leave the fields intact if you click the back button.
342 Name: !WAHa.06x36 : 2005-10-27 09:31 ID:SjmelPTB
I don't see any inconsistencies in >>341 except for the rounded corners.
106 Name: qube3.mackey.miyazaki.miyazaki.jp 2005-10-17 15:49 ID:JzjmoL7r
test
68 Name: 61 2005-10-17 07:23 ID:Heaven
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...
86 Name: Anonymous 2005-10-17 12:33 ID:Heaven
> The Title field should go above the Name and Link fields in 2ch mode.
Why should it?
> From every practical standpoint, the current solution in Kareha is a lot more convenient
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.
> Futaba now uses "..." instead of ">>>" to prefix repy blocks.
Any idea why?
117 Name: Anonymous 2005-10-18 04:04 ID:Heaven
>>116
Good question! I tried to find out myself but just found some interesting but rather unhelpful links:
http://d.hatena.ne.jp/keyword/fusianasan
http://info.2ch.net/guide/faq.html#G5
http://ansitu.xrea.jp/guidance/?FAQ1
122 Name: Anonymous 2005-10-18 06:32 ID:Heaven
About the etyomology of "fusianasan":
http://4-ch.net/nihongo/kareha.pl/1102656968/224-
17 Name: !WAHa.06x36 2005-10-13 06:16 ID:ReFmOAs0
Yes, it's throwing Javascript errors for me if I use that character. Gonna look into that some more.
235 Post deleted by user.
237 Name: Anonymous 2005-10-21 22:39 ID:Heaven
>>236
I mean, thread titles in <h2> and post headers in <h3>.
17 Name: !WAHa.06x36 2005-10-13 06:16 ID:ReFmOAs0
Yes, it's throwing Javascript errors for me if I use that character. Gonna look into that some more.
360 Name: !WAHa.06x36 : 2005-10-31 13:25 ID:Heaven
Too late! Already released!
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?
209 Name: Anonymous 2005-10-21 14:16 ID:0dCD+kFU
More information on the all threads page, date of the last post? file size?
A quote button that puts >>n and puts the post prefixed by > in the reply box
Different secret strings for different functions (e.g. one for ID generation and one for secure tripcodes)
83 Name: 2005-10-17 12:09 ID:Heaven
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.
108 Name: 34.75.33.65.cfl.res.rr.com 2005-10-17 19:51 ID:Heaven
I thought fusianasan was supposed to be a mod-only function to weed out bad posters. And what would be the difference between revealing the persons's IP and his ISP's domain?
>>99
I didn't mean to include Forcenick in there, sorry.
Adding to that, however, how about forced sage for specificed IPs? It'd make for a great slogan: Remember kids, tripcodes and aging are privileges, not rights!
153 Name: Anonymous 2005-10-19 13:16 ID:Heaven
>>152
What does that even mean? Does that mean nobody can come along and claim some sort of authorshop/copyright on Kareha or a slightly modified version of Kareha?
15 Name: Anonymous 2005-10-13 06:01 ID:Heaven
> 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.